Yandros on 23/8/2016 at 14:24
Could it be in the FMSel and NDL installs an EP or mod pack is getting enabled that replaces the table with a similar model that's rotated 90 degrees? Other than that I'm at a loss.
R Soul on 23/8/2016 at 15:02
Neither FMSel nor NewDarkLoader install any mods*, just the FMs, but they can disable mods for specific FMs. Neither tool disables anything by default, so you'd know if you'd done it.
I've been trying to think of an explanation involving mod_paths and uber_mod_paths and priorities, but nothing I've come up with explains why it looks fine in Dromed but in game. The closest I got was that you unknowingly installed a custom table into your own FM, but you also have the HDMod or EP2, which each have the correct table model. A Darkloader installation would put the files in 'resname_base' (low priority), whereas NewDarkLoader puts in in 'FM dir' (second highest priority). The Dromed screenshot only makes sense if that Dromed is in your Darkloader'd folder.
Try searching your T2 folder for table.bin and see how many you find.
*Well, NDL can install special 'fix files' but you have to set them up yourself so you'd know if you'd done it.
Yandros on 23/8/2016 at 15:59
I didn't mean to imply that FMSel or NDL install mods; when I said "in the FMSel and NDL installs an EP or mod pack is getting enabled", I meant "in the FMSel and NDL install folders an EP or mod pack is getting enabled by having a different config or modpath setup".
R Soul on 23/8/2016 at 16:09
I see. I misread your post.
Steele on 23/8/2016 at 16:21
Those definitely look like two different tables. The texture is different on the first one: more rough and it has blackened feet. Second table is cleaner but less detailed. Maybe an FM you played on one install didn't get cleaned up all the way, or you have a mod in there.
ZylonBane on 23/8/2016 at 18:20
Why do you have runtime object shadow set on the table? There does not appear to be anything in the scene that it would affect.
nightshifter on 23/8/2016 at 23:23
@R.soul, again thank you for pointing me in the right direction.
proved there was a table.bin in my objects folder ( in my defence, it was redleaf who placed hunderds of objects in that folder with all her custom goodies:joke: ;))
renaming it solved the problem. now my tables are normal again.:thumb: ( so that bin file goes out for the next beta:ebil:)
still don't understand why the table.bin made the ( looks of the) table turn 90 degrees. the physical dimension were not turned. I noticed that the ( turned) table blocked me as if he was placed original.
R Soul on 23/8/2016 at 23:52
Quote Posted by nightshifter
@R.soul, again thank you for pointing me in the right direction.
You're welcome :)
Quote:
still don't understand why the table.bin made the ( looks of the) table turn 90 degrees. the physical dimension were not turned. I noticed that the ( turned) table blocked me as if he was placed original.
It's just that the vertices are in different places. In some object program, the original was made longest on the Y axis. redleaf's table was made longest on its X axis. The physics model is independent of its shape. Dromed will try to match it by default but if you change the 'visual' model, existing physics models won't change. Tables actually have the phys model set in the hierarchy so that objects can slide under it, whereas an auto generated model would match all the dimensions.
