latimers wrote:"some of us that make changes need to figure out what to do as we go forward."
Totally agree Buzz and I wasn't trying to imply otherwise. As I said to Mike Simpson, if this .ap system is really designed to stop people modifying their TS2014 (as yet not proven), then it's up to "us" to figure out a way to get around it (legally of course).
What's puzzling me is why they implemented the .ap system. The only advantage I can see is that the Steam verify has one file to check instead of many small ones. After that there doesn't seem to be an advantage. If the .ap file needs updating for some reason then it's going to be a big download instead of a few smaller ones. It looks like it wasn't designed to help users retain their modifications (not something RSC would see to be in their interest anyway, therefore unlikely to do it for that reason). So what advantage can there be in it to RSC?
Phillip, when you changed the files and put them back in the .ap file, did it later re-download the whole .ap file?
Bob.
mikesimpson wrote:To stop users modifying anything at all in TS2014 - If you can't modify your scenario files with something like RW_Tools, then you have to purchase any missing items from RSC. This has the added advantage to RSC of reducing service calls from people who damage their setup by bad editing. Recent texture file format changes have cut down the number of re-skins as well, thus forcing users to purchase new locos (with just livery changes) again from RSC.
Mike
PapaXpress wrote:To answer Peter's question, yes you can read a zip file as if it were a file system. An example of this is when an anti-virus software scans your .zip, .rar. and .7z files content.
mikesimpson wrote: ... the only reason I can see for the use of the .ap files is:-
To stop users modifying anything at all in TS2014
wacampbell wrote:Railworks provides developers with tools, documentation and support for extending the program with addons. Even as of their most recent update, they provided new and improved developer tools, an indication that they continue to support addon developers. Addons developed with their tools and following their guidelines don't get damaged or break the program during updates.
latimers wrote:"We are a software studio we do not handle distribution of content or indeed any transactions, that is what steam does, in fact even if we wanted to access your steam account for any reason, we could not, only steam has the access.
You are obviously an intelligent man, I will leave it to your judgment, who do you think will be better placed to resolve your problem?
Especially a problem that involves the distribution and installation of software content?"
So RSC is denying any knowledge of the .ap file system. I find that very hard to believe.
Bob.
mikesimpson wrote:Where did you find documentation for the developers tools?
There has never been any documentation even for the use of Serz.exe,
and virtually no documentation for the Blueprint Editor
It was only the hackers on here and other user forums who discovered ....
wacampbell wrote:The RSDev tools package, available here ( http://www.railsimulator.com/support.php ) has over 50 doc files describing the process.There has never been any documentation even for the use of Serz.exe,
Its not documented because its an internal utility used by the Blueprint Editor. The developer never needs to run it directly. I've built many addons for Railworks, and never have needed to serz anything.and virtually no documentation for the Blueprint Editor
There's enough info in the RSDev tools package to get started.It was only the hackers on here and other user forums who discovered ....
But thats the point. The Assets folder contains private internal data for the program. There has never been any documentation for it because its not meant to be changed by the end user or the developer directly. The changes that various community members have made are great, but those changes were done without complete knowledge of the spinoff impacts wrt caching, future upgrades that railworks might want to do, etc. Nowhere does Railworks ever say that a developer should go in and hand edit .bin files in the Assets folder. Clearly the end user can do what they want, and some of these unofficial mods are very enticing, but they are always going to be fragile and should be discouraged, or at least provided with warnings about the risks of using them.
I think its time to shift the community away from hacking the Assets folder, and towards development using the BPE and the guidelines in the RSDev package.
Return to TS 2014 - Train Simulator
Users browsing this forum: No registered users and 0 guests