[Dogbert]

Went back to MG, as no 64x in 1.4.

Thanks very much for the continued development, Carlo.

Mike.

[cjakeman]

Genma Saotome, on 21 October 2021 - 09:40 PM, said:

I could not install 1.4, no idea why:
OR Update failure.jpg

I grabbed the weekly update instead.

Thanks for the feedback, Dave. I've passed it on to James.

[cjakeman]

Haran Banjo, on 21 October 2021 - 02:26 PM, said:

No support for 64 bits yet and for memory usage over 4GB?

Dogbert, on 22 October 2021 - 02:36 AM, said:

Went back to MG, as no 64x in 1.4.

Provision for 64-bit and large memory (as well as existing 32-bit) is targeted for the v1.5 Stable Version. It will build on the work that Carlo and PerpetualKid have already done.

[Dogbert]

cjakeman, on 22 October 2021 - 10:45 AM, said:

Provision for 64-bit and large memory (as well as existing 32-bit) is targeted for the v1.5 Stable Version. It will build on the work that Carlo and PerpetualKid have already done.

Thanks very much for the info, in regards 64x support buddy.

Mike.

[fiftogamer]

Thank you

[James Ross]

Genma Saotome, on 21 October 2021 - 09:40 PM, said:

I could not install 1.4, no idea why:
OR Update failure.jpg

I grabbed the weekly update instead.

That's curious - what version of Windows are you on and what version of .NET is Open Rails running on? This information is contained in every log file at the top (you don't need to go back to the old version to collect this information):

OS         = Microsoft Windows 10 Home 64-bit (10.0.19043)
Runtimes   = 2.0.50727 SP2  3.0 SP2  3.5 SP1  4 Client  4 Full  4.0 Client 
Runtime    = 4.0.30319.42000 (32bit)

My guess is that the OS/.NET version combination does not support TLS 1.2 or 1.3 (or possibly a cipher suite mismatch), which is what GitHub supports, which might be a problem for us using GitHub to host future updates (people on Stable 1.3.1 will have updated via openrails.org but people on a recent Testing/Unstable will have been given github.com links)

[James Ross]

Spoony81, on 19 October 2021 - 05:22 PM, said:

I just upgraded to version 1.4. I fired up an activity on MLT Sandpatch and the audio is making a popping or static noise. I closed out 1.4 and loaded up the latest Monogame version I have installed (103.1) and the popping sound is gone. I then loaded up an activity on Mullan Pass using version 1.4 and the same sound issues occurred. Any ideas on what would be causing the sound on 1.4?

No idea, sorry. :( I don't see anything in the NewYear MG release that would make the sound work for you without it working in the official version.

Niknak, on 20 October 2021 - 01:57 AM, said:

No sound issues here but have noticed a drop in fps of around 10-12 in v1.4 compared to Monogame version. Not a complaint just an observation.

There is a known issue where discrete graphics may give better performance on the official version but integrated graphics may give better performance on the NewYear MG version. You may also want to check the anti-aliasing control is set the same in both versions.

steved, on 20 October 2021 - 06:27 AM, said:

Are there any benefits from using 1.4 as opposed to ORMG?

There still a number of features Carlo includes in NewYear MG which haven't been migrated into the official versions. The bigger items I see on this list are:

• 64-bit
  
• New RailDriver implementation
  
• Cruise Control

Niknak, on 20 October 2021 - 07:38 AM, said:

I would be happy to use v1.4 instead of Monogame but as a Raildriver user I would need that tab to be present on v1.4

This feature looks to have been implemented by perpetualKid, so we really should have them contribute the feature into Open Rails. It's a lot more work for us to take it from Carlo's NewYear MG version.

[Niknak]

Thank you for your explanations James.