ValveSoftware
glass texture on sphere crashes game
on mg_bob2 the sphere glass texture crashes the game
map was made on 2008-05-22 and it would be a pity to update a legendary map
fix would be to remove the glass texture sphere but that's very saddening.
Why are you submitting a map-related bug to the github, do you want Valve to recompile the map for you? I recompiled it myself and get no crash.
The map worked since 2008 :) but the x64 update broke the map and 17 years of people downloaded the map.
I believe the crash should be fixed so this does not happen considering how many have the map downloaded :)
People like to have a specialty, like a disco ball on their map for celebration, this is the ending zone of the MG map.
I have also learned this is an issue on the popular jb_hopjb_v12.
Valve please fix the crash issue on glass texture sphere's for the old and future maps, thank you!
There's something wrong with rendering in-game that valve needs to fix.
The map crashed long before the update hence why bhop_bob2_fixed has existed since at least 2009: https://gamebanana.com/mods/124132
And this specific crash doesn't even happen when I try to replicate it myself.
There's no map called bhop_bob2_fixed :) I think you mean mg_bob2_fixed? that's for something else fixed as the crash is there as well.
There are dozens of videos of this in 2012, people who have played MG knows the map has worked, but the update for x64 crashed the map. To be clear we are hoping valve will fix the rendering in-game for the glass texture on sphere so the game doesn't crash.
mg_bob2 - Dec 4, 2012 https://youtu.be/GQhjbBEdcAs&t=449
Here is a video of my game crashing for you. https://github.com/user-attachments/assets/f13ce2c8-1ffd-4089-89f3-0ebbd7932715
Use -condebug in launch options to generate a console log, as I said it doesn't happen globally and the crash will be a map issue not an engine issue (its a very bad piece of brush work)
From what I saw the brush work looked fine, a sphere is complex. people have to use that for a disco ball :)
Still though, 17 years the map worked, everyone has it, x64 broke the map!
https://pastebin.com/qEwm4yQt
Add developer 2 to console before going there. This map crashed before x64, hence the existence of multiple 'fix' versions of the map.
Well, I played MG for 4 years and I've only downloaded many many mg_bob2, and other's have beat the map... Go on a MG server with course timer and see how many finished without crashing :) So whatever was fixed had to be something else. The map worked fine until the x64 update.
https://pastebin.com/BB9YEtLC
Play around with your video settings; I cannot replicate this crash nor did the other person I got to try.
Hi, 2 other people had the same crashing issue. I tried to change various video settings and I still crash.
OS: Windows 10 Home Edition 64-Bit CPU: AMD FX-8320 Eight-Core Processor RAM: DDR3 12GB GPU: NIVIDIA GeForce GTX 1060 6GB
Similar crashes happen on coop_missile_silo where the rocket will crash clients running on the 64-bit client.
Found another one in surf_seaworld_fix
Sphere textured with nature/movingplane
setpos -763 316 -1067
Triggers the crash on this map instantly (its just when this object is rendered)
No logs were generated by developer2 that look useful
https://gamebanana.com/mods/122899
Here's a simple map that consistently crashes the game.
Just look up so that the sphere is rendered and you'll get a crash
I've remade it from scratch to ensure it's not some messed up geometry, this is a 16 sided sphere in hammer++ that reliably crashes.
Textured with any translucent texture crashes. Regular textures are fine.
When I tested with 15 or less sided spheres it renders fine. 16 or more sides crashes.
The crash doesn't occur on the 32-bit versions of CS:S, HL2DM, TF2, DOD:S and HLDM:S
The crash only occurs on the 64-bit versions of CS:S, HL2DM, TF2, DOD:S and HLDM:S
and also, the crash doesn't occur on the previous_build branches of CS:S, DOD:S, HLDM:S and HL2DM
Can replicate the crash on Windows with this map. Doesn't occur for me on x64 Linux.
Build Label: 9540945 # Uniquely identifies each build
Network PatchVersion: 9540945 # Determines client and server compatibility
Protocol version: 24 # High level network protocol version
Server version: 9540945
Server AppID: 232330
Client version: 9540945
Client AppID: 240
Crash stacktrace with a debugger attached: stacktrace.txt
The crash doesn't occur on the 32-bit version of CS:S (cstrike.exe)
The crash only occurs on the 64-bit version of CS:S on Windows (cstrike_win64.exe)
How you can start 32bit cstrike ?
You created an invalid solid, hence why that sphere crashes. I imagine the other spheres are also invalid solids.
I tested this on DOD:S and TF2 and it crashes those games too (crash_sphere bsp above)
Just have to setpos to -320 320 320
How you can start 32bit cstrike ?
- Browse your game files, where you see cstrike.exe and cstrike_win64.exe
- Create new shortcut of cstrike.exe
- Right click on the shortcut and select Properties
- In shortcut properties -> Target -> add this parameter in end
-force32bitex. "D:\SteamLibrary\steamapps\common\Counter-Strike Source\cstrike.exe" -force32bit - Launch the game from the shortcut
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7132#issuecomment-2713796229
It also crashes Half-Life Deathmatch: Source and Half-Life 2: Deathmatch on 64-bit:
https://github.com/user-attachments/assets/236b7884-d1c0-4e6c-8c65-772570c87c54
https://github.com/user-attachments/assets/1416ff3a-ea77-425d-b5d1-48e3ffd666c5
And also, here are the videos of the translucent texture sphere crash happening on 64-bit DOD:S and TF2:
https://github.com/user-attachments/assets/635f349c-6833-4f29-a862-4173cca98817
https://github.com/user-attachments/assets/783b0f83-261d-411c-a07b-b36a38bc97ec
Enter setpos -320 320 320 in the console so that the sphere is rendered and you'll get a crash
The issue is poor mapping so there is nothing for Valve to fix but you can add this to a stripper config to fix the issue.
filter:
{
"targetname" "discoball"
"classname" "func_rotating"
}
Github comments can't format it properly so here is the config with formatting: https://github.com/nekoclimb/stripper/blob/main/mg_bob2.cfg
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7132#issuecomment-2710325747
I tested the crash_sphere map on the previous_build branch and the crash doesn't happen there
The issue is poor mapping so there is nothing for Valve to fix but you can add this to a stripper config to fix the issue.
Should the solution be to remove all brushes with a lot of sides in every map ever made now? As mentioned above, there are multiple instances of maps crashing now where they didn't crash before the update. These are maps people play every day, so I'm not sure why you think they consistently crashed before. The fact is, this update messed a lot of stuff up and this is just one of them, or didn't you see all the new issues?
You created an invalid solid, hence why that sphere crashes. I imagine the other spheres are also invalid solids.
The brush is made using hammer sdk prefabs, it's not an invalid solid.
The issue is poor mapping so there is nothing for Valve to fix but you can add this to a stripper config to fix the issue.
Should the solution be to remove all brushes with a lot of sides in every map ever made now? As mentioned above, there are multiple instances of maps crashing now where they didn't crash before the update. These are maps people play every day, so I'm not sure why you think they consistently crashed before. The fact is, this update messed a lot of stuff up and this is just one of them, or didn't you see all the new issues?
There are issues with the brush, you can see these in Hammer. These brushes generate errors and always have. The map in question has always had crashes hence why it has a _fix version, I even remember crashing on the map myself in the past.
You created an invalid solid, hence why that sphere crashes. I imagine the other spheres are also invalid solids.
The brush is made using hammer sdk prefabs, it's not an invalid solid.
You can create invalid solids via prefabs.
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7132#issuecomment-2716142932
How? I made a 512x512 box on 2d view, selected sphere, 16 sides, and clicked prefab. Loaded in-game and my game crashed? what is invalid?
Replying to #7132 (comment)
How? I made a 512x512 box on 2d view, selected sphere, 16 sides, and clicked prefab. Loaded in-game and my game crashed? what is invalid?
also experienced crash, there's nothing invalid in this case, that user is trolling, ignore them
