Page 1 of 1
bin file won't save

Posted:
Sun Apr 07, 2019 5:41 pm
by Squirrely7
I've installed RW Tools, and set to run as admin.
I opened all files to read / write
I'm trying to change the coupler coefficient to eliminate the stretching issue. But when I save, the "000000000000" won't save to the .bin file. If I reopen to check, the native values are back.
I'm running Train Sim19. The program seems to be for RW18. Not sure if this is the issue.
v8.0.26
Re: bin file won't save

Posted:
Sun Apr 07, 2019 6:21 pm
by mikesimpson
Hi Squirrely7,
1. Which version of RW_Tools do you have? Latest on my site is v8.0.35
2. Where is your copy of Steam and TS2019 installed? I suspect you may have Steam in c:\Program Files (x86) - If that is the case then due to security settings in Windows 10, 3rd party programs can't write to that folder and so RW_Tools can't write the .bin file into that folder.
3. RW_Tools should work on any version of Train Sim since the original Rail Simulator which I first wrote it for in 2007/8
Mike
Re: bin file won't save

Posted:
Sun Apr 07, 2019 6:23 pm
by buzz456
Ver 8.0.29 is current but that's not your problem. Probably all those zeros are out of parameters.
Re: bin file won't save

Posted:
Sun Apr 07, 2019 11:42 pm
by Squirrely7
I save all my files to my data drive. I created an App folder that contains steam and RW Tools. The OS is on my C drive.
I did figure it out, I was changing the wrong portion of the field for editing. Once I changed the value at the end, the encoding number played along.
<SpringCoefficient d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</SpringCoefficient>
<Damping d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</Damping>
Also, I checked the CMP spongy coupler fix file for comparison.
<SpringCoefficient d:type="sFloat32" d:alt_encoding="00000000004CCD40" d:precision="string">15000</SpringCoefficient>
<Damping d:type="sFloat32" d:alt_encoding="000000000070C740" d:precision="string">12000</Damping>
As you can see, it is nothing like what I entered. Should I use these values?
I cannot get the couplers fixed on the ES44DC from the Stevens Route DLC. I extracted the .ap file from the BNSFPack01, went in and found the coupler folder, changed the spring coefficient and dampening to 0. This made no change. The couplers still pull out from the loco. Also, I didn't see an option to re-zip the files.
I'm stuck
Re: bin file won't save

Posted:
Mon Apr 08, 2019 7:34 am
by buzz456
There is no reason to re-zip anything. TS reads the stuff outside the .ap if there is anything there. It only reads the stuff inside the zip file if there is nothing outside. I would go look in the bin file to see what coupler the loco is looking at to make sure it is the one you are editing. Often these dependencies get used from somewhere other than where they should be.
Re: bin file won't save

Posted:
Mon Apr 08, 2019 5:00 pm
by Squirrely7
You were correct about the file. I found it in the Stevens Pass .ap file.
Seems as though everything is working. And since the program is using the unzipped folders, can I delete the old .ap files? It'll save me a gig.
Thanks for tall the help!
Re: bin file won't save

Posted:
Mon Apr 08, 2019 7:15 pm
by buzz456
Only if you unzipped the entire .ap. Then you can with no problem.
Re: bin file won't save

Posted:
Tue Apr 09, 2019 9:30 pm
by Chacal
Don't.
The files will take even more space if you unpack the whole .ap file.
Only unpack what you need to change.
Re: bin file won't save

Posted:
Fri Apr 12, 2019 7:59 am
by ChrisOnline
Good form is NOT to unpack and delete the .ap file, but to extract (open and drag out) only the file(s) you need (it will not delete them from the .ap file). Deleting an .ap file is only temporary, as it will reappear once Steam realizes it is missing, and at that point any matching-named files previously extracted will be removed (though empty folders will likely remain)
The best and cleanest discipline is to only have required files outside the .ap file. And for any same-named file outside the .ap file, keep an easy backup to allow reinstatement if/when it disappears. I have a complete "Backup" folder mirroring the full Railworks structure for all edits that could be overwritten, so it is an easy job to just copy back if/when necessary (either selectively, or as a complete job lot)