S3D v9 bug report.
When importing a .dat file with a nod that has an embedded 3D model, SH4 will CTD when the .dat file with the new 3D model comes into visual range.
Background
I have used S3D to edit / change / import .dat files for both RSRDC / OM for a while now. I have always been able to import nodes with 3D models in the past without problem. With v9 I’m have a “re-creatable on demand” CTD when I attempt to add nodes with 3D models in them.
The following test case is the procedures I use for the importation of nodes with 3D models and have use these steps with older versions of S3D without problems.
- create working directory
- copy NDD_Clemson.dat & NTR.dat into the working directory
- launch S3D and open the NTR.dat file
- select and expand (7) Node – NTR then select and expand (12) Node – NTR_B
- select (21) NTR_barca_03 and remove “parent id” so that the node is now is a “standalone”
- Repeat step last step with NTR_barca_06.
- select (7) Node – NTR and delete
- Keep “empty” nodes 3 & 5 as they are required “material” nodes for NTR_barca_03 and NTR_barca_06 and delete the remaining “empty” node.
- Select and execute “Remap ID’s” on the file.
- save NTR.dat then use the “save as” option to save the file with the name zzz.dat
- delete “AuthorInfo”, Start, End, Unknown chunk, Index and Eof from zzz.dat
- save file zzz.dat
- open NDD_Clemson.dat
- select (7) Node – NDD_Clemson
- use the right mouse button to select “import”, then dat.file
- Select zzz.dat and select yes when ask to import 10 chunks.
- Save file.
- backup original NDD_ Clemson.dat in SH4, the copy in new file
- create test mission under “Single Missions” with the Clemson Class DD. Ensure own sub is at least 75km from Clemson Class DD.
- launch SH4 and then test mission
- head sub to the Clemson Class DD location.
- When own subs is with in range of the Clemson to be seen, SH4 will CTD.