Yeah I agree, I would be lucky to get 1/2 an hour game play without it crashing, and if I am lucky enough for it to not freeze, when I do exit the game it crashes and brings up this message.
OMSI-Hamburg v1.0 installed?
Hello guys,
in the german part of this forum you wil find an explanation why the pauses are increased. The reasen for that is the chancge of computate the "kacheln". Watch here: dynamic faq (german) or here. It' all in german, sorry for that.
Yes there is a lot of freezes in the new patch! And the screen freeze was replaced by total game freeze... And I like these 30 seconds freezing in the new patch, it didn't happen to me in the previous patch...
OMSI completely freezes while loading <DG_RefreshNearlinks>. Not entirely too sure if that is the cause but that it just frozen for me.
Yes, i have a freeze a observance the set timetable, and enable the route helper.
When enable the route helper, and choose the timetable for the service, after i choosen the timetable, the game goes in freezeing...
Therefore, thanks for that, i can not use both. I can only use or the set timetable (but not use the route helper), or only use the route helper (but not use the set timetable).
I just tried to verification cache while steam, it's useless!
That's a very problem. We hope to solve this on next patch.
Alex.
Same for me, patch 16 was fine, then it suddenly went down hill.
the path links are due to the new loading system for OMSI, compared to one which loaded the whole map and just loaded scenery objects, which was much better in my honest opinion.
I doubt they can re-write a whole program to improve this though
Regards
While I've noticed that the crashes seem slightly more frequent, I'm always able to recover the current route after force quitting the game by using the load last situation option when I restart the game. It's actually quite scary at times as it will even put you in a moving bus if you were moving when the game crashed. The only other thing I've noticed with .024 is that on all the maps I use (only Spandau and Hamburg) the passengers sometimes just disappear when they exit my bus. It's really only a small visual inconvenience, and it doesn't affect gameplay, just looks a little weird.
That disappearing thing has been an issue since OMSI 1. I might be wrong, but I think it is because when the passengers exit, there is no human path nearby, so there is nowhere for them to go. Note how it happens in Grundorf at the terminal stop on the hill, Bauernhof. I do not know if it still does it, but I remember it used to do this in OMSI 1.
My issue is the constant stuttering when stopping the bus and the crashing after fifteen minutes of gameplay. Also, that error when closing the program still comes up, although it has been said that this has been fixed. OMSI 2 has been on and off for me.
Hopefully the next patch will "revert" the loading procedure back to its previous state as I did not have any issues with it!
Well, to me the "Fehler bei Bereichsprüfung" error came back to life and again makes Omsi 2 unplayable.
But anyways - after a quater of a year I now fed up with that mess. No doubt about the fact that M&R are trying their best to get all that fixed, but I am sick of error messages. I changed back to Omsi 1. Please someone call me when the software I paid for gets usable.
And no, I won't post logfiles or things. I feel abused, I am not the beta tester here.
I feel your pain man
But lets hope the next patch takes a little longer and eradicates that nuisance bug
Dear friends,
we completely feel with you.
Since you already know we keep working hard at it, I will post a statement although:
1) The "Bereichsprüfung"-errors occur seemingly random. They are hard to find - but everytime we catch one of them at our own systems, we clean it up. We will never reach a state of "no errors", but we keep approaching this aim.
2) To catch one of those errors we need more different systems and more information about the situations in which they occur. For this purpose we started a big beta testing program (this week). Nobody had ressources to start such a big campaign during the time before the release - there have been too many other things that had to get done before.
3) We read and think about every evidence that arrives our "network". We keep working and soon you will get the rescuing update, we promise! Give us the time we need to find the thousands of little conflicts in the code. It is not a job as "seek and find". It is "try and if you are lucky you will have one of the errors today". This is one reason (besides the few ressources) for this process taking so much time.
We build on your understanding.
Stay tough!
Janine
Can i add more bug to this?
The sound bug is still persistent so i've turned off the AI vehicle sounds, as im getting stuttering and slurring of sounds so its distorting.
Also if you have neighbour tiles set at 1, and set the view at 600 say, it'll crash with the address violation error, also if you play with the 'Rainy' weather set, it'll bring up the Range Error Fehler bei Bere(something) also if you play at night, with rain you get that error, the log
file shows the Direct 3D was lost and reset and lost again if you ok the error message.
Also if you play with man NG272 the force feedback causes the wheel to lock up and become stiff, but to change the settings the trigger list takes another age to load too.
Lordy
janine i know how its feels to find problems of thousands of codes but we omsi fans support to help ya guys what someproblems comes we take printscreen and put here its hope help u guys
Since installing patch 024, I am also one of those who can no longer play OMSI2 for longer than 15 minutes before it just freezes up and stops responding (ie. Windows "close program/wait for program to respond" prompt). Absolutely no useful error message, nothing in the logfile that I can see that would help diagnose the problem. I have tried verifying the files in Steam, and outright deleted and redownloaded it, with no help.
I can post a logfile, if needed.... I am well within system specifications, and when it runs, it runs at reasonable framerates across most of the default Spandau map.
I was cheeky and had a look at what the Fehler Bei Berespfer.... error (Range check Error) could be
Take a look at this: It's not uncommon, its just new to us."https://forums.embarcadero.com/message.jspa?messageID=542729"
It's an array with an invalid code which is causing the issue, it happens when using the Snow or Rain so something coded for the Rain environment isn't doing something correctly. Im sorry if this is too intrusive but there are some Delphi wizards on the forum, maybe a little insight will help crack the mystery bug.
