From en.wiki.railvivid.railml.org
Jump to: navigation, search
This page refers to version 0.98a of railVIVID®.
Therefore the content is possibly outdated.
The current version is 1.1.


Texts are superimposed

This problem sometimes occurs in the graphic timetable view if the scaling is to small and the position of the operational points is very close (Section 'Graphic timetable').

Birne.png Tip: Use the Scaling -setting in the control window to equalize the view (see chapter 'Additive settings').

Labels in fields are cut off and end with "..."

This problem sometimes occurs in the vehicle view if the name in the railML file is long (see chapter ||Application_window_Rolling_Stock#Describing_vehicle_view | 'Describing vehicle view').

Birne.png Tip: Shift the vertical middle bar between the two views with the mouse to enlarge or shrink the desired (left) view.

Why do the station names look so strange?

If something like „BØY“ is expected, but is displayed as „B\351Y“, check the coding of your railML file. An easy test is to open the railML file in your web browser. If the names look strange there as well, it is probably a problem of your railML file. Otherwise, please contact the railVIVID team for further investigations. railVIVID supports both coding UTF-8 and Latin-x based on the system fonts. Probably railVIVID will not work with Chinese characters, though this was never tested.

Why can´t I see railML 3.0 mockup-Infrastructure?

The railML 3.0 development is currently very dynamic. The programme considers an early railML 3.0 mockup-status. In the meantime extensive changes could be implemented, which are currently not supported by the programme. It further is the task of future programme versions to fully implement a stable railML 3.0 schema and check all programme features with reliable test data. Some railML 3.0-elements of the first schemas are not implemented due to already outdated XML-schemas. In the meantime they are postponed or renamed. The following problems were reported so far:

  • If operational points shall be displayed with their name - as the railML 2 values of ocp/@name - please use nodes/*/operationalPoint/@name. Otherwise the names will not be used.
  • If tracks shall be displayed in the geographic view, please use the GML-alternative for the coordinates: geoPoint/gml:pos or geoLine/gml:posList. Otherwise the coordinates will not be used and the view will stay empty.

Which registry entries are created by railVIVID?

The registry entries in Windows systems are saved in the file: HKEY_CURRENT_USER/Software/JavaSoft/Prefs/ preferences and its subfiles. All registry entries can be exported if saved as ini-file (see chapter Menu bar item 'Settings'). Independent of all external data the registry entries are saved automatically in the application file during the usage of railVIVID. The following properties are saved:

1. TimetableView

(a) Register
(b) showTrainNo
(c) xzoom
(d) yzoom
(e) xySwitch
(f) gridColour
(g) backgroundColour
(h) Colorings

i. trainNumber
ii. trainType

2. TopoView

(a) showVMax
(b) showGeometry
(c) showTCS
(d) showElectrification
(e) textColour
(f) backgroundColour
(g) Colorings

i. trackElectrification
ii. trackSpeed
iii. trackTCS

3. common

(a) language
(b) version
(c) baseColor
(d) showFileInfoPopup
(e) filePath