john9818a on 25/9/2019 at 14:18
:rolleyes: What I need to do is find out why the vhot is shifting away from the correct location. I'll withhold any more posts unless I can for sure tie this to a dromed error. :)
voodoo47 on 25/9/2019 at 14:22
there is pretty much zero chance of this being a Dromed issue - basically, you need to generate the object in a way that is fully compatible with Dark.
I also find it extremely unlikely that this actually worked fine with 1.25 - you just didn't notice the issue, most likely.
john9818a on 25/9/2019 at 20:49
I designed the sconce so that when doused it would produce a small wisp of smoke at the wick. Since I was looking on purpose during design time I doubt I would miss it until now when I was looking for something else. Either way I won't worry about it unless I post the object at the Object Repository.
voodoo47 on 25/9/2019 at 21:21
it'd be very easy to test, all you need are the old exes.
john9818a on 26/9/2019 at 09:17
All my exes live in Texas :joke: sorry I couldn't resist :)
I tried to convert the bin back to 3ds so that I could look at it in Anim8or but eto3ds gave me an error & wouldn't generate a 3ds file. I also tested the same object in a smalk test mission and it put the flame in the same odd location right away, so there is something wrong with the object.
Unna sorry to hijack your thread.
voodoo47 on 26/9/2019 at 10:38
well yes, as I've said, the problem is with the model, so it will behave identically no matter the mission. ask Olfred for a fix if you can't do it yourself.
or you could maybe just attach to the object itself instead of a vhot? should work properly for most scenarios (for example, I had to use vhots for interactive candles, as the wick locations change depending on what model pack is used, but if that weren't the case, I could just use the object with an artificial offset).