We're a little over 2 weeks out, and while it's taking a little longer than anticipated to push through the RC(I said 1-2 weeks initially), it's because we found a few straggler issues we needed to wrap up.

I'm trying to wrap up the file dialog action for linux, and we've resolved most of the apparent SDL issuse, pending a few PRs getting rolled in. Once that's complete, I'll do a final spit-n-shine QA run over to try and make sure everything's on the level, and we should be good for release.

In other words, we should be good for the real release by the end of the week! Yaay.

When i am in the Scene on the MissionGroup and i double click on the name of some item a small box pops around the the name of the item. If i change it's name and click enter on my keyboard the new name is discarded and the old one is used.

When i am in the Scene on the MissionGroup and i double click on the name of some item a small box pops around the the name of the item. If i change it's name and click enter on my keyboard the new name is discarded and the old one is used.

Looks like it's a bug. Luckily, renaming from the name field on the object looks to still work fine. Can address that later.

As for 3.8, I've got the Linux file dialogs partially working, and if the stars align should have them wrapped up tonight. Codeblocks unfortunately doesn't make debugging stuff easy, so it's a bit slower going.

A while back I posted an issue on github about 2048+ size heightmaps, soon I discovered that the problem with that size could be with the vram memory, but the thing is that in cryengine and UE4 I can import 4096+ heightmaps without any problems.

A while back I posted an issue on github about 2048+ size heightmaps, soon I discovered that the problem with that size could be with the vram memory, but the thing is that in cryengine and UE4 I can import 4096+ heightmaps without any problems.

So, same hardware, but you can load 4096 heightmaps on other engines, but not Torque?

Alright, thanks for the rekindle on that. I don't remember running into this myself, but I may just have bypassed it. I'll make sure we get this touched on. If possible, could you upload an example of a heightmap that was giving you problems, so I can test against it?