FWIW, he says my older sets work without issue. It still could be me tho', as it's been a few years since I tinkered with GMax and MSTS. :)
The Particulars:
- The loco was originally built in 3DS Max and exported to *.3ds format, imported into GMax and configured further there (materials, material IDs, etc.).
- The materials are those only found in the GMax material editor (TexDiff/OptSpecular25, TexDiff/OptSpecular0, and BlendATexDiff/OptSpecular25/Test Only (for glass).
- Hierarchy:
MAIN (A Unit)
---- BOGIES1
-------- WHEELS11
-------- WHEELS12
---- BOGIES2
-------- WHEELS21
-------- WHEELS22
---- GLASS > (semi transparent, sorted subobject)
--- CHILDOBJECT01
~ snip ~
--- CHILDOBJECT15
(B Unit is similar, except glass object replaced by transparent wire subobject.)
- Level of Detail:
5 LODs (A Unit)
LOD1: 41,026
LOD2: 21,648
LOD3: 8,017
LOD4: 2,387
LOD5: 900
5 LODs (B Unit)
LOD1: 33,505
LOD2: 15,907
LOD3: 5,768
LOD4: 1,681
LOD5: 501
- Model was checked for isolated vertices and/or any on-edge mapping issues.
- ENG and SD file contain nothing special from my previous MSTS items (other than adjustment for length and updated physics).
- ENG file calls out for a common shape (A or B Unit), but otherwise uses a different name than that of the main (locos) or FreightAnim shapes (number boards).
- Each loco uses 2 2048 x 2048 main textures, one 512 x 512 texture, and one 32 x 32 texture with some textures being shared.
- The locos contain a FreightAnim tag in their ENG files, but those files are fairly small (about 2 dozen polys total) and uses a single 512 x 512 texture.
- 3D Cab is currently 38,635 polys (needs a diet), a similar hierarchy as the locos, but contains only one LOD.
- Problem PC Specs: Win 7 Home Premium 64-bit, Intel Core-2 @ 2.40GHz, 15.0 GB, nVidia GT630 (2Gb).
- My PC Specs: Win XP Pro, Intel Core-2 @ 2.93GHz, 4 GB, nVidia GTX275 (2Gb)
I tested the sets on the current and testing builds (and previous two builds) without issue, and I see no errors reported in the OpenRailsLog. Is there something I'm overlooking? I didn't see any follow up to the above posts, what the problem might have been, or even what to fix. :huh: