-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate why Steel_Blue had broken F1 view before BAR engine #3677
Comments
Looks like something else along the line of #3620 and #3669 It's puzzling to see that so many cases popped up since recently. The bugs were there forever, but only started to pop up after some ZK or engine change. Frankly I have no idea what change might have caused that. Anyway SteelBlue will need to follow a tedious path of finding the offending widget: http://zero-k.info/Forum/Thread/28600 |
my testimony: At the start of the game I see only red(when heightmap is active). After some condition is met, the colors change to what they should be. The condition is the ground changing height, or being affected. for example, rouge misiles or merlin misiles deform ground, so when their attacks impact I get heightmap over the explosion area. a mex explosion also does that. Larget buildings, like factories/singus, update underneath their footprint, and smaller buildings, like LLt/picket do not. These rules follow line of sight, so I need to see the modified terrain before I get heightmap. I also have a video Placeholder seems to adjust terrain too. I certainly didn't notice it before, but there's a sliver of color on the North edge of the map. thinking it's an engine bug, Ihog has guided me to do engine launches in a strange way. engine 104.0.1-1318-g8cf4dea works and |
I did not realise that the engine updates happened already. Still have issue https://streamable.com/s1lj2 ZeroK-RTS/CrashReports#23412 this is the infodump of the session I played with the video,just in case. |
Bar engine does not have broken F1 view. recommend close. |
Check you have no PBO disabled, something like UsePBO=0 in your infolog/springsettings. |
N2S. Two likely suspects: beyond-all-reason/spring@6ef7975 |
UsePBO = 0 in steamapps\common\Zero-K\_springsettings.cfg |
No idea too, but you can see the actually used value in infolog.txt. 99% sure it's going to be |
[t=00:00:02.310272][f=-000001] SetSettings Value, UsePBO, 1 Screenshot from my end showing my view is right. https://cdn.discordapp.com/attachments/432874986064052235/941698428793151488/unknown.png |
I think compat mode sets pbo to 0. Alternately you could disable springsettings changes under the developer tab http://zero-k.info/mediawiki/Zero-K:Developing#Modifying_the_game |
https://i.imgur.com/oeuUcbi.jpg
The text was updated successfully, but these errors were encountered: