[Laci1959]

Traindude, on 11 June 2022 - 08:34 PM, said:

Excellent! I have made a Trello Card in case anyone else wants to vote for it:
https://trello.com/c/iDr0POSw

Hello.

The NYMG version can support various dedicated cab views. Maybe you should try in that direction?

Sincerely, Laci 1959

[Laci1959]

Weter, on 12 June 2022 - 10:16 AM, said:

They are 2-d, as I know, aren't them?

Yes, but if it works there, the 3d cab might take over. If not, you should ask MR Csantucci. If you can help.
Trial luck.
I know it’s not a nice thing to advertise for another thread, so I apologize.
I commute here and there between the two threads, according to my current idea.

Sincerely, Laci1959

[Traindude]

Laci1959, on 12 June 2022 - 10:12 AM, said:

Hello.

The NYMG version can support various dedicated cab views. Maybe you should try in that direction?

Sincerely, Laci 1959

Thanks! I'll investigate...

[trainagrandevitesse]

Hello, :)
Thank you very much to "superheatedsteam" and "mrmosky"
I fixed my wiper animation too slow problem, I increased the speed of animations in file S. :victory:
I apologize for answering you late, but I don't have a lot of time to do 3D.

Goodbye

Jean Prisca
;)

[trainagrandevitesse]

Hello :)
I have a display problem in the 3D cabin since I did the last "test" update t1.4 533.

All analog indicators, lights, lamps, clock, digital speedometer, flash on their own as soon as you enter the game.

I feel like the problem is only on objects that are very close to each other.

I made a gif to show the problem.

On V1.4 there is no problem.

The other 3D cabin creators, did you enter this problem

I model with Blender 2.81a


still in 3D cabin view, I notice that some traffic lights have the same bug, same for some scenery objects.

In the other views, there is no problem with the objects in the background.

I put the log.txt file


Good night

Jean Prisca

Attached thumbnail(s)

• 

Attached File(s)

•  OpenRailsLog.txt (17.11K)
  Number of downloads: 109

[superheatedsteam]

trainagrandevitesse, on 21 June 2022 - 03:15 PM, said:

The other 3D cabin creators, did you enter this problem

A number of 3D cab creators have reported this issue. In my case it was due to the close proximity of faces and occured in OR v1.4.x and MG which both use the Monogame graphics engine.

If you test in OR v1.3 which uses XNA graphics engine, do you still have the issue?

Cheers,

Marek.

[Hamza97]

Yup this issue is there in newer versions which use MG API. Older XNA versions doesn't have this issue. In my cabs too this issue occurs in MG version whereas the gauges and dials works perfectly without any flickering in XNA based older versions. I think the Z Buffer Depth is low in MG versions which is causing the issue maybe.

[Laci1959]

Hello.

Unfortunately, this is exactly the problem with railway signals.
If they can't solve the Monogame problem, it would be good for the developers to provide an exact number. That is, a distance of at least 1, i.e. one meter, must be maintained between two consecutive vertical surfaces. I could have written 10 meters.
Then I would know if it is worth re-modeling about 130 railway signals or not because the error will be fixed. Instead of an alpha channel, circular cutouts should be made on the sign of the signal.
Or do you prefer to stay with version 1.3 and give up all improvements?

Sincerely, Laci 195

[Csantucci]

I believe this is not due to MG, but to 64 bit operation. To verify this you can run ORNYMG with the 32bit option set.

[VAPOR3D]

Indeed, checking that box in the "ORNYMG Only" tab solves the issue. Also, it seems that it does not affect the framerate.

Thanks for finally providing the solution, Carlo!