[jonas]

Hello,

do the following:

1. Set the option "Windowed" in the OR Unstable.
2. Call ORNYMG and close it (no activity start necessary).
3. Call OR Unstable again -> the "Windowed" option in OR Unstable is no longer set!

No matter which version numbers of the both OR versions.

(May be I have mentioned this here so or so similar before - but didn't find anything about it in the forum).

Greetings
Jonas

[engmod]

I use separate ini files for my installs.
I have 1.4, 1.5.1, unstable and ORNYMG all set up with ini files to separate any settings.

[jonas]

Interesting Derek, I would also like to do so. But I can only find one "Update.ini" in each of the different installation directories.
Can you describe in more detail how you use the separate ini files?

[engmod]

From memory if you make a file called openrails.ini, it will populate it on save.

My ORMG ini file for reference.

Attached File(s)

•  openrails.7z (1.24K)
  Number of downloads: 62

[jonas]

It works with an openrails.ini as you remember, Derek. In principle a good way to initialize the versions separately! However, it is a bit disadvantageous that you have to set all settings in the options again, for example all names and paths under "Content" etc., when using the ini for the first time. But thanks for the hint with the individual openrails.ini, I don't know this so far...or had forgett it.

But since not every user (like me until yesterday) knows how to handle the openrails.ini, I don't think the bug isn't fixed enough by this.

If no openrails.ini are used, then obviously the Win registry or similar is used. And then it seems that the using of the ORNYMG version resets the windowed option for the unstable version to full screen.

Carlo, what do you say about this, is my impression wrong?

[Csantucci]

Hi Jacob,
my opinion is that we could live with this. How many unskilled players continue switching from official OR to ORNYMG and vice-versa?

[jonas]

I also think that they are probably only a few. At most, people like me who do routinely tests with the different OR versions after making changes to a route.
I wrote it here under "May be it's a bug" because such effects can be an indication of a possible bigger problem - here for example when writing to registry when closing the program. But of course it is not a fundamental problem so far and we could live with this.

Greetings
Jonas