Hack wrote:Except for the mods to the PRR unit, all were done by me, but I recall both wipers work on my ATSF version - I'll see about what went wrong with the others.
Machinist wrote:Sam,
The ammeter of the four built-in liveries (UPRR, SPRR, DRGW and Warbonet) are working fine, no problem at my side. Which is broken is the left wiper, in all liveries. They are in the \Assets\Kuju provider folder, is that you mean by Kuju F7?
Cheers,
Doc.
Kali wrote:The F7s that shipped with RW3 are the 3DT ones. All of 'em have only one wiper though, even the warbonnet one... and that one has a broken ammeter, I just noticed. File dates are all from RW3 release so I'd assume it got the same treatment.
Machinist wrote:BTW, and off subject, are you planning a new version of your ultimate "Cajon Pass: ScaleRail" after SP-1? Your mod route is awesome, but it didn't catch (when re-installing after SP-1) all the new BSB features added post update
Samwolf wrote:Question, is there any other file, like the engineScript.lua or simulation file that would control the ammeter animation? I use a "customized" enginescript.lua for a lot of my engines, the Kuju F7's being one of them.
Machinist wrote:Samwolf wrote:Question, is there any other file, like the engineScript.lua or simulation file that would control the ammeter animation? I use a "customized" enginescript.lua for a lot of my engines, the Kuju F7's being one of them.
I've started to do my own changes in the .lua files, but I try to keep the original settings and add my new features. Some .lua's I looked in are transmitting information to consists and changing smoke's rate according to RPM changes.
Just beware, as far as I noticed and tested for now, is that RSC uses the same scripts name for all the same engines under the same provider folder (ex. Kuju). So if you changed the .lua for F7 Livery X but kept the original for F7 Livery Y (both Kuju's engines), once they have the same name the game will load both .lua's but will prevail one of them (the latest loaded into memory). I noticed that because I changed the .lua for the SD40-2 Default (or SD70) however when I gone play a scenario with other liveries, all of these other liveries were using the changes I did only for the .lua of Default livery.
So if you are going to use your own .lua, I suggest:
a) to name it differently and change the engine's .bin (in the very bottom section of bin file) to match the new name (that's the best option IMHO);
b) or, if existing, replicate your .lua into all other liveries folder under the \Assets\Kuju folder, for example.
Doc.
Return to Problems and Peculiarities
Users browsing this forum: No registered users and 4 guests