OR vs ORNYMG

[frliss]

I'm just finding out that OR and ORNYMG do not display routes and rolling stock exactly the same.

I have two questions. First: what are the major differences between OR and ORNYMG, and Second: is there any benefit of using one over the other.

Fred

[dcarleton]

It's up to you.
If you want stability, use the stable version of OR.
If you want stability plus some cool new features, use ORNYMG.
If you want to get a preview of features as they are being being developed, use the testing version of OR.
If you want an adventure, are not scared of surprises, and are willing to report defects to the OR development team, use the unstable version of OR. (That's what I do.)

If you have been using ORNYMG and you have become comfortable with it, you may want to stick with it because changing to a different version is likely to feel like a letdown. ORNYMG is not produced directly be the OR development team, and includes features unique to ORNYMG. It does get updated periodically based on more recent testing versions from the OR development team.

A new stable version of OR (1.6) is going to be released soon.

[wwhall]

^A very good synopsis. Or, you can use all of them. How? Just install each as a discrete program. The OpenRails program is not a big disk drive hog. I currently keep about the last 10 ORNYMG versions as discrete programs on my computer, just renaming the program folder to something like "OR_MG_R163" for the particular version. That way, I can easily use and earlier version if a later version causing an issue. It is also useful for "bug tracing"--as in, where did this bug first appear.

[gammaray84]

If you read Readme_ORNewYear_MG.txt, there is a release note:

"RELEASE NOTES:
This unofficial version has been derived from the latest official Testing release T1.5.1-1695,
plus some of the features already present in the Unstable release."

Have a good day everyone.

[pschlik]

To give a more concrete answer, OR NewYear MG is built off of the official Testing version as a baseline, and then also adds in some features still in Unstable (usually, these are features that are lower risk because they don't change much, are almost completed, or do something useful without introducing loads of bugs), and most importantly adds in some of its own features. Sometimes the NewYear features are things that aren't in the main version because there was some disagreement about whether or not it should be an OR feature, some are things that are more technical than the average user needs to worry about (what is the "watchdog"? If you don't know, you probably don't need to see the option for it), and then others probably should be in the official version but aren't because someone forgot that the testing on NewYear was supposed to be temporary.

I suppose it could be compared to something like the patch packs out there for OpenTTD; roughly follows the official thing but has more features as there can be less red tape than adding to the official build (not that there's much red tape).

[frliss]

If you want stability, use the stable version of OR.
If you want stability plus some cool new features, use ORNYMG.
If you want to get a preview of features as they are being being developed, use the testing version of OR.
If you want an adventure, are not scared of surprises, and are willing to report defects to the OR development team, use the unstable version of OR. (That's what I do.)

Looks like this answer pretty much sums everything up. Personally, I look forward to trying out the new features that pop up from time to time in ORNYMG.

Fred

[mikeebb]

Another question: if I want to get OR to run in Linux (with a nVidia 3060 using the system-supplied driver blob), do I need to use ORNYMG? I guess the issue is how to get either one to play nice with Wine, or even raw Linux (Mint, from Ubuntu in my case) with Mono and/or .NET Core installed. Either way, I've had No Luck and no recent documentation of the process.