Present ORTS limitations?

[conrail1]

Yes, of course it is. What's the relevance of that?

You mentioned here -

I don't think we'd actually have much trouble switching to pure DirectX or OpenGL

So can you easily use Microsoft's XNA framework for the rendering with OpenGL?

[twpol]

So can you easily use Microsoft's XNA framework for the rendering with OpenGL?

I have no idea where this came from. I said we could switch from XNA to DirectX or OpenGL. That means using the DirectX or OpenGL API directly, not by way of proxy though XNA's API.

[conrail1]

I have no idea where this came from.

If OpenRails is currently using XNA for rendering and is using DirectX API calls why do you not know where this is coming from?

That means using the DirectX or OpenGL API directly, not by way of proxy though XNA's API.

So if you use OpenGL directly are you not getting rid of XNA for the use of rendering completely?

[Dralex]

I cannot imagine XNA without DirectX. So, I would think if it is possible to use pure OpenGL, you would then get rid of XNA.
I would think that for only one year's development time you have done an enormous amount of work. I don't care how this is done. I do appreciate that it is impossible to make all MSTS features work in that time. As for instance uncoupling a loco from its consist using the F9 window. At present the only method you can use is pressing and holding D and clicking the mouse on the coupler in question. CAVEAT: Be sure that the camera focus is on the loco, that is, you did not use Alt-NP3. I did exactly that, I could then go to the cab with 1 keyin, but I can now never get an external view of the train. This would put me back to the uncoupled consist. I shall have to try to put back the loco to that consist and then put the focus on the lco (using Alt-NP7).
BTW, to make these keyin work you have to make sure that NumLock is off, thus making e.g. NP9 equal to PgUP. Was this intended?

Dralex

[twpol]

I cannot imagine XNA without DirectX. So, I would think if it is possible to use pure OpenGL, you would then get rid of XNA.

Yes, if we switch to either DirectX or OpenGL that would be without using XNA.

BTW, to make these keyin work you have to make sure that NumLock is off, thus making e.g. NP9 equal to PgUP. Was this intended?

The keys are incorrectly labelled by the game (and subsequently copied in to the documentation) as the numpad keys; they are supposed to be the 4 arrow keys, Page Up, Page Down, Home and End. These keys will work even though the labelling is wrong, and the labelling has been fixed for the next release.

[longiron]

As for instance uncoupling a loco from its consist using the F9 window. At present the only method you can use is pressing and holding D and clicking the mouse on the coupler in question. CAVEAT: Be sure that the camera focus is on the loco, that is, you did not use Alt-NP3. I did exactly that, I could then go to the cab with 1 key in, but I can now never get an external view of the train. This would put me back to the uncoupled consist. I shall have to try to put back the loco to that consist and then put the focus on the lco (using Alt-NP7).
Dralex

Dralex,
There are TWO uncoupling methods. Once uses the Mouse as you mentioned. The other is clicking on the coupler icon in the F9 Window just as you would with MSTS. Using the F9 approach eliminates the need to correctly position the camera to uncouple as you can select any coupler in the F9 window.

[GoGoran]

As for the keys: Non-US/Non-English-language users should install the US keyboard layout on their machines and switch to US keyboard layout before playing OR. Then everything works fine, or so I have been told, and the keys are also supposed to be the same as in MSTS default configuration. Oh yeah, and switch off NumLock.

[Dralex]

Switching to English or US keyboard does not help me much. I think I'll stick to what I have now - I can work with that - and wait for the day when the keyboard can be configured to one's liking. As for NumLock having to be off, I thought so, and I prefer using Home, End, PgUp and PgDn anyway because normally I have NumLock on, and I don't have to turn it off.
Besides, I recall having posted something about helper engines not being displayed. This is exactly the same problem I had with the SD402, because the helpers are such engines. With this problem fixed I can see the helper, and most probably also control it by coupling my player train to it.

Dralex

Sorry, Longiron, but clicking on the coupler icon does not work. (I would like to know why.) I woud expect the cars behind the coupler in question to disappear from the F9 window, as they do in MSTS. They should also disappear from the braking info (pressing F5 twice).

[twpol]

Sorry about not being clear. Using the F9 window to uncouple requires you to DOUBLE CLICK on the coupler - just like MSTS. If it's not working for you, please let us know.

No, you don't. It's single-click in OR.