Kapo Posted November 16, 2021 Share Posted November 16, 2021 NAME: see title DESCRIPTION: Started Ocean, Map loaded but stayed all black, crash. REPRODUCIBILITY: dont know, never happend before SCREENSHOT/VIDEO: none neccessary LOG: attached ADDITIONAL INFORMATION: after a short search this seems not to have been reported _log_proxy_crash.log crashdata.mdmp Quote Link to comment Share on other sites More sharing options...
Kubik Posted November 16, 2021 Share Posted November 16, 2021 (edited) you can go to a config and try: "maxshader": 1280,, or "maxshader": 1025,, or "maxshader": 1024,, if any of these 3 values will help. config is "Documents\BattleForge\config.json" I believe your current value is "maxshader": 768, Edited November 16, 2021 by Kubik correct the number Quote Link to comment Share on other sites More sharing options...
Kapo Posted November 16, 2021 Author Share Posted November 16, 2021 (edited) 1 hour ago, Kubik said: you can go to a config and try: "maxshader": 1280,, or "maxshader": 1024,, or "maxshader": 1024,, if any of these 3 values will help. config is "Documents\BattleForge\config.json" I believe your current value is "maxshader": 768, Now I really wonder why you colored that in that particular way. The higher the better? Edits config and adds "maxshader":65535, And yes, current config was 768 Edited November 16, 2021 by Kapo Quote Link to comment Share on other sites More sharing options...
Kubik Posted November 16, 2021 Share Posted November 16, 2021 kind of 😞 it is much more complicated than that, and I do not really follow what was released yet to main server and what not. But simplification can be that 1280 mean allow DX 11 or lower, 1025 mean allow DX 10.1 or lower, 1024 means allow DX 10 or lower, 768 means DX 9.0c (or lower part get really complicated here) And one thing we changed is default value in case the number is not know by BF, from fallbacking to 768 (DX 9.0c), to 1280 (up to DX 11). (so using 65535 result in either 768, or 1280, based on if that change is live already) problem is that all of these implementations are broken and crash for some people, so there is no value that would work for everyone 😞 Kapo likes this Quote Link to comment Share on other sites More sharing options...
Kapo Posted November 16, 2021 Author Share Posted November 16, 2021 14 minutes ago, Kubik said: kind of 😞 it is much more complicated than that, and I do not really follow what was released yet to main server and what not. But simplification can be that 1280 mean allow DX 11 or lower, 1025 mean allow DX 10.1 or lower, 1024 means allow DX 10 or lower, 768 means DX 9.0c (or lower part get really complicated here) And one thing we changed is default value in case the number is not know by BF, from fallbacking to 768 (DX 9.0c), to 1280 (up to DX 11). (so using 65535 result in either 768, or 1280, based on if that change is live already) problem is that all of these implementations are broken and crash for some people, so there is no value that would work for everyone 😞 Thanks for elaborating. ❤️ Quote Link to comment Share on other sites More sharing options...
Kubik Posted November 16, 2021 Share Posted November 16, 2021 no problem 🙂 Quote Link to comment Share on other sites More sharing options...
Zyna Posted December 21, 2021 Share Posted December 21, 2021 @Kapo Has this issue been resolved, or does it still happen for you? Kapo likes this Quote Link to comment Share on other sites More sharing options...
Kapo Posted December 21, 2021 Author Share Posted December 21, 2021 5 hours ago, Zyna said: @Kapo Has this issue been resolved, or does it still happen for you? All fine, never happend again after the fix Kubik suggested. Thanks for asking! Quote Link to comment Share on other sites More sharing options...
Recommended Posts