Dokumentation VisionVersum

ORG:Veranstaltungen   |   Thematisches Saisonportfolio

---

Hardware Requirements:

• VisionVersum: GPU RAM: min 4GB (min NVidia Quadro P2000 or T1000) - CPU: min 3GHz, 4 Cores

• Tactical View: GPU RAM: min 2GB (NVidia recommended) - CPU: min 2GHz, 2 Cores
• All other: no special requirements

---

Recommended starting sequence:

1. Schilde
2. Visioneering
3. Camera Control
4. VisionVersum
5. Tactical View
6. Navigation
7. LongRange Scan

---

Development Plan:

Device	Availability	New Feature	Change Request	Experience (Mission Feedback)
Energieverteiler	?	Karl: Networking the energy distributor with VV: The further we move away from habitable planets and space stations, the higher the performance of our life support must be The closer we get to the atmosphere of a planet or other foreign body (nebula, asteroid, moon), the more we need to power our shields The further the distance that the pilot and/or navigator set, the more energy is needed on the drives to operate them at the required power level
VisionVersum	planned for 2024.10 (Bönen Space Center)	Docking maneuver/guidance system Holding clamps Crosshairs Airlock, pressure equalization Attitude control via digital autopilot Real-time information display Easy-to-use user interfaces Goran: Improved Warp effect	Enhancements: Video Messages Request/ Question: Karl: Docking then also possible in the hangar of the U.S.S. Excelsior? -> The first throw is aimed at a standardized docking opening/plate that can be used with as many objects as possible. Then there is the “Deep Space 9”, which has its own docking ports. The Excelsior is an exception because we practically fly into the spaceship. You would need something like the transport tubes from “Mondbasis Alpha 1 (Space 1999)” (https://mondbasis-alpha-1.fandom.com/de/wiki/Mondbasis_Alpha)
VisionVersum	planned for 2024.9 (Kassel)	Max sensor resolution faster/more frequent data transmission of ListOfPlanets?
Tactical View	planned for 2024.9 (Kassel)	Dynamic Course Line (Guiding Beam) make the line visible again adjust the line Tactical View dynamically
General	2024.8.c (Botanika)		Stability Tweak: Auto-Off console output after 3 minutes (The console output leads to the browser resources being eaten up and the browser session breaking at some point) Enhancements: Reduction of media redundancies
Astronomische Analyse (Planetenscanner)	2024.8.c (Botanika)		Enhancements: Goran: Can you make our sun white when you get the chance -> With a pure white sun, we lose the texture of the surface, but I was able to make the yellow a little whiter
Camera Control	2024.8.c (Botanika)
Control Board	2024.8.c (Botanika)	More communication channels and signal buttons added. Available Console Heartbeats: Main Screen Control Board Visioneering Shields Camera Control Planeten Untersuchung Transporter Typ 2 (Neogiliar) Astronomische Analyse (Planetenscanner) Amphibien
Energieverteiler	2024.8.c (Botanika)
Long Range Scanner	2024.8.c (Botanika)		Not recommended to use due to missing MQ integration and minor runtime errors
Navigation	2024.8.c (Botanika)	Transfer of the navigation database from the VV to the console via MQ	Incorrect display/refresh of destination buttons corrected English terms changed to German
Schilde	2024.8.c (Botanika)
Sonden Konsolen	2024.8.c (Botanika)	The probe consoles have been completely overhauled. The aim is to have just one single console for all probe missions in the future. In addition to the use of the MQ, the configuration of the target system and the associated images were modularized. In future, the target system will be transferred automatically from the VV or the navigation console. Currently, however, the target is still programmed statically, which requires different consoles (as before). The current status already makes it much easier to integrate new targets. Essentially, only the planet names and the corresponding images need to be entered in the source code.	Enhancements: The console automatically switches the camera settings in the VV to the optimum values so that you can see the probe flying without having to actively adjust the camera settings in the VV
Tactical View	2024.8.c (Botanika)		Orbits are only displayed in the Sol system Dynamic Course Line (Guiding Beam) not visible
VisionVersum	2024.8.c (Botanika)	Dynamic Course Line (Guiding Beam) Continuously recalculate the coordinates of the starting point and the orientation of the line	Performance Tweak: Spacedock without bitmaps Enhancements: Assignment of the flight stick changed: You can now select the drive (nozzle thrusters, impulse, warp) using the small button on the stick, which was previously only used to set the flight altitude. Goran: Can you make our sun white when you get the chance -> With a pure white sun, we lose the texture of the surface, but I was able to make the yellow a little whiter. -> The light emitted by the sun (to illuminate the solar system) is pure white Fixes: Double assignment of speed rocker and joystick rotation -> Use keyboard for camera rotation System constantly switches back and forth between Yellow Alert and Cruise Mode -> Auto Alert disabled Asteroid type uniformly reset to “Ice” Video Glitches with impulse drive: Not yet fixed, but workaround in place
Message Queues	2024.8.c (Botanika)	More and more communication channels between VV and the consoles are being converted from AJAX/JSON to MessageQueues: ListofPlanets ListOfShips Navigationsdatenbank Camera Control Alert State Incoming Transmissions Sensor Probe Handling Nebula settings + control	Enhancements: The consoles show a red flashing bar if the message queue server is not available Performance Tweak: The MQ reduces traffic on the IIS and the communication is much faster.

---

Development Environment:

• DELL Precision 5820
• Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz
• 120GB RAM
• NVIDIA Quadro P2000, 5GB RAM
• Samsung SSD 870 QVO 1TB
• Windows 11
• Notepad++