ΔV: Wiki - User contributions [en]

Troubleshooting

2025-09-10T05:06:29Z

Koder: Add information about windows compatibility mode ruining performance

== Game settings ==
This game does not assume that it knows better than you what your computer can do and allows you to tweak many things, from the way the rendering engine works down to the accuracy of your physics simulation. Unfortunately, this means that you can configure the game in a way that makes it run really bad on your computer. Here are some tips for what to look out for:

* If you are running into performance problems, try the default settings first. The defaults should deliver a sane performance across most systems.
* If running 4k display with a graphics card that has insufficient pixel fill performance, you can run into performance issues caused by the pixel drawing bottlenecks in the display system. This most commonly happens on laptops with 4k displays. Lowering the "Resolution Scale" slider by 4 notches and raising the "HUD Scale" slider up to the point where the HUD is clearly visible will solve this.
* If you set the display to "No FPS limit" and turn off the "VSync" you are basically telling your GPU to run at 100% all the time, up to overheating. For best results:
** On variable-framerate monitors (G-Sync, FreeSync) set the framerate limit to something you are comfortable with looking at.
** For classical monitors, use VSync to not render frames that would not be visible either way.
* A high "Physics Simulation FPS" setting will put a high demand on your CPU. If you turn it up to a high value, and not have the "Dynamic Temporal Simulation Simplification" option turned on, you might experience extreme slowdowns any time something demanding happens with the physics, like simulating exhausts from multiple ships or breaking many asteroids. For best results, leave the "Physics Simulation FPS" at the default value of 60, and have DTSS enabled at all times.

== External compatibility ==
There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* If using AMD Ryzen hardware, make sure that your system runs in the Ryzen-dedicated power plan. [https://asapguide.com/ryzen-balanced/ See this guide].
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Using GSync, FreeSync or similar variable refresh rate monitor will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occasionally on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*On some systems, the exclusive full-screen mode works much faster than the borderless window mode.
*Some driver HDR features can prevent the game window from showing up at all. If you hear the game playing, but see your desktop, try disabling HDR on your monitor.
*When using a mouse with a very high polling rate (ie. 8000 Hz) you can experience degraded performance when moving your mouse cursor. You can use '''--accumulate-input''' command-line option to enable in-game workaround, or decrease your polling rate.
*On some systems enabled AMD Enhanced Sync Technology caused the game to not display at all. You can turn that option off in your Adrenaline software panel, under Gaming -> Graphics -> Advanced Settings.
*Running the game in Windows Compatibility Mode will hurt your performance a lot. This might be caused by setting the compatibility mode on the game directly, or running through a launcher (Steam Client, GOG Galaxy, etc) set to run in compatibility mode.

== Support and Bug Reporting ==
If you encounter a game bug, either with running the game or in gameplay, please zip/tar and upload your game data/log directory:

* Windows: <code>%AppData%\dV</code> or <code>$APPDATA\dV</code> or <code>$env:APPDATA\dV</code> (AppData is a hidden directory in Windows, so to open ΔV's data directory in windows explorer, hit <code>Win+R</code> to open a run window, and type <code>%appdata%\dv</code>)
* Linux: <code>~/.local/share/dV/</code> or <code>~/.var/app/com.valvesoftware.Steam/data/dV/</code>
* Mac: <code>~/Library/Application Support/dV</code>

Please zip the entire directory, including your logs, saves and settings. Koder can use that data to attempt to recreate the bug. If you did something specific that caused the problem, describing it will also help a lot.

You can alternatively use the <code>DV Annotate</code> tool, which automatically packages logs and screenshots for bug reports, and provides a few other useful tools. More info can be found on this page: [[DV Annotate]]

Upload/send your bug report to:
* Upload it directly on Discord [https://discord.com/invite/dv https://discord.com/invite/dv] channel [https://discord.com/channels/426287934870781952/1019875051480289281 #bug-reports] for real-time feedback.
* Email to [mailto:support@kodera.pl support@kodera.pl]
Do note that if mods are installed and running when the problem occurs, Koder will likely flag it as <code>using mods</code> as a lot of the time the issue originates within one of the installed mods. Please see if the issue can be replicated without mods installed before reporting.

Crew

2025-04-02T12:52:46Z

Koder: /* Experience */ The gains in the rings are granted if ship is moving above 5m/s, not 50m/s

Crew help your ship with various functions. Every crew member comes with an associated [[Agenda]]. Each crew member has exactly one of the four different professions: Geologist, Astrogator, Mechanic, and Pilot, and works on a (mostly) fixed monthly salary starting from the date of hire.

== Menus ==
[[File:Active Crew Menu.png|thumb|488x488px]]

==== Crew ====
This menu will let you manage your currently hired crew.

Each crew member will show their name, occupation, education level, experience level, monthly salary, and the in-game date where their salary is due next, alongside their portrait, the button to activate/deactivate them from the current ship, dismiss them from your crew, and if your ship is not full on crew, how their skills affect the general ability they would provide to the ship (red arrows mean they negatively affect it, from a little to a lot, gray means that no stat changes if they are on your ship, and green means they benefit you from your current crew's capabilities.

The top of this menu provides context to the current ship (excluding total salary), including the number of crew active on a ship out of the total able to be placed on it, (from the pilot): the adrenal slowdown percentage & course anticipation, (from the mechanic): the repair limit of parts and the jury-rig efficiency, (from the geologist): the price prediction accuracy and the mineral discovery range, (and from the astrogator): the tactical awareness range and coordinate tracking time. More info on these is provided in each profession's info later down the page.
[[File:Hire Crew Menu.png|thumb|486x486px]]

==== Hire ====
This menu is where you go to hire new crew. There is no limit to how many crew you can hire, except of course how capable you are of being able to pay them their salaries.

The information shown here is decently similar to what's shown on the section for your current crew. Do note that the arrows still are compared to who's currently on your ship.

The education and experience stats, albeit just as useful on the ''Your Crew'' menu, they become a lot more important when hiring as it affects how much they charge, and is why it is included in this section. These stats are continuous, but the interface only shows "milestones" of skill - for example, if someone's education is shown as "Self-Taught", that may mean an internal education stat anywhere from 0 to 0.25. Each profession has two skills, each scaling with one of the stats. Crew members also have a mostly-hidden Morale stat, which affects their skills.

Some things to consider when hiring crew is what you need and how quickly it's needed. If you cannot afford much, going with a cheaper crew is better, compared to if you need a good crew quick you might have to splurge. One trick used is to hire good crew to train a cheaper one, then get rid of the expensive crew when they are no longer needed. See further below for info on training.

Crew can have a very wide span of wages based on their experience and education, however the minimum and maximum possible for each role is listed here:
* pilot: 400 / 48 400 E$
* mechanic: 400 / 48 400 E$
* geologist: 600 / 72 600 E$
* astrogator: 500 / 60 500 E$
== Professions ==

==== Geologist ====
Education skill: '''Price prediction accuracy'''. Determines accuracy of price prediction by your geologist - both on station in Mineral Market and during ring dive.

Experience skill: '''Mineral discovery range'''. Geologist will estimate compositions and prices of minerals within a radius around your ship.
* Without a geologist on board, it's not possible to identify compositions of mineral chunks (except visually - they look differently depending on mineral and purity). This makes them rather essential crew members.

==== Astrogator ====
Education skill: '''Tactical awareness range'''. Astrogator will highlight ships around you by their transponders.
* Fairly essential to be able to detect threats, derelicts, and other ships outside of visual range.

Experience skill: '''Coordinate tracking time'''. The constantly shifting planescape of the rings makes it challenging to trace a specific location. Your astrogator will be able to keep track of them for a limited time.
* Without an astrogator on board, you won't be able to astrogate to waypoints. If at any moment you end up without any astrogators in your employ, you will furthermore lose all saved waypoints. This makes having an astrogator essential.

==== Mechanic ====
Education skill: '''Jury-rig efficiency'''. Changes how far mechanic can push your ship systems in OMS menu during ringdive.
* Can be very useful, e.g. turning a critical reactor leak that would cause the ship to run out of propellant in seconds into a merely concerning one.

Experience skill: '''Repair limit'''. Extends how much your mechanic can repair during maintenance on Enceladus prime station.
* Most equipment is significantly cheaper to repair than to replace (although some isn't), so this allows saving on repairs.
* Note, however, that repairs take more time that replacements, and you'll have to pay for crew wages and hotels in the meantime, which for large and skilled crews may be more expensive than the repair savings.

==== Pilot ====
Education skill: '''Adrenal slowdown'''. When in danger, pilot's perception of time will slow down.
* Available even without a pilot, albeit only a small slowdown.

Experience skill: '''Course anticipation'''. Pilot will predict the course of your ship and all surrounding objects to determine if ship is in danger of collision.
* This automatically enables adrenal slowdown if a collision is predicted to happen in that time, given the current velocity.
* Often toggles unnecessarily.

== Training ==
With time spent in your crew, crew members gradually improve. Education is improved both by spending time on[[Enceladus Prime | Enceladus]] as well as within the rings, whereas doing profession-specific actions during dives increases Experience. The more advanced in a skill a crew member is, the slower they progress further.

The only thing that accelerates learning is having another crewmember of the same profession, who is better in the relevant skill, tutor them. The gain is determined by the difference of their skills, but caps at 2x the normal learning rate - so in total, a crewmember can learn at most at trice the normal learning rate (if they are completely unskilled and tutored by someone perfect).

=== Education ===
The formula for education is as follows: 
if the current Education (which goes from 0 to 1) is y, then the gain per day is

<code>
y' * 1day = (1-y)/400 + (A-y)/200
</code>

where A is the highest Education level among crewmembers with the same profession (so if there's nobody better, then A=y and that term is zero).

Without tutoring, the solution to this differential equation is <code>y(t) = 1 - (1-y(0))*exp(-t/(400*day))</code>. So the Education level exponentially decays towards perfection, with a characteristic time of 400 days. For example, it takes 115 days for an initially completely unskilled crewmember to reach the first milestone of 0.25.

=== Experience ===
The formula for rate of skill gain is the same for Experience as for Education. However, instead of being per day of time, Experience experience is gained by going actions. If there are multiple crewmembers with the same occupation on the ship, all of them gain the full experience amount.

The actions are as follows: 
* Geologists: identifying mineral chunks, depending on value (1 day per 60 000 E$ of value)
* Astrogators: detecting ships (seems to be 2 days per ship detected); discovering points of interest
* Mechanics: repairing or replacing parts (1 day's worth per 4 hours spent doing that)
* Pilot: evading collisions (per unit of time flying the ship while under the pilot's automatic adrenaline)
* Entire crew: flying through the rings at more than 5 m/s (0.5 days per minute).

== Multiple Crew of Same Profession ==
Having multiple crew of the same profession on a ship can provide additional benefits besides the tutoring mentioned earlier, which will happen anywhere.

==== Aiding In a Job ====
Having multiple crew of the same profession can assist with the speed and/or effective capability of the task at hand.

* Geologists work in tandem, and will identify <code>n</code> mineral chunks at a time, where n is the number of geologists
* Astrogators can identify ships faster and do so in tandem
* Mechanics will lower the amount of time to repair/replace equipment (only affects at the time of repair, counts every mechanic you have instead of who's on board)

==== Spare Crew ====
Crew may be unable to continue doing their job in the rings with a multitude of causes. From this, if a task is necessary enough for you not to want to take risks, having extra crew may hold additional benefits. Geologists and astrogators especially benefit from the extra help, as they can seriously hamper a dive and may cause an early return.
{| class="wikitable mw-collapsible mw-collapsed"
|+Causes for Crew Incapacitations
!Incapacitated how?
!Cause
|-
|Injured themselves
|When attempting to salvage a derelict with a crewmember, there's a chance of failure and the crew can injure themselves. This may not always be the case after a failed attempt.
|-
|Piloting ship
|After a successful salvage using a crewmember, they will need to pilot the ship back to Enceladus Prime, and cannot remotely do their job
|-
|Singing Job
|If you have a singer onboard, they may request to take some leave to perform a job. It is recommended to let them do it as they may leave your crew otherwise.
|}

== Morale ==
[[File:Crew Morale Example.png|thumb|Three crew members with higher morale]]
Morale is a hidden stat of each crew member, and goes from -0.5 to 0.5. Morale is shown directly at Enceladus when its absolute value is more than 0.3, by happy/sad icons on the crew members in question.

Usually, morale gradually decays to 0 over time. Good accommodations (good hotels for the time on the station, or particularly comfortable ships like the [[OCP-209]] or the [[Peacock Prospector]] for the time spent in dives) or bad ones (like the [[Vulture Prospector]]) change this point of stability. Some services, like good hotels or The Twins, also have an instant effect on morale. Purchasing drinks in the rings from dedicated suppliers will also positively affect morale for any crew currently on your ship.

Some [[Agenda]] events may affect morale. Also, not paying a crew member's wages will cause their morale to rapidly decrease.

Morale modifies the value of skills as <code>modified = original^(1-morale)</code>. This only applies to the effects of skills, and not to training (happier crew members don't learn or teach faster). The effects of morale are more significant for low skill levels. For example, morale of 0.3 increases a base skill of 0.25 to 0.37, but a base skill of 0.75 only to 0.81.

More info can be found on the [[morale]] page.

Troubleshooting

2025-03-10T15:52:44Z

Koder: adds information about AMD Enhanced Sync Technology incompatibility

== Game settings ==
This game does not assume that it knows better than you what your computer can do and allows you to tweak many things, from the way the rendering engine works down to the accuracy of your physics simulation. Unfortunately, this means that you can configure the game in a way that makes it run really bad on your computer. Here are some tips for what to look out for:

* If you are running into performance problems, try the default settings first. The defaults should deliver a sane performance across most systems.
* If running 4k display with a graphics card that has insufficient pixel fill performance, you can run into performance issues caused by the pixel drawing bottlenecks in the display system. This most commonly happens on laptops with 4k displays. Lowering the "Resolution Scale" slider by 4 notches and raising the "HUD Scale" slider up to the point where the HUD is clearly visible will solve this.
* If you set the display to "No FPS limit" and turn off the "VSync" you are basically telling your GPU to run at 100% all the time, up to overheating. For best results:
** On variable-framerate monitors (G-Sync, FreeSync) set the framerate limit to something you are comfortable with looking at.
** For classical monitors, use VSync to not render frames that would not be visible either way.
* A high "Physics Simulation FPS" setting will put a high demand on your CPU. If you turn it up to a high value, and not have the "Dynamic Temporal Simulation Simplification" option turned on, you might experience extreme slowdowns any time something demanding happens with the physics, like simulating exhausts from multiple ships or breaking many asteroids. For best results, leave the "Physics Simulation FPS" at the default value of 60, and have DTSS enabled at all times.

== External compatibility ==
There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* If using AMD Ryzen hardware, make sure that your system runs in the Ryzen-dedicated power plan. [https://asapguide.com/ryzen-balanced/ See this guide].
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Using GSync, FreeSync or similar variable refresh rate monitor will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occasionally on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*On some systems, the exclusive full-screen mode works much faster than the borderless window mode.
*Some driver HDR features can prevent the game window from showing up at all. If you hear the game playing, but see your desktop, try disabling HDR on your monitor.
*When using a mouse with a very high polling rate (ie. 8000 Hz) you can experience degraded performance when moving your mouse cursor. You can use '''--accumulate-input''' command-line option to enable in-game workaround, or decrease your polling rate.
*On some systems enabled AMD Enhanced Sync Technology caused the game to not display at all. You can turn that option off in your Adrenaline software panel, under Gaming -> Graphics -> Advanced Settings.

== Support and Bug Reporting ==
If you encounter a game bug, either with running the game or in gameplay, please zip/tar and upload your game data/log directory:

* Windows: <code>%AppData%\dV</code> or <code>$APPDATA\dV</code> or <code>$env:APPDATA\dV</code> (AppData is a hidden directory in Windows, so to open ΔV's data directory in windows explorer, hit <code>Win+R</code> to open a run window, and type <code>%appdata%\dv</code>)
* Linux: <code>~/.local/share/dV/</code> or <code>~/.var/app/com.valvesoftware.Steam/data/dV/</code>
* Mac: <code>~/Library/Application Support/dV</code>

Please zip the entire directory, including your logs, saves and settings. Koder can use that data to attempt to recreate the bug. If you did something specific that caused the problem, describing it will also help a lot.

You can alternatively use the <code>DV Annotate</code> tool, which automatically packages logs and screenshots for bug reports, and provides a few other useful tools. More info can be found on this page: [[DV Annotate]]

Upload/send your bug report to:
* Upload it directly on Discord [https://discord.com/invite/dv https://discord.com/invite/dv] channel [https://discord.com/channels/426287934870781952/1019875051480289281 #bug-reports] for real-time feedback.
* Email to [mailto:support@kodera.pl support@kodera.pl]
Do note that if mods are installed and running when the problem occurs, Koder will likely flag it as <code>using mods</code> as a lot of the time the issue originates within one of the installed mods. Please see if the issue can be replicated without mods installed before reporting.

MediaWiki:Emailsender

2024-11-06T15:56:24Z

Koder:

MediaWiki:Emailsender

2024-11-06T07:22:01Z

Koder:

ΔV: Wiki

MediaWiki:Emailsender

2024-11-06T07:14:11Z

Koder:

MediaWiki:Emailsender

2024-11-05T20:55:22Z

Koder: Created page with "=?UTF-8?Q?=CE=94V: Wiki?= <wiki@kodera.pl>"

=?UTF-8?Q?=CE=94V: Wiki?= <wiki@kodera.pl>

Troubleshooting

2024-05-11T19:12:15Z

Koder: Added information on mouses with high polling rates

Troubleshooting

2024-05-11T13:26:22Z

Koder: Add HDR information

Troubleshooting

2024-01-10T07:03:56Z

Koder:

Troubleshooting

2024-01-10T07:02:39Z

Koder:

Troubleshooting

2024-01-10T06:58:27Z

Koder: Add description for the Ryzen High Performance power plan.

Troubleshooting

2023-11-05T12:44:33Z

Koder: Added headers

Troubleshooting

2023-11-05T12:43:46Z

Koder: Added information about in-game settings that can cause problems

This game does not assume that it knows better than you what your computer can do and allows you to tweak many things, from the way the rendering engine works down to the accuracy of your physics simulation. Unfortunately, this means that you can configure the game in a way that makes it run really bad on your computer. Here are some tips for what to look out for:

* If you are running into performance problems, try the default settings first. The defaults should deliver a sane performance across most systems.
* If running 4k display with a graphics card that has insufficient pixel fill performance, you can run into performance issues caused by the pixel drawing bottlenecks in the display system. This most commonly happens on laptops with 4k displays. Lowering the "Resolution Scale" slider by 4 notches and raising the "HUD Scale" slider up to the point where the HUD is clearly visible will solve this.
* If you set the display to "No FPS limit" and turn off the "VSync" you are basically telling your GPU to run at 100% all the time, up to overheating. For best results:
** On variable-framerate monitors (G-Sync, FreeSync) set the framerate limit to something you are comfortable with looking at.
** For classical monitors, use VSync to not render frames that would not be visible either way.
* A high "Physics Simulation FPS" setting will put a high demand on your CPU. If you turn it up to a high value, and not have the "Dynamic Temporal Simulation Simplification" option turned on, you might experience extreme slowdowns any time something demanding happens with the physics, like simulating exhausts from multiple ships or breaking many asteroids. For best results, leave the "Physics Simulation FPS" at the default value of 60, and have DTSS enabled at all times.

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Using GSync, FreeSync or similar variable refresh rate monitor will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occasionally on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*On some systems, the exclusive full-screen mode works much faster than the borderless window mode.

Troubleshooting

2023-11-05T12:07:41Z

Koder: Remove obsolete M1 information, which was fixed by a workaround

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Using GSync, FreeSync or similar variable refresh rate monitor will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occasionally on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*On some systems, the exclusive full-screen mode works much faster than the borderless window mode.

Troubleshooting

2023-09-07T08:47:14Z

Koder: Added workaround information for crashes on M1 Mac systems

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Using GSync, FreeSync or similar variable refresh rate monitor will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occasionally on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*On some Mac M1 systems, game will crash when you attempt to switch full-screen mode or resize a window. This is an engine bug that developers have filed against the Godot Engine and are awaiting fix; however, there is a workaround available. Adding --render-thread safe to the game launch options (command line options) will cause it to not use multi-threading and fix the crashes, but will degrade the performance, as rendering will not be using all the available CPU cores anymore.

Troubleshooting

2023-08-22T07:02:28Z

Koder: Typos

Troubleshooting

2023-08-22T07:00:13Z

Koder: Merge two lists; both present problems that can cause performance

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Usinv GSync, FreeSync or similar variable refresh rate montior will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occassionaly on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.

Troubleshooting

2023-07-30T13:19:38Z

Koder:

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Usinv GSync, FreeSync or similar variable refresh rate montior will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occassionaly on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.

The following doesn't cause a crash, but can significantly impair the experience.
*If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.

Troubleshooting

2023-05-31T12:48:55Z

Koder: Adds AMD PRO driver information

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* Please make sure your system meets the minimum hardware requirements for the game.
* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
* AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
*Corrupted Windows files. Try to verify your system for corrupted files using the [https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e Windows System File Checker tool].
*The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
*Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
*Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
*The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Usinv GSync, FreeSync or similar variable refresh rate montior will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occassionaly on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.

Troubleshooting

2023-05-31T05:21:45Z

Koder: Add note about observing the minimum hardware requirements

Troubleshooting

2023-02-12T08:33:22Z

Koder: Added note about Razer Corte

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
* The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
* Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
* Nahimic OSD service is known to cause crashes when enabled.
* NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
* The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
*Usinv GSync, FreeSync or similar variable refresh rate montior will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
*GSync and FreeSync are reported to cause the game to flash occassionaly on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
*Running Razer Cortex software in background was reported to cause worse performance.

Troubleshooting

2022-12-07T11:53:17Z

Koder: Add information about VRR monitors and VSync

Troubleshooting

2022-11-16T06:59:56Z

Koder: Adds GSync/FreeSync info

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least [https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-7-1 driver version 22.7.1] which contain significant performance enhancements.
*Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
* The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
* Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
* Nahimic OSD service is known to cause crashes when enabled.
* NVIDIA control panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA control panel and in "Manage 3D settings" set "Let the 3D application decide".
*GSync and FreeSync are reported to cause the game to flash occassionaly on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.

Troubleshooting

2022-11-02T19:16:43Z

Koder: Re-phrase Unsupported GPU problem with AMD cards.

Troubleshooting

2022-10-09T09:35:21Z

Koder: Add information about specific AMD driver version that improves performance.

Troubleshooting

2022-08-21T09:24:16Z

Koder: adds NVidia display freeze description and solution to it

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers.
* The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
* Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
* Nahimic OSD service is known to cause crashes when enabled.
*NVIDIA control panel can be set up to override any setting the game makes and, in case of dV and few other games, freezes the display. Go to your NVIDIA control panel and in "Manage 3D settings" set "Let the 3D application decide".

Troubleshooting

2022-04-18T09:59:48Z

Koder: Trim the troubleshooting page to just the essential text

There are a couple of things that we know can crash Delta V, which aren't in our reach:

* At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers.
* The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
* Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
* Nahimic OSD service is known to cause crashes when enabled.

Troubleshooting

2022-04-18T09:57:33Z

Koder: Created page with "Koder has always had a policy with Delta V that feature work never progresses while replicable bugs exist. Fixes always come first. But some bugs aren't within his power to address. Some are in the engine, some are in drivers, some are in particular applications and the way they interact with the engine or drivers. So while there are few known causes for CTD that remain unresolved, there are a couple of things that we know can crash Delta V, which aren't in our reach. A..."

Koder has always had a policy with Delta V that feature work never progresses while replicable bugs exist. Fixes always come first. But some bugs aren't within his power to address. Some are in the engine, some are in drivers, some are in particular applications and the way they interact with the engine or drivers.

So while there are few known causes for CTD that remain unresolved, there are a couple of things that we know can crash Delta V, which aren't in our reach.
At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers.
The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
As always, we're interested in hearing about and fixing the problems you encounter. The best way to get our attention is in the #bug-reports channel on our discord.[discord.gg]

In #bug-reports, please read the pinned post, which will direct you to the location of your game files to submit with your issue. Please note that everything there is helpful. We ask for the whole directory because every file is of use. Your settings and saves help us duplicate your game and conditions, and many of the various log files all have different data about a single session.

Main Page

2022-04-18T09:57:00Z

Koder: /* Browse... */

[[file:Header.png|frame|center]]

Welcome to the '''ΔV: Rings of Saturn''' Wiki!

= The year is 2273 =
The unexpected discovery of valuable minerals within the rings of Saturn has sparked a thriving space excavation industry. You control an asteroid excavation ship hoping to make it rich out on the rings, but soon you find out that all is not as it appears. Experience a hard sci-fi story backed up with real physics and science.

[[File:k37-tntrl.png|frame|center|500px]]

= Browse... =
<p class="gamep">
[[:Category:Ships|Ships]]
[[:Category:Equipment |Equipment]]
[[:Category:Events |Events]]
[[Crew]]
[[Codex]]
[[Guides]]
[[FAQ|Frequently Asked Questions]]
[[Troubleshooting]]
</p>

== Key Features ==

* Realistic top-down hard sci-fi space flight experience. Every aspect of gameplay is backed up by real science. Ships fly just as spacecraft should.
* Jump into action in seconds with autopilot assist or save fuel by manual thruster maneuvers.
* Detailed ship simulation down to every subsystem - upgrade your ship, fix or even jury-rig broken systems on the fly. Every system failure will impact gameplay - adapt to survive in the hostile environment of space.
* Discover the mystery of the Rings, or just try to get rich leading your excavation company.
* Plan your strategy back on Enceladus Prime station. Sell your output, upgrade your ship, hire the crew and manage your company.

<div id="home-card-discord" class="home-card home-card--col2 home-card--button">[https://discord.gg/dv [[File:Discord wordmark white.svg|x30px|link=|alt=Discord]]]</div>

[https://store.steampowered.com/app/846030/V_Rings_of_Saturn/ [[File:Steam.svg|x30px|link=|alt=Steam]]]

==Editors Wanted==
[[Getting Started with Editing]]

[[Tips & Tricks]]

Did You Know??

Featured Article

Articles Wanted

Search

Popular Pages

Link to Steam, Homepage, discord, steam forums

Main Page

2022-02-13T09:19:56Z

Koder:

[[file:Header.png|frame|center]]

Welcome to the '''ΔV: Rings of Saturn''' Wiki!

= The year is 2273 =
The unexpected discovery of valuable minerals within the rings of Saturn has sparked a thriving space excavation industry. You control an asteroid excavation ship hoping to make it rich out on the rings, but soon you find out that all is not as it appears. Experience a hard sci-fi story backed up with real physics and science.

[[File:k37-tntrl.png|frame|center|500px]]

= Browse... =
<p class="gamep">
[[:Category:Ships|Ships]]
[[:Category:Equipment |Equipment]]
[[:Category:Events |Events]]
[[Crew]]
[[Codex]]
[[Guides]]
[[FAQ|Frequently Asked Questions]]</p>

[https://store.steampowered.com/app/846030/V_Rings_of_Saturn/ Steam]

== Key Features ==

* Realistic top-down hard sci-fi space flight experience. Every aspect of gameplay is backed up by real science. Ships fly just as spacecraft should.
* Jump into action in seconds with autopilot assist or save fuel by manual thruster maneuvers.
* Detailed ship simulation down to every subsystem - upgrade your ship, fix or even jury-rig broken systems on the fly. Every system failure will impact gameplay - adapt to survive in the hostile environment of space.
* Discover the mystery of the Rings, or just try to get rich leading your excavation company.
* Plan your strategy back on Enceladus Prime station. Sell your output, upgrade your ship, hire the crew and manage your company.

<div id="home-card-discord" class="home-card home-card--col2 home-card--button">[https://discord.gg/dv [[File:Discord wordmark white.svg|x30px|link=|alt=Discord]]]</div>

==Editors Wanted==
[[Getting Started with Editing]]

Did You Know??

Featured Article

Articles Wanted

Search

Popular Pages

Link to Steam, Homepage, discord, steam forums

MediaWiki:Common.css

2022-02-02T14:07:10Z

Koder:

MediaWiki:Common.css

2022-02-02T14:06:14Z

Koder:

.gamep a {
border: 1px solid white;
border-radius:16px 0px 16px 0px;
font-family:Audiowide;
text-align:left;
vertical-align: middle;
font-size:22px;
display:inline;
padding:0 2em;
box-shadow: 0px 0px 4px 4px rgba(255, 255, 255, 0.60);
}

.gamep a:hover {
border: 1px solid white;
border-radius:16px 0px 16px 0px;
font-family:Audiowide;
text-align:left;
vertical-align: middle;
font-size:22px;
display:inline;
padding:0 2em;
box-shadow: 0px 0px 4px 4px rgba(255, 255, 255, 0.80);
}

Main Page

2022-02-02T14:05:49Z

Koder: /* Browse... */

[[file:Header.png]]

Welcome to the '''ΔV: Rings of Saturn''' Wiki!

= The year is 2273 =
The unexpected discovery of valuable minerals within the rings of Saturn has sparked a thriving space excavation industry. You control an asteroid excavation ship hoping to make it rich out on the rings, but soon you find out that all is not as it appears. Experience a hard sci-fi story backed up with real physics and science.

[[File:k37-tntrl.png|frame|center|500px]]

= Browse... =

<p style="border: 1px solid white;border-radius:16px 0px 16px 0px;font-family:Audiowide;text-align:left;display:inline;font-size:22px;padding:0 2em">Test2</p>
<p style="border: 1px solid white;border-radius:16px 0px 16px 0px;font-family:Audiowide;text-align:left;display:inline;font-size:22px;padding:0 2em">[[K37]]</p>

<p class="gamep"> Test_class </p>

<p id="test"> Test </p>

<p class="gamep">
[[:Category:Ships|Ships_class]]
[[:Category:Ships|Ships]]
[[:Category:Equipment |Equipment]]
[[:Category:Events |Events]]
[[Crew]]
[[Codex]]
[[Guides]]
[[FAQ|Frequently Asked Questions]]</p>

[https://store.steampowered.com/app/846030/V_Rings_of_Saturn/ Steam]

== Key Features ==

* Realistic top-down hard sci-fi space flight experience. Every aspect of gameplay is backed up by real science. Ships fly just as spacecraft should.
* Jump into action in seconds with autopilot assist or save fuel by manual thruster maneuvers.
* Detailed ship simulation down to every subsystem - upgrade your ship, fix or even jury-rig broken systems on the fly. Every system failure will impact gameplay - adapt to survive in the hostile environment of space.
* Discover the mystery of the Rings, or just try to get rich leading your excavation company.
* Plan your strategy back on Enceladus Prime station. Sell your output, upgrade your ship, hire the crew and manage your company.

<div id="home-card-discord" class="home-card home-card--col2 home-card--button">[https://discord.gg/dv [[File:Discord wordmark white.svg|x30px|link=|alt=Discord]]]</div>

==Editors Wanted==
[[Getting Started with Editing]]

Did You Know?

Featured Article

Articles Wanted

Search

Popular Pages

Link to Steam, Homepage, discord, steam forums

Module:Test

2022-02-01T10:41:44Z

Koder: Created page with "local capiunto = require 'capiunto' local p = {} function p.main(frame) local args = frame:getParent().args local headerStyle if args.headerstyle and args.headerstyle ~= '' then headerStyle = string.format('background-color:%s;', args.headerstyle) else headerStyle = 'background-color:grey;' end local retval = capiunto.create( { title = args.title, headerStyle = headerStyle, } ) :addImage( args.image, args..."

local capiunto = require 'capiunto'

local p = {}

function p.main(frame)
local args = frame:getParent().args
local headerStyle
if args.headerstyle and args.headerstyle ~= '' then
headerStyle = string.format('background-color:%s;', args.headerstyle)
else
headerStyle = 'background-color:grey;'
end
local retval = capiunto.create( {
title = args.title,
headerStyle = headerStyle,
} )
:addImage( args.image, args.caption )
:addRow( 'Foo', args.foo )
:addHeader( 'A header between the data rows' )
:addRow( 'Bar', args.bar )
return retval
end

return p

Template:Infobox

2022-01-31T22:02:22Z

Koder: Reverted edits by Hyperflare (talk) to last revision by User:[[wikipedia:>Primefac|wikipedia:>Primefac]]

{{#invoke:Infobox|infobox}}<includeonly>{{template other|{{#ifeq:{{PAGENAME}}|Infobox||{{#ifeq:{{str left|{{SUBPAGENAME}}|7}}|Infobox|[[Category:Infobox templates|{{remove first word|{{SUBPAGENAME}}}}]]}}}}|}}</includeonly><noinclude>
{{documentation}}

</noinclude>

Template:Div col

2022-01-31T22:02:02Z

Koder: Reverted edits by Hyperflare (talk) to last revision by User:[[wikipedia:>Matt Fitzpatrick|wikipedia:>Matt Fitzpatrick]]

<includeonly><templatestyles src="Div col/styles.css"/><div class="div-col {{#ifeq:{{{small|}}}|yes|div-col-small}} {{#ifeq:{{{rules|}}}|yes|div-col-rules}} {{{class|}}}" {{#if:{{{colwidth|}}}{{{gap|}}}{{{style|}}}|style="{{#if:{{{colwidth|}}}|column-width: {{{colwidth}}};}}{{#if:{{{gap|}}}|column-gap: {{{gap}}};}}{{#if:{{{style|}}}|{{{style}}}}}"}}>{{#if:{{{content|}}}|{{{content}}}</div>}}{{#ifeq:{{{small|}}}|yes|[[Category:Pages using div col with small parameter]]}}</includeonly>{{#invoke:Check for unknown parameters|check|unknown={{main other|[[Category:Pages using div col with unknown parameters|_VALUE_{{PAGENAME}}]]}}|preview=Page using [[Template:Div col]] with unknown parameter "_VALUE_"; use colwidth= to specify column size |ignoreblank=y | class | colwidth | content | gap | rules | small | style }}<noinclude>
{{Documentation}}
</noinclude>

Crew

2022-01-31T21:34:38Z

Koder: Use bullet list for crew

Crew help your ship with various functions. Every crew member comes with an associated [[Agenda]].

* Geologist
* Astrogator
* Mechanic
* Pilot

User talk:Koder

2022-01-31T21:27:16Z

Koder: Created page with "Test."

Test.

File:Background.jpg

2022-01-30T19:03:39Z

Koder:

File:Favicon.png

2022-01-28T15:28:45Z

Koder:

File:Delta-v-logo.png

2022-01-28T15:23:04Z

Koder: