T3D 1.1 Known Issues

#1 Reserved for workarounds.

Workaround for THREED-1860 - Terrain Painter Causing the Engine to Relight Textures in Scene
1. Run engine
2. Open level
3. Paint down terrain material (should relight)
4. Save level
5. Shut down
6. Run: correct lighting should be used now

Workaround for THREED-1903 - Clean-up of new projects fails, occasionally works
1. Run the generateProjects.bat file in the project folder
2. Wait for project generator to complete successfully
3. Projects should now be regenerated correctly

Workaround for THREED-1886 - Scaling/rotating/translating a decal can lock camera
1. Click on the decal to reselect it
2. Camera should be unlocked

#2 I don't see a problem with .DIF portals anywhere there, or maybe I missed it? because if I didnt, add .DIF's, when going inside a portal on them, all rendering is lost and you can only see the skybox

#3 What happened with THREED-1471?
Reference thread.

I dont see it solved nor listed here.

#4 @siba
I don't see any ticket logged for that. If you can report the bug in then one of the guys will log it. Note that .DIF's have been deprecated in 1.1 though.

@Novack
Odd, that one should have been on there. Looks like I must have removed accidentally when I took off the duplicates of it.

#5 There's a few things missing from that list if we're going to get pedantic. :P

#6 Thanks Scott.

#7 Has anyone reported these;
1. PhysX streams can not be inherited, they must be stipulated in a datablock or else the multiactor fails to be created (it's odd that you can make a new datablock in the datablock editor only for the datablock to fail on game reload.)
2. 'Player collision debug rendering' doesn't work in the physics builds ?

//EDIT#1
3. editing a projectile datablock using the datablock editor and then saving it; causes crashes.

//EDIT#2
4. Editor settings for the shape editor background color doesn't work properly nor does the change get saved for the next run.
5. Editors still get stuck on each other: Using the shape editor for certain things causes it to no longer be switched out for another editor to be used. You have to close the editor system and reopen it in most cases.
6. I mounted an object to another object, the cs file was written but failed to complete the correct file data for the mounting; (I also had to play tricks to get it to allow me to save.

singleton TSShapeConstructor(HangingLightDts)
{
   baseShape = "./hangingLight.dts";
};

function HangingLightDts::onLoad(%this)
{
// WHERE IS THE STUPH? THIS IS NOT GOOD!
}

7. The Shape editor fails to allow me to save an edited shape after I do anything besides moving nodes or creating imposters. ..pfff.
FIX: leave the SaveShape icon active 100% of the time.


P.S. This post will continually grow as long as I find issues that are worthy of noting.

#8 @siba: We found a workaround for the DIF / Zoning issue...

1) Use the World Editor to "Export Interiors as Collada", this will create .DAE versions of your Interior DIF files.

2) Delete your DIFs from the mission, and replace with the new DAEs. They may need to be repositioned slightly since sometimes they don't seem to drop in at the same place even when copying and pasting the old DIF position co-ordinates.

3) Make sure "Visible Mesh" is set for the collision, and that "Allow Player Step" is set to "1".

Now the objects that were your DIFs will render properly when your player is within the zone, and be culled out when he is outside the zone.

In our case, all our floors and walls were DIF files, so this was a big problem until this simple workaround was found. Now we are simply converting all the DIFs in the game to DAE and bringing them back in, prior to doing all the zoning for the mission. So far so good, rendering and culling appears to be working as it should.

#9 that's a long list of things still needing to be done..

specifically things like:

THREED-1689 - Taking Damage with a Player Mass Value of "1" will Cause the Engine to Stop Responding

and

THREED-1497 - T3D vsync broken

are these issues still open?? i mean i know it's only $100 bucks n all, but seriously?

#10 These known issues is fixed in T3D 1.2?

#11 Changelog here

#12 Oops. Misread this as the 1.2 known issues list. Sorry about that!

- Dave