Just out of the blue, mid-scenario, the F1 key stopped working. Additionally, after this occurred, the same save caused a frozen game. Twice. In the exact same spot. The F1 issue is now endemic. Do I need to do a file verification, or is there a solution to this? BTW, the SD cache file in Content was not the issue. The task list can still be brought up via the HUD, but not via F1.
Cyclone, can you tell me in which scenario that happened? I remember I had lost keyboard control in one of the East Midlands Coal scenarios, had to quit via TaskManager.
Of course it's not the end of the world. But Cyclone and me are perfectionists. And in that East Midland Coal scenario, no keyboard input was accepted.
If you wait for perfection you might wait a long time, it doesn’t hurt to ask for it though (ancient Chinese proverb, I just made up).
Before we get philosophically lost... It was an Edinburgh-Glasgow scenario. coincidentally, starting at Edinburgh, going to Glasgow on the 15:28 or so express. Ran in 64-bit.
I will check that. I've learnt a lot from that BLE issue. Small mistakes in some blueprints can, but don't always have to, lead to weird behaviour. Btw I found a lot of odd stuff in the G-Trax assets. Wrong audio and occlusion paths, double IDs and a lot more. The number of fixed/adjusted files for all of my content is now 1450!
So I figured out the F1 key issue. The key is literally not working. I just tested using the onscreen keyboard and could hook up a portable one I use for the laptop to further test, but since the onscreen brought up the help function in Windows and my actual one didn't, I think I have to buy a new $20 keyboard soon... Now for why the scenario is freezing in the same spot. Twice. I wonder if 64-bit is related in a 32-bit scenario? I'm not getting to the INT DIVIDE BY ZERO error, it just freezes.
Again, Edinburgh or South Wales, what is this scenario again? There is no 64-bit reference in any scenario. Just memory requirements due to asset numbers. But a fault can lead to different consequences in 32 and 64 bit exe.
The scenario that froze twice in the same spot, I said, is the Westbound Express. Maybe the Class type would help; it's a Class 170 scenario included with the E-G route, 15:28 start time IIRC. I may give it a shot in 32-bit.
I'll just try it (Career). I take it you don't use savegames. 15:42, on my way to Falkirk, everything's cool.
I did, but I also tried both moving to that point and then from a savegame generated along the way. Savegames are helpful during recording in case, you know, the game freezes. LOL
Yes but using savegames you cannot always find the cause for an eventual crash, because they might screw it up. To test a scenario you need to do a full run in one session. Do you know when the freeze is approximately expected to happen?
In both cases, it was between Falkirk High and Croy. I was driving beyond the Cumbernauld exit passing underneath, and the exact mileage remaining differed ever so slightly. 3.50 on the first run, 3.52 on the second. This is approaching a left turn. In both images above, I was on a frozen screen on 64-bit Train Simulator. The second came from a savegame at Falkirk High. torf, I can possibly send you the save file to test it if you have a clean run. I also know savegames can be a problem. City Express on London-Brighton says hi.
I just played it and had a trouble free run in 64bit. There's just one thing I can say. It is not always best to update your drivers, I've had nVidia drivers screw up some games in the past and stuck with one revision that worked perfectly.
Hmm. I may have to give it another try. Here's the save if you want to try and see if it causes problems.
Your save game is broken. Now it freezed at the exact same spot you reported, whereas I had no trouble running it in one session. Don't save! And that score is a bad sign of some kind of overflow. Edit: Code: <cScoreModel d:id="13264229"> <CurrentScore d:type="sInt32">400</CurrentScore> <UserId d:type="sUInt64">76561198256537172</UserId> <Score> <cScoreInstance d:id="164734146"> <Points d:type="sInt32">200</Points> <Reason d:type="cDeltaString">eTimelinessEarly</Reason> <Location d:type="cDeltaString">Waverley Platform 7</Location> <Time d:type="sFloat32" d:alt_encoding="000000803BBF5C40" d:precision="string">114.988</Time> <Detail d:type="cDeltaString">On Time</Detail> <MD5 d:type="cDeltaString"></MD5> </cScoreInstance> <cScoreInstance d:id="148416676"> <Points d:type="sInt32">200</Points> <Reason d:type="cDeltaString">eTimelinessEarly</Reason> <Location d:type="cDeltaString">Haymarket Platform 4</Location> <Time d:type="sFloat32" d:alt_encoding="00000080FAB78040" d:precision="string">534.997</Time> <Detail d:type="cDeltaString">On Time</Detail> <MD5 d:type="cDeltaString"></MD5> </cScoreInstance> </Score> <MD5 d:type="cDeltaString"></MD5> </cScoreModel> Score is saved correctly. Might just be because the UserID doesn't match. Anyway, play it from start to end and stay away from saving on career scenarios with lots of AI traffic. Interesting to see that the UserID is saved as Int64... So while we cannot differentiate between 32 or 64 bit scenarios, we can see if the savegame comes from the 64 or 32 bit exe. (subject to more investigation)
Actually, my score never did that. My score is normal, as seen in the second screenshot. In any case, we confirmed the save is the issue, so I'm going to presume that both issues here are solved since I already diagnosed the F1 keyboard issue. I'll have to rerun it.
Yeah, but the rest of the details on the save are definitely still going to happen. And clearly did. So we've figured that out, at least!
For Cyclone as I can't upload to conversations. Register Serz.exe to .bin extension for just double-clicking them to get xml and editing is super fast in conjunction with 7zip file manager Love my super stable Win7 system.... can play TS, Youtube in the background, editors open and edit on the fly without closing TS.
If I try to open in 7zip it does nothing. I have to run 7zip itself, navigate to the directory, and open it that way. Takes a lot longer than just doing this: Also, older versions of WinRAR do NOT lock you out after 40 days (they just harass you with buy suggestions, which you can get a hacked EXE to bypass if it really bothers you). Current versions, I think, lock you out after 30 and try to force you to buy with no further use unless you do buy. Given the prohibitive cost, I wonder how few copies he actually sells...
Nah. Just run 7zip file manager. WinRAR's LOVE I'm off for a beer now with my fishing pal. Hope it's not my last one... See you, good night!
The beer. Putin's gone wild. And he's known for saying If a fight is inevitable you must strike first. Let's hope for the best.
Not sure where you are from, but yeah, Putin is a bit crazy ATM. I won't get into politics further than this. EDIT: Good news. I cleared the service. Felt better knowing the save I had messed someone else up, too, but I was still uneasy turning after the Cumbernauld route passed underneath.
I know that feeling when testing the coupler fixes I'm from Germany, Black Forest, they almost modelled my home along the Strasbourg-Karlsruhe line. I can see the lake where I'm spending sunny days.
