|
Author
|
Topic: freeze on plane crash
|
bjorn
Pilot
|
posted 04-24- 08:50 AM
  
The P47 has lately started freezing SDOE when it crashes. Not always, but often. When it happens, it's when the P47 is blown to pieces.I've encountered this before, and then it has always either been illegal inertia vectors DOF property list errors. Now I've gone through every property in the P47, and I cannot find it. It is of course there, somewhere, but it's something I'm not looking for. Those of you who have experienced, found and corrected similar freezes, what is it that has been wrong?
_
/Bjorn. IP: Logged |
mposis
Pilot
|
posted 04-24- 08:55 AM
If a damaged lod with a bad polygon gets displayed it can cause a crash. You have to check all the damaged lods for bad polygons. Hopefully the LODs does not have too many polygons or it will take a lot of time to find.IP: Logged |
bjorn
Pilot
|
posted 04-24- 09:02 AM
Ouch, that hurt. How would one define a bad poly? Wrong number of vertices and/or illegal flags. Is there anything else that can be wrong?
_
/Bjorn.
IP: Logged |
jedi
Pilot
|
posted 04-24- 09:30 AM
You could go into OPS and remove the "obHidden" property from one damaged .lod at a time. If that's the source I would think the game would crash on startup when you hit the bad one. I'd start with the inner-wings, as they are pretty strong and likely to only show up in a big boom.If you do find one, you may be able to just replace it with a "mirrored" version from the opposite side (if there's two of em and only one bad). This sometimes messes up the normals, but probably not the end of the world for a damage .lod.
------------------
--jedi-- [This message has been edited by jedi (edited 04-24-2000).] IP: Logged |
mposis
Pilot
|
posted 04-24- 09:33 AM
I think this is the reason for most of the CTDs when planes explodes or gets damaged. It is hard to fix becuse you don't know what damaged lod gets displayed.To fix it you have to do it in a 3d program. Sometimes the vertices of the polygons are not in the correct order. You can usually fix this by reversing all the normals and then reversing it again. You can also try triangulating all polygons though this will increase your polycount. If it doesn't get fixed you have to find the particular polygon and replace it with a new one. You can also create all the damaged lods from scratch and pray you don't duplicate the problem. I have seen this problem on almost all the projects I made. Sometimes it is not even the damaged lod. When I view on object I am building externally and move the viewpoint around it, I can get a CTD if a lod with bad polygons gets displayed.
IP: Logged |
JT
Pilot
|
posted 04-24- 10:48 AM
For whatever it's worth, when I first added the damage LODs I made it so they were all visible. I added the obHidden property after they were all in place.
IP: Logged |
bjorn
Pilot
|
posted 04-24- 10:52 AM
Bleah, this sounds like a lot of fun.
_
/Bjorn.IP: Logged |
mposis
Pilot
|
posted 04-24- 11:27 AM
I guess now you know how fun it is to do 3d models for SDOE. JT, I think if the bad polygon is hidden behind a good one then it may not cause a CTD.
Maybe you can hide all the regular lods and only display the damaged ones. View it externally in SDOE and move the view point around and see if you get a CTD. Maybe the problem is not even bad polygons. [This message has been edited by mposis (edited 04-24-2000).] IP: Logged |
FSIC Messageboard
UBBFriend: Email This Page to Someone! 
