Torque 3D Beta 3,4,5 Bug: crash on multiple terrains with different mat count
by Fyodor -bank- Osokin · in Torque 3D Professional · 06/24/2009 (4:19 pm) · 10 replies
In case we have more than one terrain block in mission and first block using more textures comparing to others, we need to be sure HERE we are not trying to use NULL's properties, so checking if material is actually fixed crashing when loading mission. The proper fix should be "matCount" to equal the exact number of material on "current" terrain block being process, haven't looked into this though.
Inside:
bool TerrainCellMaterial::_createPass( Vector<MaterialInfo*> *materials, Pass *pass, bool firstPass ):
After this code block:
I'm doing some "research" with T3D (have 16 terrain blocks) and noticed with when was messing with painting and re-logging.
Inside:
bool TerrainCellMaterial::_createPass( Vector<MaterialInfo*> *materials, Pass *pass, bool firstPass ):
After this code block:
normalMaps.clear();
pass->materials.clear();
for ( U32 i=0; i < matCount; i++ )
{
TerrainMaterial *mat = (*materials)[i]->mat;I needed to add this check:...
for ( U32 i=0; i < matCount && !baseOnly; i++ )
{
TerrainMaterial *mat = (*materials)[i]->mat;
if ( mat == NULL )
continue;I'm doing some "research" with T3D (have 16 terrain blocks) and noticed with when was messing with painting and re-logging.
About the author
Game developer.
Recent Threads
#2
06/26/2009 (2:53 pm)
Logged as THREED-528
#4
THREED-528 can be merged with THREED-891 as looks like it's the same fix for both.
05/18/2010 (1:04 am)
This one is fixed in r29952 (THREED-891).THREED-528 can be merged with THREED-891 as looks like it's the same fix for both.
#5
If THREED-891 truly is a fix, could someone post a REAL link to this? Because the fking GG website search function is totally incapable of comprehending such a search query, and i do not have endless amounts of time to fritter away trying to get the search to work for me.
05/18/2010 (11:58 am)
I have also been having mysterious multi-terrain block issues, and impatiently waiting for some type of fix for over 6 months now. If THREED-891 truly is a fix, could someone post a REAL link to this? Because the fking GG website search function is totally incapable of comprehending such a search query, and i do not have endless amounts of time to fritter away trying to get the search to work for me.
#6
THREED-891 is the ID for the ticket in our internal bug tracking system. We post those IDs in the threads for the bugs so that the community knows with absolute certainty that we're aware of a bug and are working on it, and also so that other employees/associates know that the bug has been logged if they come across the thread.
05/18/2010 (12:06 pm)
@CayloTHREED-891 is the ID for the ticket in our internal bug tracking system. We post those IDs in the threads for the bugs so that the community knows with absolute certainty that we're aware of a bug and are working on it, and also so that other employees/associates know that the bug has been logged if they come across the thread.
#7
But perhaps if its part of YOUR bug tracking system you yourself could take the 90 seconds or so, and just drop me a link???
EDIT: After all, what is 90Sec compared to the many months i have been kicking multi-terrain block bugs around?
05/18/2010 (12:16 pm)
Yes i know that thank you.. I guess expecting the forum search to FIND a entry mentioning THREED-891 is just WAY to much!But perhaps if its part of YOUR bug tracking system you yourself could take the 90 seconds or so, and just drop me a link???
EDIT: After all, what is 90Sec compared to the many months i have been kicking multi-terrain block bugs around?
#8
Just to give you an idea of how close it is, without getting into specific dates, iT2D 1.4 and TorqueX 3.2.1 are currently being tested and will release respectively, during that time my team will receive 1.1 Beta 2 for testing. Once we run through it here in the lab and make sure it doesn't majorly break for users out of the box then the community will receive Beta 2.
05/18/2010 (12:41 pm)
Here's the link to the thread where it was reported, but there's no fix in that thread. The bug has been fixed for 1.1 Beta 2 which, and I know you hate to hear this, is coming very soon.Just to give you an idea of how close it is, without getting into specific dates, iT2D 1.4 and TorqueX 3.2.1 are currently being tested and will release respectively, during that time my team will receive 1.1 Beta 2 for testing. Once we run through it here in the lab and make sure it doesn't majorly break for users out of the box then the community will receive Beta 2.
#9
Thanks for the time and effort.
05/18/2010 (12:49 pm)
Argh. I was excited at the prospect of smashing this one. Thanks for the time and effort.
#10
08/02/2010 (5:41 pm)
Fixed in 1.1 Beta 2
Associate Tom Spilman
Sickhead Games
I'll have to test with mutliple terrain blocks as its not something i've done yet.