Phredreeke, on 16 July 2019 - 03:19 PM, said:
I think eduke32 requires you to set up a 32-bit video mode before it lets you set Polymost or Polymer in autoexec.cfg
My main eduke32.cfg already has that set, so should be good?
[Screen Setup]
Polymer = 0
ScreenBPP = 32
ScreenHeight = 2160
ScreenMode = 1
ScreenWidth = 3840
Forge, on 16 July 2019 - 03:47 PM, said:
I have 2 shortcuts in my HRP game directory, one for polymer, one for polymost & each with their own commandline parameters to use specific def files-hduke3d_hrp.def-hduke3d_hrp2.defduke3d_hrp.def is:// Extra additions to the game - High Resolution Pack//if polymost then include duke3d_hrp_polymost.def//else// include duke3d_hrp_polymer.def//endifduke3d_hrp2.def is:// Extra additions to the game - High Resolution Pack//if polymost then// include duke3d_hrp_polymost.def//else include duke3d_hrp_polymer.def//endifAll the hrp & def files are in the svnthese will select the proper HRP to use, but you still have to manually set the render mode & check the polymer box.If you want to have them pre-set, then you'll need to make specific cfg files to do that & ad the -cfg[filename.cfg] commandline to the shortcut
That's effectively what I'm doing now with my shortcuts:
"D:\Full Games\Duke Nukem 3D\eduke32_win64\eduke32.exe" -j "hrp" -h "duke3d_hrp_polymer.def" -nosetup -usecwd
"D:\Full Games\Duke Nukem 3D\eduke32_win64\eduke32.exe" -j "hrp" -h "duke3d_hrp_polymost.def" -nosetup -usecwd
I'm just trying to find a way to ensure the renderer is set appropriately when double clicking each shortcut. The autoexec.cfg file in subdirectories was looking beautiful, but failed during practice as EDuke32 just terminates after parsing the autoexec.cfg file.
My preference would be to always use Polymer as I don't have many performance issues with it and I think the FOV is better (Polymost seems to stretch heaps in the corners, half way between full 3D and Software's Y-shearing), but regressions like in R7736 onwards where I get a black screen when a relfective surface is shown necessitates some kind of fallback.
The only option I can think of now is using a batch script to parse eduke32.cfg and change the line "Polymer = 0/1" and change it appropriately upon launching. Doing that without mangling the file is difficult though.