Beiträge von ES64F4

  zahnpabst,
Ich habe gestern die BR 146 von RailTraction mit vR-IC-Wagen ausprobiert und habe keine Ansicht 5. Mit einer anderen Lokomotive habe ich erwartungsgemäß Ansicht 5 im Inneren der IC-Wagen.

BR 146.2 and 146.3 arrive. RailTraction agreed. This is awaiting publication by Rail-Sim.de.
Available : BR 146.2 and 146.3 DB repaint

The BR 146.2 and 146.3 are ready. I'm waiting for Railtraction's agreement to share them.

Railtraction : Is publishing repaints allowed ?

I made the BR 146.2 and 146.3 with theirs specifications (ZZA color, side logo and numbering).
I also add some missing side informations (160 Km/h D and brakes) on all models.

I used the same red as vR even if it is not the real red of the BR 146. It will be easier to make compositions with the Dostos.

Die Arbeiten sind noch im Gange... Die Unterseite des Chassis hat jetzt vorne ihren roten Bereich.
Die Lokomotive BR 146 279-5 hat eine Kontrollnummer. Dies ist laut RailcolorArchive eine Ausnahme in der Serie.

It's all done !
BR 146 2005 with wide strip, large side logo and green ZZA
BR 146 2015 with mid strip, small side logo, no control number and amber ZZA

DB BR 146 244-9 wip...

BR 146 244-9

[RT] BR 146-5 Fernverkehr

Zitat von IvanDakota99

Hallo. Gute Nacht, wie ist alles? Ich schreibe in dieses Forum, um zu fragen, ob jemand anderes diesen Fehler erhält, wenn er das Installationsprogramm für das Traxx BR 146-2-Produkt ausführt, das kürzlich gestartet wurde. Ich erhalte diesen Fehler, ohne das Add-on installieren zu können, und dann springt es Auf der letzten Seite des Installationsprogramms steht, dass ein Fehler vorliegt, den ich nach dem Ausführen des Installationsprogramms usw. getestet habe. Wissen Sie, woran dieser Fehler liegen könnte? Ich habe den Serienschlüssel, da das Produkt gekauft wurde ...

Danke für eure Antworten

Ivan

Die Dame kaufte neue Kleidung.

Weitere Lokomotiven mit neuen Nummern sind eingetroffen.

WIP...

The spark is always located at pantograph 2 regardless of the pantograph raised.

<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>

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.

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.

Zitat von Railtraction

Please Have a little patients, with uploading and releasing inputmappers, report your wishes to us and we check into it! I will launch this evening or tomorrow internal release version 1-1 to our beta testers. If that is oké i launch it in the store.

till now there is no show stopping bug reported , almost everything is controllable by cabin control or hud. switch zugart also work, switch on pzb and use control+8 , hold the button combination till pzb symbol switch to next zugart, and release. There is on the zugart U one issue with the uv mapping which is internal already solved, you see 40 instead of blue 55 .

I always add every driving feature in the inputmapper (except sunbling, open door, open windows, etc)... I also change sensitivty to my wishes if needed.
Panto up/down

Panto selection
Main switch
Cab light
Desk light
Instrument light
Engine light / long distance light
Wiper on/off
Wiper speed
Hand brake

Do you plan to add all ?