What are .out files? New to TS2013?

[chrisell]

Just getting ready to package up my first update and I noticed that a bunch of new files have appeared with the extension 'out'. Looks like one for each simulation and wagon script. Seems like the LUA files generate them. I can't tell if they've been created in-game or are temporary files left over from crashes in the blueprint editor.

Are these needed for redistributing engines and wagons or is it safe to delete them?

[shanyiqua]

from exported assets you can delete xml, tgt, cost, out files.

[chrisell]

from exported assets you can delete xml, tgt, cost, out files.

Thanks. I knew about cost, tgt and xml, but I'd never come across out files before.

[MaikG]

.out is just a compiled version of the .lua (before it was .luac)

[chrisell]

Important note : you CANNOT delete the .OUT files any more. The new blueprint editor does NOT dump the LUA files into the exported Assets folder any more, only the OUT files. If you delete them, especially on trains and wagons, you end up with no script functionality.

The question now is this : did TS2012 read the .out files or the .lua files? If it only read the .lua files, then anyone building projects using the new blueprint editor isn't going to be able to have users with TS2012 run them ....

[nobkins]

I believe it read both. If the out was present then it used it. Otherwise it used the lua.

Not 100% certain though. Just what I have picked up along the way. Hopefully someone else can confirm.

[shanyiqua]

I believe it read both. If the out was present then it used it. Otherwise it used the lua.

Not 100% certain though. Just what I have picked up along the way. Hopefully someone else can confirm.

I confirm, exactly that happens. .out is the primary source, .lua is the secondary.

[chrisell]

Well I have some news in this area - if you don't provide the LUA files, none of your rolling stock works in TS2012.
I just found this out the very, very hard way.

So if you use the TS2013 blueprint editor, your rail assets, if scripted, I guarantee will not work in TS2012 just using the .out files.
You MUST use the old blueprint editor, OR manually provide the LUA files after the fact.

[Kariban]

You can just rename the .out files with a .lua file extension. TS2012/RW3 reads compiled lua just fine. That will work for 2013 also.

[chrisell]

You can just rename the .out files with a .lua file extension. TS2012/RW3 reads compiled lua just fine. That will work for 2013 also.

Are you sure? That would make life a lot easier because I could do that in my installer script. But I could swear I tried that with one of my customers and the ONLY way we got it to work in TS2012 was uncompiled LUA

[Kariban]

I have used compiled lua in 2012 ( in RW2, even ). I do remember people having issues, but I've definitely used it.

[chrisell]

I have used compiled lua in 2012 ( in RW2, even ). I do remember people having issues, but I've definitely used it.

It's a pity none of the luadec programs work on Railworks LUA files or I'd just decompile the .out file into .lua as the final stage in my installer.