[RT] BR 146-5 Fernverkehr

It's because your Railworks folder is not set in Windows Registry. Read how to fix :

'Railworks Registry Entry Was Not Detected' Or 'Railworks Was Not Found' : The Spirit of Flight Simulation (justflight.com)

Hello,

I find the model well done overall. It's better than RSSLO and 3DZug but still far from what vR does. The sounds are weak, there are missing sounds for example for the PZB (it sounds like the sounds of an old locomotive from the 90s). There are still some cool functions (rollo, panthograph spark and windows that open). I haven't encountered any bugs. The behavior of the headlights and screen lighting is a bit mixed with the long-range lights.

I find that the asking price is still high for the BR146-5 and the IC2, especially without an interior view and with incomplete sounds. And what's more, the model has not finished all the tests. It is therefore not a “finished” product. There is no automatic numbering and the driver does not change with the direction of travel. For a 2024 train, it is still below standards. With the help of the community, it should go well in the end.

Only for advanced users : mapper, engine with a few sensitivity changed, cabview (vR like). No support from me nor the editor.

For testing prupose only. I add some descriptions in the engine bin file for feature handled by inputmapper.

Kann man nicht den Sound von der Niclas Lindner 146 bei der hier einbauen, fand den nämlich eigentlich ganz gut gelungen und das beste an der Lok...

Vielleicht macht linusf für nen paar Euros nen Soundupdate...dann wäre sie mir den Kauf wert.

@ES64F4

Thank you for your feedback, it only doesn’t help us much forward here, you give a point and don’t provide exact details what is missing. Ofcourse I like to ask than for more info which I will use to do bug fixing on.

First of all which PZB sound is missing for you?. The guys in our beta team are real train drivers and they didn’t discovered a missing sound. So I’m curious to know what you missing. So we can look into that.

You give an example of the headlights which are mixed for you? What is exactly mixed for you, both switches are correct , they do what the real train do and I didn’t find it in any other train correct like this which you mentioned.

Driver switch from cab when you turn into driving directions, code is 10 years the same. Something what is included already for 10 years in my addons .

Auto numbering? I never used this for a couple of numbers, and I will for sure never use it in TSC. TSW is another story. How much times users look into a couple of numbers which change ? I use the auto numbering for something more interesting, the destination signs, and a scenario creator use this to make a train setup with driver position and the right destination. And I use this because it’s also very user friendly for a beginner scenario creator to fill in a train number and go

You come here with an example about the selling price, I can only say, my opinion. You received a fair price for 6 months of development time where 3 months long was daily full time working this was moste time 6 days per week. include one student graduated his software education on this addon. To compare and give you some sort of comparable information with my working speed .the basic DTG TSC trains which run probably some where on one of your routes (not made by me) Im able to finish in one month to a final product. There is really allot in this locomotive and it contain also the moste code amount I ever released in a addon, there is much more going on there inside. And every part is made by one person , and many thanks to the people which help me in their free time with beta testing and guide me forward.

I’m looking forward to receive detailed info so we can look into it and improve on this br146-5 addon if possible. Thanks in advance for your help.

Railtraction - Hello - I don't think you need to justify the price. You are an entrepreneur and calculate according to your own criteria - out and out. I think the price you are asking is more than fair. This eternal price talk is simply unnecessary! Thank you for your great work and the support you are still providing.

Zitat von SÜWEX

Railtraction Would it be possible to make the power lever of the animation a little slower and the AFB just a little faster?

Yes sure I can look into that, this should be possible.

DonMattheo ,

Thank you for your understanding. Ofcourse I understand that I can’t make everybody happy, especially with the newer simulators in the background which also increase a little bit the expectations in TSC. I think some times it is a little forgotten how much time this work can eat, a big wish for the community was a better RT LZB, i did spend extra time on that and even rebuild it completely. And if I’m happy with that LZB I will reuse it in other addons, for this I still take time to follow the results.

I really like the model, for me it's the best Traxx 2 so far. The only thing I don't like on the exterior ist the brightness of the running surfaces of the wheels. Perhaps they could be made darker and a less glossy? As they are always in the dark below the loco, they should not reflect so much light.

ja, ist mir auch passiert

Ja muss man sich leider was selbst zusammen basteln

Zitat von SÜWEX

Hat eig. noch jemand von den Szenario Erstellern das Problem, dass der mitgelieferte Preload den TS zum Absturz bringt?

Hi,

What i can tell is that there is nothing wrong with the preload itself, it also cant create many issues as this blueprints self doesnt do allot.

Yes im able to reproduce the exact same problem when i try to place the preload. but im unable to find where this problem come from, i dont see anything unusual trough logmate , only thing what i can trace for now is that TSC crach near the particle manager when i have windbg online.

After this i tried to place everything manual what is part of the preload consist, this work fine here. (question is here than where is this crash comming from? if it is my loco than i also expect to get some problems with manual placing, or ingame,or in quickdrive. this isnt the case.

than i start to run the quickdrive and use this preload , works also fine.

under your message i was writing a update,

UPDATE

After a full debug round trough every function in lua i came on a part where i received a Null Reference on a Call to the core GetSpeed, This is solved and i can place the preload again without issues,

Dont ask me why this problem excist, placing manually the loco do exactly the same as when place by preload, manual work correctly. place by preload it go stuck /crash on a lua Call.

so i cant explain exactly what happen in TSC but it is atleast solved.

Zitat von SÜWEX

Railtraction Would it be possible to make the power lever of the animation a little slower and the AFB just a little faster?

You can edit en engin with RWtools. For exemple; I change to 20 to have a faster AFB speed change. Perhaps 1.3 will be better. High value => High speed.

<cControlContainerBlueprint-cControlValue d:id="706906">

<ControlName d:type="cDeltaString">AfbSpeedSet</ControlName>

<DefaultValue d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</DefaultValue>

<MinimumValue d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">0</MinimumValue>

<MaximumValue d:type="sFloat32" d:alt_encoding="0000000000006440" d:precision="string">160</MaximumValue>

<BriefDescription d:type="cDeltaString"></BriefDescription>

<LocalisedControlName>

<Localisation-cUserLocalisedString>

<English d:type="cDeltaString"></English>

<French d:type="cDeltaString"></French>

<Italian d:type="cDeltaString"></Italian>

<German d:type="cDeltaString"></German>

<Spanish d:type="cDeltaString"></Spanish>

<Dutch d:type="cDeltaString"></Dutch>

<Polish d:type="cDeltaString"></Polish>

<Russian d:type="cDeltaString"></Russian>

<Other/>

<Key d:type="cDeltaString"></Key>

</Localisation-cUserLocalisedString>

</LocalisedControlName>

<DetailedDescription d:type="cDeltaString"></DetailedDescription>

<ApplyToConsist d:type="cDeltaString">eFalse</ApplyToConsist>

<HUDControlID d:type="sUInt32">0</HUDControlID>

<InterfaceElements>

<cControlContainerBlueprint-cInteriorIrregularNotchedLever d:id="706927">

<ElementName d:type="cDeltaString">Untitled</ElementName>

<DifficultyType d:type="cDeltaString">StopGo</DifficultyType>

<PickTransformName d:type="cDeltaString">AFBLever</PickTransformName>

<MovementType d:type="cDeltaString">MoveUpDown</MovementType>

<AnalogInputSensitivity d:type="sFloat32" d:alt_encoding="0000004033331540" d:precision="string">20</AnalogInputSensitivity>

<DigitalInputSensitivity d:type="sFloat32" d:alt_encoding="0000000000002640" d:precision="string">20</DigitalInputSensitivity>

It's the same for VirtualThrottle. Value is set to 1, you can set it to 0.9 or 0.8 to slow it down. I have not test it.

<cControlContainerBlueprint-cControlValue d:id="704023">

<ControlName d:type="cDeltaString">VirtualThrottle</ControlName>

Railtraction : I will report some bugs and answer you later.

Zitat von Perotinus

I really like the model, for me it's the best Traxx 2 so far. The only thing I don't like on the exterior ist the brightness of the running surfaces of the wheels. Perhaps they could be made darker and a less glossy? As they are always in the dark below the loco, they should not reflect so much light.

I fix it for my use.

Please check below what is currently already around the clock for 1-1 ! Not online yet! I run an internal test now on the bugs and check if it’s really fixed . currently in version 1.0.5

\\\\\\\\\\\\\\\ Changelog 1-1 /////////////////

Added: Phantograph inputmapper Key: P

Added: Handbrake input mapper Key: / (Slash)

Added: Extra preload for single locomotive, also added a couple of extra guids.

Added: lua Call for B Symbol(disapear now when pzb/LZB switch off) instead of always on .

Added: Extra lua condition check on syscall messages, now when loco is not driven messages are blocked, also block on initialize.

Bug: Missing 0 value in the brake dial.(Brake dial now turn back to 0 when train stand still)

Bug: extra condition on LZB to monitor incomming PZB messages when locomotive enter in LZBEnd program.

Bug: Preload placement work again after a small fix in our lua script (regarding Null reference).

Change: Sound curve for motor sound, slightly changed the traction curve , traction sound levels increase earlier by Kilonewton.

Change: sound curve motor sound vs speed, sound volume increase now a little earlier.

change: 6 motor steps decibels increased to aproxx -12db , and low level decreased.

Change: zugart messages, should be more clear to understand now when switch to other zugart/ pzb modus.

Change: AFB key mapping from: K to Shift+A

Change: Sifa only activate when train stand still include reverser in position M.

Change: PZB only activate when train stand still include reverser in position M.

Change: LZB Signal blocker only activate when train stand still include reverser in position M.

Change: Regulator, digital sensitivity decreased.

Change: AFB SpeedSet, digital sensitivity Increased.

Change: Darker Wheel texture include more contrast in wheel details.

Extended: manual

Under investigation: AFB brake power, require more time to optimize

<cControlContainerBlueprint-cControlValue d:id="707706">

<ControlName d:type="cDeltaString">LightSelector</ControlName>

<DefaultValue d:type="sFloat32" d:alt_encoding="000000000000F0BF" d:precision="string">-1</DefaultValue>

<MinimumValue d:type="sFloat32" d:alt_encoding="000000000000F0BF" d:precision="string">-1</MinimumValue>

<MaximumValue d:type="sFloat32" d:alt_encoding="0000000000000040" d:precision="string">2</MaximumValue>

<BriefDescription d:type="cDeltaString"></BriefDescription>

<LocalisedControlName>

<Localisation-cUserLocalisedString>

<English d:type="cDeltaString"></English>

<French d:type="cDeltaString"></French>

<Italian d:type="cDeltaString"></Italian>

<German d:type="cDeltaString"></German>

<Spanish d:type="cDeltaString"></Spanish>

<Dutch d:type="cDeltaString"></Dutch>

<Polish d:type="cDeltaString"></Polish>

<Russian d:type="cDeltaString"></Russian>

<Other/>

<Key d:type="cDeltaString"></Key>

</Localisation-cUserLocalisedString>

</LocalisedControlName>

<DetailedDescription d:type="cDeltaString"></DetailedDescription>

<ApplyToConsist d:type="cDeltaString">eFalse</ApplyToConsist>

<HUDControlID d:type="sUInt32">0</HUDControlID>

<InterfaceElements>

<cControlContainerBlueprint-cInteriorIrregularNotchedLever d:id="707727">

<ElementName d:type="cDeltaString">Untitled</ElementName>

<DifficultyType d:type="cDeltaString">Expert</DifficultyType>

<PickTransformName d:type="cDeltaString">LightSelector</PickTransformName>

<MovementType d:type="cDeltaString">MoveUpDown</MovementType>

<AnalogInputSensitivity d:type="sFloat32" d:alt_encoding="0000000000804340" d:precision="string">39</AnalogInputSensitivity>

<DigitalInputSensitivity d:type="sFloat32" d:alt_encoding="0000000000804340" d:precision="string">39</DigitalInputSensitivity>

39 is far to high speed to handle the light switch (with inputmapper). Average value like 4 is better.
Thank you for upcoming fix. The AFB breaking power fix will be great. With the default train, breaking with AFB from 160 Km/h to 140 Km/h slow down to 130 Km/h. It's even lower with the engine alone.

As part of the slow down with LZB/AFP, you have 1. Most engine have 0. 1 make the engine wait 1 second before breaking. This can be a cause of too late braking and overspeed. This can depend on yout engine script but I directly check this value when I noticed engine wait before enaging dynamic brake.

<DynamicBrakesSystem>

<EngineSimulation-cDynamicBrakeBlueprint d:id="591743">

<DelayBeforeEngaging d:type="sFloat32" d:alt_encoding="0000000000000000" d:precision="string">1</DelayBeforeEngaging>

As part of the slow down with LZB/AFP, you have 1. Most engine have 0. 1 make the engine wait 1 second before breaking. This can be a cause of too late braking and overspeed. This can depend on yout engine script but I directly check this value when I noticed engine wait before enaging dynamic brake.

the dynamic brake is completely driven over LUA, same as normal brakes and regulator ! with an Delay in it which is controlled by a function which calculate the user his FPS in realtime over interval to avoid different changing speeds, on this way im able to give same predictable results on 20fps vs 60 /100 Fps. AFB brake require more time to improve. should be done in AFB module itself, and speed up the system a little. one second delay doesnt do a big difference on brake apply/release, it can slightly improve to run over a 0 delay.