2 Years since i checked up on BG:EE are the black lines STILL a problem?
Gloomfrost
Member Posts: 261
Downloaded the latest version from GOG 2.3.6.7.3 and was stunned to see these black lines again around the character sprite boxes.
I remember seeing this same problem right around the launch of SoD. Two years ago. Version 1.3 didn't have this problem.
I tried alternate renderer to no effect. Please tell me that with the passage of two years there is just something i missed some setting that are causing these black line boxes around every npc and pc.
I remember seeing this same problem right around the launch of SoD. Two years ago. Version 1.3 didn't have this problem.
I tried alternate renderer to no effect. Please tell me that with the passage of two years there is just something i missed some setting that are causing these black line boxes around every npc and pc.
2
Comments
Sorry, I made a mistake. Disregard below.
Open: Documents/Baldur's Gate - Enhanced Edition/Baldur.lua
SetPrivateProfileString('Graphics','Use Sprite Outlines','0')
[Line 48 in my current installation]
Should solve your problem.
oh i do remember posting about this and others had the same problems, i guess i need to look at my history or posts and get a link over here.
Yep just as i thought here it is from 2 years ago
https://forums.beamdog.com/discussion/comment/737642#Comment_737642
doesn't appear it was fixed
On an unrelated note, you actually LIKE the walking speeds of BG1?! You should post that in the "Unpopuar Opinions" thread.
Glad to hear this is a legit problem in 2.0 and up UI's. For some reason i saw it immediately in the first CandleKeep exterior map. Just thought in 2 years Beamdog would of fixed the issue with it.
As for the walking speed well that's why they invented the The Paws of the Cheetah
Seriously good to see you still active around here.
Now THATS a scary thought
I almost wish the issue was more consistent, just so it was more obvious what was wrong. I seeing on only a couple sprites, but others see it constantly, ugh.
Also, its always nice to know that I don't annoy everybody
Edit: No, reading the bug report more fully it looks like they've been working on that since 2016. The timing is just coincidental.
I'm on a live Steam version, so the latest version 2.5 whatever it is now. It automatically updates.
However I should mention that I see the lines mostly on the old Blue UI - I deleted SOD so I could play without the new black UI and the lines are just about everywhere there. They sometimes show up as boxes around character sprites, around the spell icons in the spell books, in bodies of water, and sometimes along spell effects too.
I recently reinstalled SOD and the black lines are fewer but still extant. One on the spell Invisibility's icon and the ones in the water which never go away. One also in High Hedge that cuts through the big crystal.
The alternate render seems to help, but creates a new problem that makes the game unplayable for me. If I go to the map (where it zooms out) the game sticks in outdoor areas. I have to ctrl+alt+del out and come back for it to unstick each time.
I gave up on alternate render after a chapter or two because I couldn't handle it anymore. However - and this is important - the lines and sprite boxes were still there, just not as frequently as before. So it wasn't a true cure.
What's crazy is that it's not always reproducible. Just tonight I was in the cave after escaping the crypts under Candlekeep. In the battles, every enemy had a black sprite box around it. It was horrible. I got through it, saved, re-loaded a previous save and went in again to get screenshots and guess what? No spriteboxes this time. NO reason for it.
So the lines just appear and disappear inconsistently.
I did get a screenshot of some of the spriteboxes or lines around these spiders. You have to enlarge the picture to see them, but they are around the spell graphics.
Anything is possible. But I never had this issue back in 1.3 and I didn't have any issues up until the Siege of Dragonspear patch, 2.0 I think. I played SOD when it came out with no issues and hadn't returned to the original game since that patch until now - and I'm having issues. I've been playing BG:EE on the same PC with the same hardware since 2014.
I will mention one thing. I DO alt+tab a lot to check the internet for things - could alt+tabbing be causing the issues? I will try to play my next session without doing it.
I've confirmed that alt+tab is not affecting it. It seems to happen truly randomly, mostly in underground areas for some reason. So far I've learned to live with it.
I will consider it. This isn't my thread so I won't ask anyone to move it, and usually if I post asking the mods for help they tell me to just post it in Redmine. Considering that the bugs and issues I've put in Redmine have sat there for years with no fix - I'm not inclined to believe in the system anymore.
I think it's related to the maths which selects a segment of an image to draw onto the screen, at various resolutions and zooms it maybe rounds slightly wrong and ends up selecting a bit of black border or nothingness which is filled in with black.
So this has been going on since 2016? I will be honest, it's about time it's fixed. It destroys my experience. Every single spell has this bug, can't play like this.
The lines discussed in this thread above are fixed by 2.5. The lines shown during casting are planned to be fixed for 2.6. The bug is not present with the Nearest Neighbor Scaling enabled.
This is a direct quote from the thread you posted:
So how can they be fixed by 2.5, if people in the same thread are still seeing this problem even after 2.5?
Also, Nearest Neighbor Scaling enabled doesn't mitigate the problem. I had the Nearest Neighbor Scaling enabled when I recorded the video above. Anyway, hope the 2.6 comes soon, because as of today the game is unplayable.
@ThacoBell thanks for your suggestion. Already tried that, no luck.
fun fact: I rolled back to the 1.3beta version on Steam and the problem is not present in the 1.3. Unfortunately, the 1.3 version has it's own problems, so it's unplayable either way.