Elvas Tower: 3D Cabs - Elvas Tower

Jump to content

Posting Rules

All new threads will be started by members of the Open Rails team, Staff, and/or Admins. Existing threads started in other forums may get moved here when it makes sense to do so.

Once a thread is started any member may post replies to it.
  • 79 Pages +
  • « First
  • 69
  • 70
  • 71
  • 72
  • 73
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

3D Cabs Rate Topic: -----

#701 User is offline   trainagrandevitesse 

  • Apprentice
  • Group: Status: Active Member
  • Posts: 32
  • Joined: 17-September 13
  • Gender:Male
  • Location:Paris Gare de l'Est
  • Simulator:ORTS
  • Country:

Posted 22 June 2022 - 02:05 PM

View PostCsantucci, on 22 June 2022 - 12:42 PM, said:

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.


Hello Carlo,

I can't use my 3D cabin with MG, because an error message that I don't understand.
(see screenshot).

Could someone help me to solve the problem?

You talk about using the 32bit version of MG to solve the problem.

How to do on the "test" version and the "unstable" version?

Good night

Attached thumbnail(s)

  • Attached Image: MSG Erreur MG.jpg


#702 User is offline   trainagrandevitesse 

  • Apprentice
  • Group: Status: Active Member
  • Posts: 32
  • Joined: 17-September 13
  • Gender:Male
  • Location:Paris Gare de l'Est
  • Simulator:ORTS
  • Country:

Posted 22 June 2022 - 02:10 PM

View Postsuperheatedsteam, on 21 June 2022 - 04:01 PM, said:

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.


Hello Marek,
I haven't tested my 3D cabin on V1.3 of OR, but on stable V1.4 it works, so I think on v1.3 it works.

Were you able to solve the problem?

Good night

Jean Prisca

#703 User is offline   trainagrandevitesse 

  • Apprentice
  • Group: Status: Active Member
  • Posts: 32
  • Joined: 17-September 13
  • Gender:Male
  • Location:Paris Gare de l'Est
  • Simulator:ORTS
  • Country:

Posted 22 June 2022 - 03:49 PM

Good evening,
That's it, my 3D cabin, works in MG, so I no longer have a flickering display problem.

The problem comes from the digital clock.

Does it have to have a specific designation to work in MG?

Do you know how to display the seconds? I only had hours and minutes.

I can resume the development of my 3D cabin without having to redo everything.

Thanks to everyone who helped me.

Good night

Jean Prisca

#704 User is offline   superheatedsteam 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 497
  • Joined: 28-June 08
  • Location:Perth, WA
  • Country:

Posted 23 June 2022 - 02:21 AM

View Posttrainagrandevitesse, on 22 June 2022 - 03:49 PM, said:

Good evening,
That's it, my 3D cabin, works in MG, so I no longer have a flickering display problem.

The problem comes from the digital clock.

Does it have to have a specific designation to work in MG?

Do you know how to display the seconds? I only had hours and minutes.

I can resume the development of my 3D cabin without having to redo everything.

Thanks to everyone who helped me.

Good night

Jean Prisca


Hi Jean,

I had to increase the distance of the geometry. The faces that were approximately 0.3 mm apart had the problem. I had to increase the distance to over 1mm to stop the z fighting.

I think there is a problem with the digital clock on the 3D cabview. I only have one 3D cabview with digital clock. This cabview crashes MG but works in OR v1.3 and v1.4, but only displays hours and minutes. No seconds are displayed.

Cheers,

Marek.

#705 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 6,986
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 23 June 2022 - 03:50 AM

Hi Marek,
could you attach the crash logfile? Also a link to this cabview crashing in ORNYMG could be useful.

#706 User is offline   superheatedsteam 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 497
  • Joined: 28-June 08
  • Location:Perth, WA
  • Country:

Posted 23 June 2022 - 02:36 PM

View PostCsantucci, on 23 June 2022 - 03:50 AM, said:

Hi Marek,
could you attach the crash logfile? Also a link to this cabview crashing in ORNYMG could be useful.



Hi Carlo,

This is the exception message in ORNYMG.

Attached Image: cab_exception.jpg

In OR v1.3 and v1.4 it displays time but without seconds.

Attached Image: cab_time.jpg

The loco with 3D Cabview is called au__nr.zip available from trainsim.com (https://www.trainsim...right&fid=33315)

OpenRailsLog.txt attached.

Attached File  OpenRailsLog.txt (13.94K)
Number of downloads: 109

Cheers,

Marek.

#707 User is offline   Hamza97 

  • Engineer
  • Group: Status: Contributing Member
  • Posts: 606
  • Joined: 01-March 15
  • Gender:Male
  • Simulator:Open Rails
  • Country:

Posted 23 June 2022 - 08:23 PM

I guess this was bought up previously too and one of the reasons mentioned was that crash occurs in MG version due to excessive usage of digital numbers or something to that effect. I think the number of digit after the dot (.) causes the crash ( the ACCURACY value in CVF definition ). I have made two types of cab. One of them have slightly more digital number defined in CVF file and that cab crashes in MG version, with this same error.

#708 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 6,986
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 23 June 2022 - 10:48 PM

I have checked the code. In all OR versions there is a limit about the maximum number of digits that can be displayed for a digital control in 3D cabs. This number is 6. If the real string is shorter, blanks are inserted in a position that depends from the justification of the control, as defined in the .cvf file.
In the ORNYMG version there is a check (that probably has been dropped in the official OR versions) about the length of the string to be displayed. If this length is bigger than 6, the check aborts the execution of OR, which indeed is a hard measure.
In the other versions there is simply no check, and only the first 6 characters are displayed.
Indeed, if seconds have to be displayed, 6 chars are not enough. There should be 8 (considering also the ":") separators.
Now I can easily remove the length check, and so there wouldn't be the crash, and excess chars wouldn't be displayed.
Increasing the max number of displayable chars to e.g. 8 would also be easy, but maybe might lead to misalignmens with respect to actual OR versions.
Having a variable max number of displayable chars (that is setting it to 8 for clock displays with seconds) is a bit more complicated.

So by the moment I will only remove the length check, and wait for comments by the 3D cab creators for further changes.

#709 User is offline   superheatedsteam 

  • Conductor
  • Group: Status: Contributing Member
  • Posts: 497
  • Joined: 28-June 08
  • Location:Perth, WA
  • Country:

Posted 23 June 2022 - 11:17 PM

After Hamza97's post, I tested different values for the digital clock ACCURACY () parameter and found a 0 or any negative number will not throw an exception in ORNYMG and, as expected, no seconds are displayed.

Ideally, OR and ORNYMG should be able to display the seconds in clocks with digital display.

Cheers,

Marek.

#710 User is offline   Csantucci 

  • Member, Board of Directors
  • Group: Status: Elite Member
  • Posts: 6,986
  • Joined: 31-December 11
  • Gender:Male
  • Country:

Posted 24 June 2022 - 01:17 AM

OK, in ORNYMG 126.3 I have eliminated the crash and have increased to 8 the max digits displayed for digital clocks requiring the display of seconds (Accuracy > 0).

  • 79 Pages +
  • « First
  • 69
  • 70
  • 71
  • 72
  • 73
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

3 User(s) are reading this topic
1 members, 2 guests, 0 anonymous users

  1. abschlammventil