[erledigt] TCP Status Zugverband - Fahrzeugdateiname
Verfasst: 04.02.2017 12:43:36
Hallo Carsten,
I have been experiencing a problem with the Status Zugverband data sent via TCP.
Background information:
For some vehicles the Grunddaten details are contained in the main .rv.fzg file. For others these Grunddaten details are not in the main .rv.fzg file but rather in an external file that is linked from a Fahrzeug-Variante. This is legitimate (provided there is only a single Grunddaten defined for a specific vehicle) and currently works absolutely fine in the simulator. Some examples that have functioning separated Grunddaten details are the BR151, BR103 etc.
The problem relates to the Fahrzeugdateiname sent as per Doku 11.3.3.3.7. When the corresponding vehicle .rv.fzg file directly contains the Grunddaten details the Fahrzeugdateiname is sent correctly.
Some examples:
For BR111 (Grunddaten contained in 111.rv.fzg):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche4\Elektroloks\BRD\111\111.rv.fzg
For E10 (Grunddaten contained in E10.rv.fzg):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche3\Elektroloks\BRD\Einheitsloks\E10.rv.fzg
For BR120 (Grunddaten contained in 120.rv.fzg):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche4\Elektroloks\BRD\120\120.rv.fzg
However, it seems that when the Grunddaten has been linked via an Externe-Datei in a Variante section of the main .rv.fzg file the resulting Fahrzeugdateiname is not as expected.
Some examples:
For BR103 (Grunddaten in various Variante specific Externe-Datei):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche3\Elektroloks\BRD\E03\Gemeinsame_Daten\DB_103_216-245_SBS_Grunddaten.fzg
(Not the expected 103.rv.fzg)
For BR151 (Grunddaten in various Variante specific Externe-Datei):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche4\Elektroloks\BRD\151\Fahrzeugdaten\151_Grunddaten_DBS54.fzg
(Not the expected 151.rv.fzg)
I am currently using these Status Zugverband details in my client and this inconsistency is creating an issue in correctly reading all the fahrzeug details that I need. If possible it would be good to have just the main .rv.fzg filename sent in every case.
MfG
Steven.
I have been experiencing a problem with the Status Zugverband data sent via TCP.
Background information:
For some vehicles the Grunddaten details are contained in the main .rv.fzg file. For others these Grunddaten details are not in the main .rv.fzg file but rather in an external file that is linked from a Fahrzeug-Variante. This is legitimate (provided there is only a single Grunddaten defined for a specific vehicle) and currently works absolutely fine in the simulator. Some examples that have functioning separated Grunddaten details are the BR151, BR103 etc.
The problem relates to the Fahrzeugdateiname sent as per Doku 11.3.3.3.7. When the corresponding vehicle .rv.fzg file directly contains the Grunddaten details the Fahrzeugdateiname is sent correctly.
Some examples:
For BR111 (Grunddaten contained in 111.rv.fzg):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche4\Elektroloks\BRD\111\111.rv.fzg
For E10 (Grunddaten contained in E10.rv.fzg):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche3\Elektroloks\BRD\Einheitsloks\E10.rv.fzg
For BR120 (Grunddaten contained in 120.rv.fzg):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche4\Elektroloks\BRD\120\120.rv.fzg
However, it seems that when the Grunddaten has been linked via an Externe-Datei in a Variante section of the main .rv.fzg file the resulting Fahrzeugdateiname is not as expected.
Some examples:
For BR103 (Grunddaten in various Variante specific Externe-Datei):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche3\Elektroloks\BRD\E03\Gemeinsame_Daten\DB_103_216-245_SBS_Grunddaten.fzg
(Not the expected 103.rv.fzg)
For BR151 (Grunddaten in various Variante specific Externe-Datei):
Fahrzeugdateiname sent via TCP is: RollingStock\Deutschland\Epoche4\Elektroloks\BRD\151\Fahrzeugdaten\151_Grunddaten_DBS54.fzg
(Not the expected 151.rv.fzg)
I am currently using these Status Zugverband details in my client and this inconsistency is creating an issue in correctly reading all the fahrzeug details that I need. If possible it would be good to have just the main .rv.fzg filename sent in every case.
MfG
Steven.