Autofrob signs stopped working with Darkv123

redleaf on 12/9/2015 at 08:57

For every mission in progress that I updated to the latest New Dark, my auto frob signs and books have stopped working. It's probably something very simple that I'm overlooking, but I can't discover the problem. Any ideas out there? :confused:

I checked that my text are strings, and not text. I don't even get the message that "there should be a book here but DromEd can't find it".

I installed v123 using the installer, and am using NV's toolkit. I believe it is the latest one.

Thanks for any help. :thumb:

redleaf on 13/9/2015 at 08:51

Hello? Anybody?

fibanocci on 13/9/2015 at 09:02

What's a "auto frob sign/book"?
Onscreen text with special scripts like tnhscript/NVScripts?
What about the other books?

Yandros on 13/9/2015 at 15:05

I agree with fib, describe to us how you implemented the autofrob signs (which scripts and settings on the signs) and we can go from there. Also, if you revert NewDark to 1.22 does it start working again in the same version of the mission?

redleaf on 14/9/2015 at 06:50

Hi guys. Thanks for the replies.

The missions giving me trouble have been upgraded to v123. When I go to a backup drive and load the last old v210 missions which are in their v210 DromEd folders, the signs work fine (white text on screen when frobbed).

I made each one by creating a marker. Properties are:
Render Type: normal
Controls: location, rotation
Model Name: plaqb
S>Scripts = StdBook
Engine Features>Frob Info>World = Script
Book>Text = whatever

I can open the v123 missions in version 210 Dark, though I get warnings about them, and nothing seems to work correctly, including the signs

The v210 mission signs all work perfectly when they are opened in v210 Dark.

I noticed there is an intrinsic readable requiring a design note rather than entering the name of a string file in book>text. Is this what I should be using to create the white text now? I have no idea how to write the design note if that is the case. Just typing the text into the box does nothing.

Really trying hard to figure out what I'm doing wrong here.

fibanocci on 14/9/2015 at 07:08

For testing, I did the same setup. It's working just fine in Newdark 1.23.
Did you load gen.osm?

redleaf on 15/9/2015 at 10:45

Hi Fib - I re-acquired the latest scripts to be sure. Maybe something wrong with my copy of gen.osm? I will download again, but from a different source. Thanks for the suggestion!

redleaf on 15/9/2015 at 10:58

Okay - tried a different gen.osm file. Same problem. Weird, eh? I did find a nice telliamed page describing the functions of the different scripts we use. Really nice stuff to know about!

Maybe I'll try re-installing NewDark 123 all over again.

fibanocci on 15/9/2015 at 12:24

I don't know what's wrong.
Here's a small demo in ND 1.23 with the (working) setup that you described. The only script required is gen.osm

(http://www45.zippyshare.com/v/QMZMgjJ6/file.html)

redleaf on 16/9/2015 at 01:59

I think I needed the str files in order to read the text. But I entered the file names of two of my own str files. I got this error messagewhen frobbing the sign.

Inline Image:

http://i251.photobucket.com/albums/gg309/redleafpix/redleaf_sign_error_zpskta3gefz.gif

No white text on screen.

Could I have a corrupt gen.osm? I've tried copying that script from older backups - no change in behavior. It's me, isn't it? DromEd just HATES me, I know it! :p