Official v0.7 Thread

[OTTODAD]

One thing is the roads are not showing up,I think they never have ?

What problems with which roads I have no problems with here in the NEC-4 with DB-Tracks ?

O t t o

[twpol]

Let me take a look at the updates to the code between build 677 and build 779. That should help determine what changed to narrow down the problem.

Considering the error is with loading the cab view, I expect it's just when we added a particular bit of that. Most likely some malformed or bogus data that MSTS doesn't heed that we need to be more defensive about.

[dennisat]

Multiple units with combined throttle/brake controls displayed the control in the previous release of OR but did not animate. In the new release the control does not display and when you're "in the cab" OR continuously generates the following message, as if in a loop:


Error: System.NullReferenceException: Object reference not set to an instance of an object.
at ORTS.CabViewDiscreteRenderer.GetDrawIndex()
at ORTS.CabViewDiscreteRenderer.PrepareFrame(RenderFr ame frame)
at ORTS.CabRenderer.PrepareFrame(RenderFrame frame)
at ORTS.MSTSLocomotiveViewer.PrepareFrame(RenderFrame frame, ElapsedTime elapsedTime)
at ORTS.MSTSElectricLocomotiveViewer.PrepareFrame(Ren derFrame frame, ElapsedTime elapsedTime)
at ORTS.TrainDrawer.PrepareFrame(RenderFrame frame, ElapsedTime elapsedTime)
at ORTS.ORTraceListener.TraceEventInternal(TraceEvent Cache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
at ORTS.ORTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
at System.Diagnostics.TraceInternal.TraceEvent(TraceE ventType eventType, Int32 id, String format, Object[] args)
at System.Diagnostics.Trace.TraceError(String format, Object[] args)
at ORTS.ORTraceListener.WriteLine(Object o)
at System.Diagnostics.TraceInternal.WriteLine(Object value)
at System.Diagnostics.Trace.WriteLine(Object value)
at ORTS.TrainDrawer.PrepareFrame(RenderFrame frame, ElapsedTime elapsedTime)
at ORTS.Viewer3D.PrepareFrame(RenderFrame frame, ElapsedTime elapsedTime)
at ORTS.UpdaterProcess.Update()
at ORTS.UpdaterProcess.UpdateLoop()
at System.Threading.ThreadHelper.ThreadStart_Context( Object state)
at System.Threading.ExecutionContext.runTryCode(Objec t userData)
at System.Runtime.CompilerServices.RuntimeHelpers.Exe cuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(Exec utionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()


I've tried several payware and freeware models with combined throttle/brake with the same result. OR keeps going but the log gains size extremely rapidly!

Dennis

[longiron]

Multiple units with combined throttle/brake controls displayed the control in the previous release of OR but did not animate.
Dennis

Dennis,

We discovered a bug with combined throttle/brakes as follows:

Using 3DTS Tehachapi Pass II --- Activity 3DTS_TEH2_SF_E-BAK_SBD-5-18 as a test case. The 3DTS_SD75M-cvf cab view file has the value 18 for NumFrames ( 18 .... This is consistent for standard Dash 9 cab view. Nine frames are used for throttle control, nine used for dynamic breaking. However the 3DTS_SD75M_SANTAFE_242.eng file Brake_Dynamic ( ... NumNotches ( 3 ; only 3 notches for the required 9. Replacing the Brake_Dynamic block with MSTS dash 9 eliminated the hang-up. {NumNotches ( 9 ... values filled out}

Most likely this problem didn't show up with MSTS, they probably parse the files differently to obtain there values. Bottom line is that OR needs correspondence between the .cvf file and .eng file as in the standard MSTS Dash 9 distribution. A cursory glance of other Dash9 files in the 3DTS folder appear to have the same characteristics.

A secondary problem the OR code has a fixed constant of 18 for NumFrames. In this particular case the bug would have been the same. The value 18 would have been picked up from NumFrames. This will be fixed shortly.

[apco25]

I just want to say the reappearance of microtext.ace and the throttle responsive exhaust is just phenominal. THANKS OR Team!

However, the new version isn't digesting the LSRC route as the previous version did. I'm now getting this pile of errors and subsequently tiles are not being display - just blank white empty space. I had no issues with the previous verison displaying tiles in the entire LSRC route.

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014402.w
Line 61: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014402.w
Line 536: Input string was not in a correct format.
SSSSSSSSSSW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014402.w
Line 142: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014402.w
Line 1891: Input string was not in a correct format.
SSSSSSSSSSSSSSSSWtttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014405.w
Line 19: Missing texture filename in forest region. UID=0

W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014405.w
Line 19: Missing texture filename in forest region. UID=0

W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011588+014405.w
Line 19: Missing texture filename in forest region. UID=0

tttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014402.w
Line 61: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014402.w
Line 536: Input string was not in a correct format.
W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014402.w
Line 142: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014402.w
Line 1891: Input string was not in a correct format.
WtttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014405.w
Line 19: Missing texture filename in forest region. UID=0

W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014405.w
Line 19: Missing texture filename in forest region. UID=0

W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011588+014405.w
Line 19: Missing texture filename in forest region. UID=0

tttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014402.w
Line 61: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014402.w
Line 536: Input string was not in a correct format.
W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014402.w
Line 142: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014402.w
Line 1891: Input string was not in a correct format.
WtttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014401.w
Line 265: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014401.w
Line 2156: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014401.w
Line 2465: Input string was not in a correct format.
S(repeats) SSSW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014401.w
Line 24: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014401.w
Line 383: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014401.w
Line 399: Input string was not in a correct format.
SSSWtttTTTwwwWWW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014401.w
Line 19: Missing texture filename in forest region. UID=0

tttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011588+014403.w
Line 19: Missing texture filename in forest region. UID=0

WWtttTTTwwwWWW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014401.w
Line 19: Missing texture filename in forest region. UID=0

tttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014400.w
Line 19: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014400.w
Line 54: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014400.w
Line 70: Input string was not in a correct format.
W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014400.w
Line 313: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014400.w
Line 2823: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014400.w
Line 2851: Input string was not in a correct format.
S(repeats) SSSSSSSSSSSSSSSSSSSW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014400.w
Line 41: Missing texture filename in forest region. UID=0

SStttTTTwwwWW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014403.w
Line 14: Missing texture filename in forest region. UID=0

W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 423: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 4500: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 4516: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 4532: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 4548: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5216: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5233: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5509: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5525: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5541: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5557: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5573: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5589: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5605: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5621: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5637: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014403.w
Line 5653: Input string was not in a correct format.
tttTTTwwwW

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014400.w
Line 19: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014400.w
Line 54: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011591+014400.w
Line 70: Input string was not in a correct format.
W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014400.w
Line 313: Missing texture filename in forest region. UID=0

STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014400.w
Line 2823: Input string was not in a correct format.
STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011590+014400.w
Line 2851: Input string was not in a correct format.
W

Warning: STF Error in E:\MSTS\Train Sim\Train Simulator\ROUTES\LSMS\World\w-011589+014400.w
Line 41: Missing texture filename in forest region. UID=0

[OTTODAD]

On the subject of combined throttle controls, the combined speed and train brakes control used in the Japanese Series 7000 and my Santa-Fe Explorer does not work in ORTS like it does in MSTS.

No throttle lever is being displayed, train brakes have to be applied separately as with other locos and there is no forward movement or very little of it in a jerking fashion.

O t t o

[longiron]

The new version isn't digesting the LSRC route as the previous version did.

As the OR team digs deeper into the guts of MSTS files, new things crop up. As discussed regarding problems with your Blackfoot route,

https://www.trainsim.com/vbts/showthread.php?305211-OR-not-digesting-BaclkFoot-Vegreville-CAN99v2-world-files-properly

the Missing texture filename in forest region relates to "0" entries in the World file for Yard Cam which causes OR not to parse the world file correctly. The fix is the same.

[koasterkidd]

i do personally think that in the future, there should be an "automatic fireman" feature for users who want a better experience in msts but do not know how specifically fire an engine, etc.

[GoGoran]

i do personally think that in the future, there should be an "automatic fireman" feature for users who want a better experience in msts but do not know how specifically fire an engine, etc.

It unrealistic anyway to have one person fire and drive at the same time. There is a reason why there were always two men on a steam locomotive. In MSTS, I always use the automatic fireman.

[longiron]

i do personally think that in the future, there should be an "automatic fireman" feature for users who want a better experience in msts but do not know how specifically fire an engine, etc.

Right now the default mode is automatic fireman. The future will have more manual controls.

[kox]

Maybe there is something that i missing, but where are the night shadows of object cast by the locomotive headlights? I see some terrain only shadows, but those look very badly, those are total black, and looks like that shadowing uses the terrain faces, so the shadows are triangles, rectangles and other odd looking shapes, also those shadows edges isn't blurred, while the day shadows are.

If i use 512x512 shadow maps, the shadows of moving objects (like trains) are lagging, it looks like the shadows updated in every second or more frames. With default 1024x1024 it's still happens but less noticeable.

[apco25]

Further checking finds the Goodrich & Exeter (GOD_Ex) has 4km by 4km tiles which OR won't read at all, so it is the same boat as Blackfoot 3...

[twpol]

Maybe there is something that i missing, but where are the night shadows of object cast by the locomotive headlights?

There aren't any - never have been. The headlight lights up things facing it, but no shadows are or ever have been cast by it.

If i use 512x512 shadow maps, the shadows of moving objects (like trains) are lagging, it looks like the shadows updated in every second or more frames. With default 1024x1024 it's still happens but less noticeable.

Shadows are updated every frame. The position of the sun used for shadows is not but this is only noticable if you speed up time.

[kox]

There aren't any - never have been. The headlight lights up things facing it, but no shadows are or ever have been cast by it.

Hmm that's strange, i've seen something like that in an older orts release video when a that default Japanese DMU's headlight cast the shadow of a signal post but i can't find it now. Maybe it was a terrain shadow, perfectly aligned on signal.

Shadows are updated every frame. The position of the sun used for shadows is not but this is only noticable if you speed up time.

Then what is that lagging? (i did not use speed up time).

The terrain shadows look like this. Is it possible to disable them?

What is ShadowAllShapes boolean doing? I know that if i enable it more objects cast shadows, but without it how the game determines what objects have shadows and what are not?

[twpol]

Hmm that's strange, i've seen something like that in an older orts release video when a that default Japanese DMU's headlight cast the shadow of a signal post but i can't find it now. Maybe it was a terrain shadow, perfectly aligned on signal.

I know the video and it must be something else conincidentally looking like that, as they've never been implemented.

Then what is that lagging? (i did not use speed up time).

The terrain shadows look like this. Is it possible to disable them?

What is ShadowAllShapes boolean doing? I know that if i enable it more objects cast shadows, but without it how the game determines what objects have shadows and what are not?

I do not know what is "lagging". If you've turned ShadowMapCount down from 4 or ShadowMapResolution down from 1024, the lower resolution may make them look less smooth because they're more blocky (with blur enabled it can be tricky to tell how big the blocks are).

Terrain shadows are not actually shadows and you cannot disable them.

With ShadowAllShapes disabled, the route creator has control over what casts shadows with the relevant shadow options in the MSTS RE. With ShadowAllShapes enabled, all objects cast shadows.