Atomic Systems

ChrisBarnes wrote:

prairie4566 wrote:Does anyone else have a Schema Reading Failure error with the Blueprint Editor?

Does this fix it?

EDIT -' No.'

Steam\steamApps\common\railworks\Temp\BlueprintSchema

You're not the first person to have this problem and I'm sure you wont be the last either. Delete the file "BlueprintSchema", found as shown above, then try the blueprint editor, it should work.

Chris

...still no go

"This game is currently unavailable.
Please try again at another time".

Usually a sign, that an update is in progress, but that is not the case.
???

Go into C:\Program Files (x86)\Steam\steamapps\common\railworks\ and double-click "railworks.exe". This will not bring up this message.

So the audio issues are still there...

thetrainfan wrote:Go into C:\Program Files (x86)\Steam\steamapps\common\railworks\ and double-click "railworks.exe". This will not bring up this message.

Thanks, but no such file is present there. Time to verify game files.

trainsmit wrote:"This game is currently unavailable.
Please try again at another time".

Usually a sign, that an update is in progress, but that is not the case.
???

I've had this with other Steam stuff too, maybe their servers are overloaded?

nelson wrote:

trainsmit wrote:"This game is currently unavailable.
Please try again at another time".

Usually a sign, that an update is in progress, but that is not the case.
???

I've had this with other Steam stuff too, maybe their servers are overloaded?

As I said, click the RailWorks.exe application in your RW directory and it will load up RW. Always has done for me and others I know of.
Its normally a high amount of traffic using that game, but do the way I suggested and you'll be fine.

With regards to the blueprint schema error I think the method I use when i get it off the top of my heads was to do the following:
1. Go to the temp folder in the railworks directory then delete its content. (I'd advise making a temporary backup )
2. go to "C:\Windows\System32\Temp" and delete the content inside of that.
3. Load a scenario in railworks once its loaded quit the scenario then shut the game down that in theory should fill the temp folder.
4. Copy the content of the temp folder into the temp folder in "C:\Windows\System32\Temp"
5. try blueprint editor, if It don't work I've done done one of the steps in the wrong order
regards
Edward

Having trouble editing .GeoPcDx files using RW_Tools - getting a SERZ message saying it can't 'recompress' the file on save (.BIN files are fine)?

Could this update of SERZ.EXE be causing this as I am sure I could edit these before?

Traveller54 wrote:Having trouble editing .GeoPcDx files using RW_Tools - getting a SERZ message saying it can't 'recompress' the file on save (.BIN files are fine)?

Could this update of SERZ.EXE be causing this as I am sure I could edit these before?

I've had this happen with several .GeoPcDx files before the TS2013 update, and it is still happening - from memory it has affected the Black 5, and updated versions of the 43, 47 and BR294. Looks like RSC have changed something in the shape file that no versions of serx.exe released to the public will re-compress.

Seems to be a file size issue.

From a thread in the RW_Tools Area:

Acorncomputer wrote:I seem to recall Mike Simpson saying that serze.exe can only deal with files of a certain size. Perhaps if you trawl his posts or do a UKTS search you will be able to find the relevant post.-
Thanks Acorn that seems to be the reason - the .Geo file I was trying to edit was 4752Mb. I have gone down the sizes and it looks like 1999Mb is about the upper limit! HexEditor here I come )

alanch wrote:

Traveller54 wrote:Having trouble editing .GeoPcDx files using RW_Tools - getting a SERZ message saying it can't 'recompress' the file on save (.BIN files are fine)?

Could this update of SERZ.EXE be causing this as I am sure I could edit these before?

I've had this happen with several .GeoPcDx files before the TS2013 update, and it is still happening - from memory it has affected the Black 5, and updated versions of the 43, 47 and BR294. Looks like RSC have changed something in the shape file that no versions of serx.exe released to the public will re-compress.

I recall reading very recently that these GeoPcDx files have some form of protection applied, and that would be the reason that current SERZ.EXE versions can't recompress them. Same statement said that older SERZ.EXE versions might be able to write files - although they might have other issues, or incompatibilities.

I can't remember where I read this exactly, but it was some RW_Tools related documentation I believe.

tnleeuw01 wrote:

alanch wrote:

Traveller54 wrote:Having trouble editing .GeoPcDx files using RW_Tools - getting a SERZ message saying it can't 'recompress' the file on save (.BIN files are fine)?

Could this update of SERZ.EXE be causing this as I am sure I could edit these before?

I've had this happen with several .GeoPcDx files before the TS2013 update, and it is still happening - from memory it has affected the Black 5, and updated versions of the 43, 47 and BR294. Looks like RSC have changed something in the shape file that no versions of serx.exe released to the public will re-compress.

I recall reading very recently that these GeoPcDx files have some form of protection applied, and that would be the reason that current SERZ.EXE versions can't recompress them. Same statement said that older SERZ.EXE versions might be able to write files - although they might have other issues, or incompatibilities.

I can't remember where I read this exactly, but it was some RW_Tools related documentation I believe.

I have tried to use a SERZ file that came with the original TS2012 without success?

Hi Traveller,

I think 'older' was referring to the SERZ.EXE file that came with original TrainSimulator, from years back.

tnleeuw01 wrote:Hi Traveller,

I think 'older' was referring to the SERZ.EXE file that came with original TrainSimulator, from years back.

Ahah, even older than the one I tried then - need to dig out my 'older' backups then!!

Onwards ........