You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had big troubles getting the music tracks to work, but found a fix just now.
I made sure I had the correct naming scheme for the music files; track02.ogg through to track17.ogg or the corresponding casa1.ogg etc. all lowercase and that they were placed under "ux0:/data/Hexen II/cdtracks", but I could not get them to play in the vita port no matter what I did. Using .mid or .mp3 extensions did not work for me so ultimately I deleted all the config files that came with my PC installation of the game. autoexec.cfg, hexen.rc, config.cfg in the data1 folder and also a config.cfg in the portals folder. Only when I deleted the config.cfg in the portals folder did it work so I assume anyone else facing this issue only have to delete portals/config.cfg if you also have one.
Hope it helps anyone having the same issue.
Sorry for posting it as a bug, but I thought it might be a good idea to have this printed on the source page.
The text was updated successfully, but these errors were encountered:
I had big troubles getting the music tracks to work, but found a fix just now.
I made sure I had the correct naming scheme for the music files; track02.ogg through to track17.ogg or the corresponding casa1.ogg etc. all lowercase and that they were placed under "ux0:/data/Hexen II/cdtracks", but I could not get them to play in the vita port no matter what I did. Using .mid or .mp3 extensions did not work for me so ultimately I deleted all the config files that came with my PC installation of the game. autoexec.cfg, hexen.rc, config.cfg in the data1 folder and also a config.cfg in the portals folder. Only when I deleted the config.cfg in the portals folder did it work so I assume anyone else facing this issue only have to delete portals/config.cfg if you also have one.
Hope it helps anyone having the same issue.
Sorry for posting it as a bug, but I thought it might be a good idea to have this printed on the source page.
The text was updated successfully, but these errors were encountered: