ΔV: Wiki - User contributions [en]

DV Annotate

2024-12-05T03:39:08Z

NimrodX: /* Bug Reporting */ fix markup (i keep using Markdown by accident)

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

This is a human-readable script for Windows PowerShell 5.1 (the powershell.exe that ships with Windows 10 and later). You can [https://github.com/NimrodXMods/dv-annotate/tree/main/windows/build download it from the GitHub repo here.]

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in PowerShell but no knowledge of PowerShell or command lines is needed to run it.
[[File:Dv-annotate-screenshot1.png|alt=Screenshot of dv-annotate's Annotate tab|frame|Annotate Tab]]
[[File:Dv-annotate-screenshot2.png|alt=Screenshot of dv-annotate's Review tab|frame|Review Tab]]
[[File:Dv-annotate-screenshot3.png|alt=Screenshot of dv-annotate's Archive tab|frame|Archive Tab]]

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (PowerShell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to '''review it''' because it's a good idea to look for anything suspicious in scripts before running them.)

'''To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".'''

The first time it is run it will do a "lightweight install" which means it will offer to move itself to <code>%AppData%\dV-annotate\</code> and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

After running for the first time it will create a settings file in <code>%AppData%\dV-annotate\</code>.

It can be completely removed by just deleting <code>%AppData%\dV-annotate\</code> and the shortcut.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab. Settings are stored in: <code>%AppData%\dV-annotate\prefs.json</code>

I tried to do as much autoconfiguration as possible with reasonable defaults.

If you want to modify the script yourself, all the important functions are at the top of the file and all the ugly tool-generated GUI stuff is toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it before launching the game. (There's a "Launch dV" button in the Archive tab to make this easier.)

During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. By default, the game will automatically pause when it gets sent to the background (unless you changed this in settings).

As long as you have the Annotate tab selected, the input focus will switch to the textbox, the timestamp will be updated to "now", and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing. So switch, type, switch, and the game should pause while typing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled for the game.)

The script by default will try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete older screenshots to keep them out of the archive.

You can also set your own screenshots folder manually. This folder will get used to include any jpg or png files newer than the last annotation log reset. Since it can't tell if a image is a screenshot of the game, it's a good idea to use a folder that only contains screenshots of dV. Any screenshot utility can be used or you can just manually place screenshot images in the directory you set.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting that happened is saved in the game save data. Creating the archive at other times isn't terrible but isn't as useful as doing so at this time.

The script '''can archive the game directory while the game is running''' without any problems, so quitting the game is not required.

==Windows Download==

Download the script from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/windows/build dv-annotate.ps1]

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The scripts can be downloaded from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/bash-steamos-linux-osx dv-annotate.sh]

I threw these scripts together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above, but require familiarity with bash command line usage.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

=Questions?=

For questions or other discussion, see the [https://discord.gg/dv Delta V Discord] <code>#workshop</code> channel thread.

=Bug Reporting=

For information on troubleshooting and bug reporting info, see the '''bottom section''' of the [[Troubleshooting]] page.

DV Annotate

2024-12-05T03:37:03Z

NimrodX: add link to Troubleshooting page

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

This is a human-readable script for Windows PowerShell 5.1 (the powershell.exe that ships with Windows 10 and later). You can [https://github.com/NimrodXMods/dv-annotate/tree/main/windows/build download it from the GitHub repo here.]

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in PowerShell but no knowledge of PowerShell or command lines is needed to run it.
[[File:Dv-annotate-screenshot1.png|alt=Screenshot of dv-annotate's Annotate tab|frame|Annotate Tab]]
[[File:Dv-annotate-screenshot2.png|alt=Screenshot of dv-annotate's Review tab|frame|Review Tab]]
[[File:Dv-annotate-screenshot3.png|alt=Screenshot of dv-annotate's Archive tab|frame|Archive Tab]]

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (PowerShell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to '''review it''' because it's a good idea to look for anything suspicious in scripts before running them.)

'''To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".'''

The first time it is run it will do a "lightweight install" which means it will offer to move itself to <code>%AppData%\dV-annotate\</code> and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

After running for the first time it will create a settings file in <code>%AppData%\dV-annotate\</code>.

It can be completely removed by just deleting <code>%AppData%\dV-annotate\</code> and the shortcut.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab. Settings are stored in: <code>%AppData%\dV-annotate\prefs.json</code>

I tried to do as much autoconfiguration as possible with reasonable defaults.

If you want to modify the script yourself, all the important functions are at the top of the file and all the ugly tool-generated GUI stuff is toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it before launching the game. (There's a "Launch dV" button in the Archive tab to make this easier.)

During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. By default, the game will automatically pause when it gets sent to the background (unless you changed this in settings).

As long as you have the Annotate tab selected, the input focus will switch to the textbox, the timestamp will be updated to "now", and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing. So switch, type, switch, and the game should pause while typing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled for the game.)

The script by default will try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete older screenshots to keep them out of the archive.

You can also set your own screenshots folder manually. This folder will get used to include any jpg or png files newer than the last annotation log reset. Since it can't tell if a image is a screenshot of the game, it's a good idea to use a folder that only contains screenshots of dV. Any screenshot utility can be used or you can just manually place screenshot images in the directory you set.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting that happened is saved in the game save data. Creating the archive at other times isn't terrible but isn't as useful as doing so at this time.

The script '''can archive the game directory while the game is running''' without any problems, so quitting the game is not required.

==Windows Download==

Download the script from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/windows/build dv-annotate.ps1]

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The scripts can be downloaded from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/bash-steamos-linux-osx dv-annotate.sh]

I threw these scripts together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above, but require familiarity with bash command line usage.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

=Questions?=

For questions or other discussion, see the [https://discord.gg/dv Delta V Discord] <code>#workshop</code> channel thread.

=Bug Reporting=

For information on troubleshooting and bug reporting info, see the **bottom section** of the [[Troubleshooting]] page.

DV Annotate

2024-12-04T22:56:55Z

NimrodX: fix up the article and correct errors and such

DV Annotate

2024-12-04T22:25:18Z

NimrodX: add screenshots and improve formatting of them

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

This is a human-readable script for Windows PowerShell 5.1 (the powershell.exe that ships with Windows 10 and later).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in PowerShell but no knowledge of PowerShell or command lines is needed to run it.
[[File:Dv-annotate-screenshot1.png|alt=Screenshot of dv-annotate's Annotate tab|frame|Annotate Tab]]
[[File:Dv-annotate-screenshot2.png|alt=Screenshot of dv-annotate's Review tab|frame|Review Tab]]
[[File:Dv-annotate-screenshot3.png|alt=Screenshot of dv-annotate's Archive tab|frame|Archive Tabn]]

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (PowerShell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to '''review it''' because it's a good idea to look for anything suspicious in scripts before running them.)

'''To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".'''

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man usally. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Windows Download==

Download the script from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/windows dv-annotate.ps1]

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The gist linked to below contains bash scripts I hacked together help with bug reports. I threw these together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

==Unix Download==

The scripts can be downloaded from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/bash-steamos-linux-osx dv-annotate.sh]

File:Dv-annotate-screenshot3.png

2024-12-04T22:15:11Z

NimrodX:

Screenshot of dv-annotate Archive tab

File:Dv-annotate-screenshot2.png

2024-12-04T22:14:05Z

NimrodX:

Screenshots of dv-annotate, number 2

File:Dv-annotate-screenshot1.png

2024-12-04T22:12:30Z

NimrodX:

Screenshots of dv-annotate, number 1

DV Annotate

2024-12-03T11:31:32Z

NimrodX: change links to point to new github repo

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

[[Image:DV_Annotate-image.png|300px|thumb|right]]This is a human-readable script for Windows PowerShell 5.1 (the powershell.exe that ships with Windows 10 and later).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in PowerShell but no knowledge of PowerShell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (PowerShell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to '''review it''' because it's a good idea to look for anything suspicious in scripts before running them.)

'''To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".'''

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man usally. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Windows Download==

Download the script from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/windows dv-annotate.ps1]

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The gist linked to below contains bash scripts I hacked together help with bug reports. I threw these together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

==Unix Download==

The scripts can be downloaded from GitHub here: [https://github.com/NimrodXMods/dv-annotate/tree/main/bash-steamos-linux-osx dv-annotate.sh]

DV Annotate

2024-11-25T21:48:12Z

NimrodX: br tags

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

[[Image:DV_Annotate-image.png|300px|thumb|right]]This is a human-readable script for Windows Powershell 5.1 (the powershell.exe that ships with Windows 10).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in powershell but no knowledge of powershell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (powershell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 review it] because it's a good idea to look for anything suspicious in scripts before running them.)

To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man ually. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Windows Download==

Download the script from GitHub Gist here: [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 dv-annotate.ps1]<br />
Use the "Raw" or "Download Zip" buttons in the upper right to download.

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The gist linked to below contains bash scripts I hacked together help with bug reports. I threw these together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

==Unix Download==

The scripts can be downloaded from this GitHub Gist: [https://gist.github.com/NimrodXMods/1c0cbd519cc357d4e23d8611be41bc5f dv-annotate.sh]<br />
(Use the "Download ZIP" button in the upper right).

DV Annotate

2024-11-25T21:46:06Z

NimrodX: /* Download */ br

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

[[Image:DV_Annotate-image.png|300px|thumb|right]]This is a human-readable script for Windows Powershell 5.1 (the powershell.exe that ships with Windows 10).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in powershell but no knowledge of powershell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (powershell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 review it] because it's a good idea to look for anything suspicious in scripts before running them.)

To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man ually. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Download==

Download the script from GitHub Gist here: [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 dv-annotate.ps1]
Use the "Raw" or "Download Zip" buttons in the upper right to download.<br />.
These assume that you know what you're doing with 'bash' and how to run these kinds of shell scripts.

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The gist linked to below contains bash scripts I hacked together help with bug reports. I threw these together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

==Download==

The scripts can be downloaded from this GitHub Gist: [https://gist.github.com/NimrodXMods/1c0cbd519cc357d4e23d8611be41bc5f dv-annotate.sh] (use the "Download ZIP" button).

DV Annotate

2024-11-25T21:43:51Z

NimrodX: /* dv-annotate bash Scripts (Linux/SteamOS/OSX) */ Add gist link.

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

[[Image:DV_Annotate-image.png|300px|thumb|right]]This is a human-readable script for Windows Powershell 5.1 (the powershell.exe that ships with Windows 10).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in powershell but no knowledge of powershell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (powershell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 review it] because it's a good idea to look for anything suspicious in scripts before running them.)

To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man ually. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Download==

Download the script from GitHub Gist here: [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 dv-annotate.ps1]
Use the "Raw" or "Download Zip" buttons in the upper right to download. These assume that you know what you're doing with 'bash' and how to run these kinds of shell scripts.

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The gist linked to below contains bash scripts I hacked together help with bug reports. I threw these together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

==Download==

The scripts can be downloaded from this GitHub Gist: [https://gist.github.com/NimrodXMods/1c0cbd519cc357d4e23d8611be41bc5f dv-annotate.sh] (use the "Download ZIP" button).

DV Annotate

2024-11-25T21:41:25Z

NimrodX: add unix dv-annotate scripts

This page describes two different "dv-annotate" tools: one GUI-based utility for Windows, and one package of simple bash scripts for Linux/SteamOS/OSX. These are for keeping notes on when problems happen (annotations) and creating a zip or tgz archive of the game data directory to aid in debugging.

=dV-Annotate Windows Utility=

[[Image:DV_Annotate-image.png|300px|thumb|right]]This is a human-readable script for Windows Powershell 5.1 (the powershell.exe that ships with Windows 10).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in powershell but no knowledge of powershell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (powershell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 review it] because it's a good idea to look for anything suspicious in scripts before running them.)

To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man ually. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Download==

Download the script from GitHub Gist here: [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 dv-annotate.ps1]
Use the "Raw" or "Download Zip" buttons in the upper right to download. These assume that you know what you're doing with 'bash' and how to run these kinds of shell scripts.

=dv-annotate bash Scripts (Linux/SteamOS/OSX)=

The gist linked to below contains bash scripts I hacked together help with bug reports. I threw these together quickly just for myself, so they’re pretty minimal. But I fixed them up some in case anyone else wants to use them. They're roughly the equivalent of the windows utility above.

I use these on SteamOS but they should work on any Linux and probably OSX if the pathnames are set properly.

===dv-archive.include.sh===
Edit this to set pathnames and such for screenshots. Not much needs changing here, but OSX will need more changes.

===dv-annotate===
Run this to save a comment plus the timestamp of when you started the script and the file name of the most recent screenshot in the screenshots dir.

===dv-archive===
Run this to archive the dV game directory along with the annotations and screenshots taken since the first annotation.

===dv-show-annotations===
Run this to review current annotations or the ones in the most recent archive.

DV Annotate

2024-11-25T21:08:54Z

NimrodX: Add liink to gist containing the script and add more instructions.

=dV-Annotate: Windows utility for tracking events and creating a zip for bug reports=

[[Image:DV_Annotate-image.png|300px|thumb|right]]This is a human-readable script for Windows Powershell 5.1 (the powershell.exe that ships with Windows 10).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in powershell but no knowledge of powershell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (powershell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 review it] because it's a good idea to look for anything suspicious in scripts before running them.)

To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want and it will still work.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text file PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, hit Enter, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

===Including Screenshots (optional)===

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default try to find the Steam screenshots folder for Delta V, and will include screenshots that were taken since the annotation log was reset. Therefore you don't need to delete screenshots to keep them out of the archive.

You can also set your own screenshots folder man ually. This folder will also get used to include any jpg or png files newer than the last annotation log reset.

===When to Archive===

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Download==

Download the script from GitHub Gist here: [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 dv-annotate.ps1]
Use the "Raw" or "Download Zip" buttons in the upper right to download.

File:DV Annotate-image.png

2024-11-25T20:55:36Z

NimrodX: Screenshot of the GUI of the dv-annotate.ps1 script.

== Summary ==
Screenshot of the GUI of the dv-annotate.ps1 script.

DV Annotate

2024-11-25T20:48:34Z

NimrodX: Add link to GitHub Gist containing the script

=dV-Annotate: Windows utility for tracking events and creating a zip for bug reports=

This is a human-readable script for Windows Powershell 5.1 (the powershell.exe that ships with Windows 10).

It is a GUI utility to help people using Windows archive game logs, saved games, screenshots, and also timestamps of events for bug reports. I wrote it in powershell but no knowledge of powershell or command lines is needed to run it.

The reason for a script like this is that it can be rather difficult to keep track of when different things happen during gameplay that might be relevant for debugging, and the more timestamps and descriptive info the developer can get, the less time they have to spend looking for stuff. So this can save a lot of developer time and also make it more possible to discover more issues, etc.

==Installation/Setup==

This is just a plain text .ps1 (powershell) script, but it creates a GUI so you don't need to run it from the command line. Just download the .ps1 file and save it wherever it's convenient.

If you double click on the script it won't execute, but instead should get opened in a text editor. (I encourage everyone to review it because it's a good idea to look for anything suspicious in scripts before running them.)

To actually run it, just right-click on dv-annotate.ps1 in Windows Explorer and select "Run with PowerShell".

The first time it is run it will create a settings file in <code>%AppData%\dV-annotate\</code>. It will then offer to move itself to that directory and create a shortcut in its current location that will allow it to be run in a normal manner without opening a terminal window. This shortcut can be moved anywhere you want.

==Configuration==

If you need to change any paths or settings, see the '''Archive''' tab.

And if you want to modify the script yourself, all the important functions are at the top of the file will all the ugly tool-generated GUI stuff being toward the bottom. It's just a normal plain text PowerShell script, so it can be read and edited with any text editor.

==Usage==

The easiest way to use this is to run it and minimize it before launching the game. During the game, just bring the window to the front by using <code>Alt+Tab</code>, type in a comment, then <code>Alt+Tab</code> again to make it go away and go back to playing. Having the "Auto-pause in background" option enabled in dV's settings will be useful.

As long as you have the Annotate tab selected, the input focus will switch to the textbox and so you can just <code>Alt+Tab</code>, Type a comment, hit enter, and <code>Alt+Tab</code> again to go back to playing.

If using Steam then you can use <code>F12</code> to take screenshots of anything interesting. (This requires having the Steam Overlay enabled.) The script by default will look for screenshots to include in the archive that are newer than when the annotation (comment) log was created.

The recommended time to create the .zip archive is '''after returning to Enceladus''' (which saves the game) but '''before exiting the game'''. This helps to ensure that the Godot engine log doesn't get blown away and that anything interesting is saved in the game save.

The script '''can archive the game directory while the game is running''' without any problems.

==Download==

Download the script from GitHub Gist here: [https://gist.github.com/NimrodXMods/e642e10d50953ef7f8abce7e308c0633 dv-annotate.ps1]

DV Annotate

2024-11-25T19:05:16Z

NimrodX: add more stuff and add file link

DV Annotate

2024-11-25T18:54:55Z

NimrodX: initial version of page for this utility script

Troubleshooting

2024-11-25T18:45:00Z

NimrodX: add support and bug reporting section

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

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

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]