My biggest issue with Persist behavior is that "Reset persisted objects" action resets all objects on all layouts - which makes it pretty much unusable in large projects.

There are also lots of bugs when objects with Persist behavior are in hierarchies, restored from save state etc.

What are some of the issues you've run into regarding saves? I'll need to keep an eye out on those in my project as well. I did run into hierarchy issues on my end too, which I had to solve with some failsafes.

Persist feels more and more like it is more trouble than it's worth. I've avoided using it in other projects because of it's monolithic nature, and only did so this time because developing my own tracking methods was previously such a pain that I figured this would be better.

Still trying to figure this one out, I am able to band-aid fix some of the issue by turning the back face of the object invisible when it's obscured from the player (using raycasting) but this still allows for edge cases (such as when the corner of the object is visible, but the rest of the back face is obscured, it will still display).

I've been using the fog exponential effect for my project and up til recently been quite happy with it. However, I discovered that it doesn't really create a radius around the player from which fog starts, but rather just draws a straight line in relation to where the camera is facing, to illustrate this point, here is a screenshot where I bumped the fog density up to 100%:

I get why, for most projects this would be perfectly acceptable. It's not ideal for mine though, I was hoping to have a radius I can fiddle with to give the game a bit more moodiness. Any ideas on ways I can recreate or work with the existing fog exponential effect to achieve more of a ring of fog around the player?

The two methods that immediately come to mind would be updating the players deceleration value, or for more granular control you could tween a value and update the players speed to reflect that while the tween is running.

Thank you so much for the reply R0J0hound!

It took a bit of futzing with, but I did get it running in my game and I am pretty happy with the results. For anyone who hopes to do this in the future with 3D shapes as I did, the easiest way is to basically just copy your example and then add a "for each sprite" event afterward that replaces each sprite with your 3d shape and updates its size to reflect it. Make sure you add a centered image point to your sprite and spawn the 3D shape there. I spent a couple hours trying to spawn the 3D shape instead of a sprite and just offset it but that never worked properly for me.

So I'm trying to optimize my dungeon generation. Currently I use a similar method to the "3D Castle Maze" example. I generate a tilemap at runtime that then creates 3D objects as solid walls on each applicable tile.

However ideally I would like to optimize this further. Because my generated dungeons can be quite large and complex, and because I am spawning hundreds of enemies, I do start to see performance drops when I reach 900+ objects.

One way to reduce the number of 3D objects is to identify straight lines of repeating tiles and create a single 3D object that is the length/width of those identical tiles (plus their corners) instead of one 3D object per tile.

I have an over complicated, very broken version of this already so I'm hoping someone can point me to a simpler solution to this. Currently I ID every "corner" tile and repeat a check in 1 direction for that corner until it ID's a different corner, and spawn the 3D object based on that information. Unfortunately this is really complicated and falls apart a bit at some weirder junctions you can see in the screenshot below:

I've been having random, intermittent visual issues with effects in 3D through out my project. This either seems to be tied to updates being made to Construct or changes I am making in development that I assume won't affect established effects but apparently do. Here's some examples:

Here we have an issue where a tint effect placed on a sprite being used as a 3D face screws up some aspects of other 3D objects behind it.

The above issue has been occurring for a longer period, some bullet objects display even when behind a 3d object.

These kinds of issues have been popping up through out the project, what should I look for to fix them and what might be some best practices to avoid them going forward?

Thanks in advance

A stupid method I have used is to pin a fan shaped sprite to the player billboard facing toward the camera. Your player billboard is already locked to the camera so if you pin the angle of the fan, it should do the same.

Then you set any wall colliding with that fan to invisible. This has some obvious drawbacks, like allowing players to see through walls, but works well enough in many cases.

Alternatively, you could use the Line of Sight behavior to cast a ray in the direction of the camera from the player, and then clamp the camera distance to the length of that ray if it intersects a solid object. That might have some issues to, just spitballing.

A quick follow up because I had an idea on how to approach this that I think would work, but presents edge-cases I can't account for and just isn't as stable as the original brute-force method.

My idea was to identify corner tiles in the generated tilemap and then assign each one a direction. The system then repeats a check in that direction from that corner until it identifies a tile different from the wall connected to the tile:

Tilemap being used (arrows id corners and which direction they check for):

I couldn't use the Auto-16 tilebrush and had to use the 47 in order to identify both inner and outer corners. This ALMOST works:

There are some positioning issues I could work through, the bigger issue is that using this method, sometimes a wall is created that has no "spawn corner":

Short of brute-force checking corners for connecting walls and fixing them after the original run, I can't think of an elegant solution to this. I'm probably going to revert back to the "one tile one 3Dobject approach", but I wanted to document this here in case anyone has a similar issue and wants to refine my approach. Here's my function: