Wake up Editor

#1 One of the scripts you replaced probably loaded some of the resources for the TLK dialog. Go back and make sure everything TLK needs is being loaded.

B--

#2 Didn't replace anything - just copied my folder to the example folder.

There must be some differences in the missions/Srcipts.

#3 Hi Juergen,

Does the Torque Lighting Kit menu appear in the Mission Editor? When you press F12 or select the menu item does it generate an error on the console?

-John

#4 Let me phrase that better.. One of the scripts you are using now might not be loading some of the TLK resources. If you are using an editor like CodeWeaver or Torsion, just do a project wide search for TLK related script files, and make sure your scripts are loading everything needed for the TLK dialogs.

B--

#5 Hi John,

the menu is there, but pressing F12 or selecting the menuitem dosn't start the editor.

I can seen that the TLK is working because the ambient colors are more bright (and I can adjust them).


Maybe I did overlook something but in the guides there is no advice that I have to

adjust scripts. (Maybe I have to add the keybinding for F12?)

To make it clear I don't want to recompile - I just want to use your precomiled Torque with TLK (1.4)

Thanks for your help

#6 The TLK is not only a modified EXE. It also needs some script changes to fully work (i.e: the lighting editor is 100% implemented in script). And yes, the docs do tell you to do a merge of the scripts to your own.

Your copied folder will not load the TLK scripts by default. You need to add the TLK-relevant changes to it. As mentioned before, do a search on the TLK example scripts to find out what you need to change.

#7 Hmm,

maybe I overlooked it, but where it is explained in the doc's how to search and merge?

I which scripts?

Is winmerge used to to compare?

#8 Ah, I misunderstood your original post. If you've copied a whole new mod directory into the "example" folder then you need to add two or three TLK code changes to make the Light Editor available.

The Developer's Guide has all the info you need, it covers the directory structure, all of the changed files (including scripts, which are the only files you need to check out at this time), and how to use WinMerge.

If you haven't already, you should become familiar with all of the TLK documentation, it saves a lot of questions down the road.

#9 Thanks John,

will look into it.

Just thought the developers guide is to for those who will compile the TLK again.