VZX Player News

You can now choose to start VSXu with DirectSound or ASIO sound API support instead of the default "WASAPI". This could be helpful for people who have issues with WASAPI as well.

If you start VSXu Player from your library, you should get this dialog:



Do note that the help text will still say WASAPI if you select Directsound or ASIO. If this is too much of a hassle, we'll fix it in the next release!

Our discord:

https://vovoid.info

Take care!

Today a small update was pushed - VSXu Player v0.8.2.

The following bugs have been addressed:

• Automatic recording when starting - one had to change sound device back and forth for the player to start visualizing. We suspect that people with only one sound source could not use the player at all.
  
• Window position was not saved when config pane was not open
  
• Possible fix: The slowdown that some users experienced when having paused the progression and moving the mouse seemed for one of the testers to be fixed. If someone can repeat this error, please contact us.
  

The following improvements have been implemented:

• Better text when player not hearing sound, referring to FAQ and discord for help.
  

Otherwise we're working on the next visual pack - it will be called "Networks" and feature visuals representing this theme. If you want to follow development, we post screenshots in our discord once in a while.

https://discord.gg/vovoid

Take care!

Today's small patch should help users on laptops where they accidentally launch the software using the embedded graphics instead of the discrete graphics.

Also, this should be helpful for users who missed that Intel HD Graphics is not supported should they lack a discrete GPU.

The error message looks like this:


Before the application just exited silently without saying anything which was very confusing.

Hope it helps!

Today a small update was pushed which enables you to launch the player multiple times on one computer and at the same time as playing a game via Steam.

To do this, you have to execute the .EXE file directly from Windows - not through Steam.

If you right-click VSXu Player and select "Properties", you can find the tab "Local Files", if you click "Browse Local Files..." you should get an explorer window for the directory where VSXu has been installed. (Or if you know where your Steam library is - just go there with windows explorer.)

Once viewing this directory, double-click the "vsxu_store_player.exe" to start it.

Now it will still detect Steam and integrate with it and at the same time free up Steam for launching other things.

[h2]Creating WIndows Shortcut to VSXu Player[/h2]
Being able to start it like this means you can also create a windows shortcut to it - for inclusion on desktop or task bar for instance.

[h2]Running a game and VSXu at the same time[/h2]
This technique also enables you to run VSXu and a game at the same time - just don't start VSXu through Steam at all, but through the exe file directly and then launch the game on Steam like you do normally. Useful for the Streamers out there!

[h2]What was changed?[/h2]
Since this is not a change in the code, the version number is still the same. All that was done was to add the file "steam_appid.txt".

The following bugs were fixed:

• Minimum / base value of transition between visuals was not saved when application closed. You can find this value on the main player bar, the clock symbol.
  This is initially a minimum of 60 s per visual, in the screenshot it's been changed to 70.
  
• Some left-over DLC debugging code was removed (not a problem for anyone but not good either)