https://github.com/GarageGames/Torque3D ... screenshot perhaps?

Same issue occur for you with the development fork? Been trying to nail that bit of hinkiness down for a while now, so more data could help there.

Going to dig into this today (likely an issue on my end based on the feedback so far) but all of the builds fail to run on my system. They show the Torque3D splash screen and then immediately close. Console log seems normal, last line is 'sfxStartup...' but that's not particularly helpful. This is ...

That's a pretty reasonable tweak to the idea. I'll also talk to lukas and see if we can find any kind of moderation strikes marker so it's easier to keep tabs on things. I've seen forum systems where it's a "health" system that comes back over time on good behavior, which I think is a good way to a...

Only thing we've got thus far resembling a decent report thus far is: When launching T3D 4.0 Test 2 (May 25 2019) this error appears. Did not occur with prior Test 1 (May 20 2019). That'll translate to checking each commit on somebody with a win 7 box from Commits on May 19, 2019 to probably around ...

You are consistently failing to separate the action from the actor. Nobody is saying folks cannot object to an action. What they are saying (and all that this CoC codifies) is that you can and indeed are encouraged to criticize any given act or product. But if the language used is applied to an indi...

Have you considered just not labeling a person with a negative attribute simply because you either don't understand their point of view or disagree with it, and instead focusing on the point of disagreement?

This thread shows otherwise.

Fix yourself.

mProbeArrayEffect->setShaderConst("$numProbes", mEffectiveProbeCount);
+
uniform int numProbes;

does indeed seem to have done the trick as far as the hang goes. still doesn't quite explain why it went nearly that batshit, but thanks for a much saner fix.

https://github.com/Areloch/Torque3D/blob/Preview4_0_skylight_array/Engine/source/renderInstance/renderProbeMgr.cpp#L782 to mProbeArrayEffect->setShaderConst("$numProbes", (float)mMax(mEffectiveProbeCount,1.0)); with otherwise identical code did indeed serve to bypass the flaw. which is still.. bizar...

Since you haven't specified player, weapon, vehicle, or background asset: For physics, vertex density means more than sheer vertex count on the asset side. Particularly if you're skipping making collisionmesh proxies and usings straight what you see is what you get collisions. Per scene we've found ...