QW-Group / ezquake-source

main ezQuake source code base
https://www.ezquake.com/
GNU General Public License v2.0
265 stars 122 forks source link

BUG: standard renderer throws glsl compilation errors #569

Closed ciscon closed 3 years ago

ciscon commented 3 years ago

switching to std renderer gets:

repeated error

0:32(9): error: syntax error, unexpected NEW_IDENTIFIER VertexShader.Compile() failed Shader->Compile(8B31) failed 0:31(9): error: syntax error, unexpected NEW_IDENTIFIER VertexShader.Compile() failed Shader->Compile(8B31) failed 0:32(9): error: syntax error, unexpected NEW_IDENTIFIER VertexShader.Compile() failed Shader->Compile(8B31) failed 0:32(9): error: syntax error, unexpected NEW_IDENTIFIER VertexShader.Compile() failed ]map dm1 VM_Load: "qwprogs" Place of Two Deaths == Cheats are enabled == Error: Unable to create lightmap texture array: error 1281 Error: Unable to create lightmap texture array: error 1281 Shutting down SDL audio.

crash

on separate std/glsl builds, the std build still appears to work fine other than those shader compilation errors still appearing, though bgnr is using the combined build but doesn't have the crash when playing a demo yet doesn't see players.

ticketjp commented 3 years ago

[]()Hi I had same issue + invisible player model/skin when watching demos (didnt joined a server) and i noticed a big penalty in timedemo performance (3x more to complete) to a earlier build from just some weaks ago. Tested in linux, in 2 diff setups, one with a nvidia gfx on nouveau driver and another on intel igpu, with freshly compiled binaries in both setups, on vanilla ezquake, but using personal cfg. I append cfg if needed. 1.cfg.txt Thanks for your attention! ezquake000 ezquake002 (url)

ciscon commented 3 years ago

still getting those shader errors when switching to standard

meag commented 3 years ago

Hi ciscon

I could reproduce (other) program compilation errors on AMD drivers by fixing the len=0 check (https://github.com/ezQuake/ezquake-source/commit/df5b1a9912ddc6dd634266d1b980ef71a6bc9969)

If you could try again and confirm if still broken? Can't reproduce exactly what you've got, linux machine here can't run modern but will try and get something up and running. Can you confirm if it happens starting up in classic, or if using classic-only build?

Thanks, meag

ciscon commented 3 years ago

just did a pull and recompile, still getting the error even when starting up with vid_renderer 0


ezQuake &c1e13.6-dev-alpha9-dev&r r7109~956ceae4

<1d><1e><1e><1e><1e> &c1e1ezQuake Initialized&r <1e><1e><1e><1e><1f> Type /help to access the manual. Use /describe for help on commands. execing /home/ciscon/games/quake/qw/autoexec.cfg ]map ultrav couldn't exec server.cfg VM_Load: "qwprogs" &cf00Warning&r: weapon scripts will be executed client-side &cf00Warning&r: high-lag teleport fix not available <02>UltraViolence == Cheats are enabled == ciscon entered the game You got armor Shader->Compile(8B31) failed 0:29(9): error: syntax error, unexpected NEW_IDENTIFIER VertexShader.Compile() failed Shader->Compile(8B31) failed 0:30(9): error: syntax error, unexpected NEW_IDENTIFIER ...
meag commented 3 years ago

Hi ciscon

Can you try that with developer 1 set before starting the map? Should hopefully tell us which program is failing. Will update debugging messages if that doesn't help...

Thanks,

ciscon commented 3 years ago

here's where it starts:

Compiling: aliasmodel-std[16] Shader->Compile(8B31) failed 0:29(9): error: syntax error, unexpected NEW_IDENTIFIER VertexShader.Compile() failed Compiling: aliasmodel-std[17] Shader->Compile(8B31) failed 0:30(9): error: syntax error, unexpected NEW_IDENTIFIER

attached is the full log.

ezqoutput.txt

meag commented 3 years ago

Thanks ciscon - that helps :)

ciscon commented 3 years ago

groovy ;)

meag commented 3 years ago

Hopefully fixed now...

ciscon commented 3 years ago

just tried it, looks good.

ticketjp commented 3 years ago

Solved here too Thanks for the work