Skip to content
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

Black screen when cursor on creeps or heroes #328

Closed
qjjy29 opened this issue Feb 4, 2020 · 35 comments
Closed

Black screen when cursor on creeps or heroes #328

qjjy29 opened this issue Feb 4, 2020 · 35 comments
Assignees

Comments

@qjjy29
Copy link

qjjy29 commented Feb 4, 2020

System information

Computer Information:
    Manufacturer:  Apple
    Model:  MacBookPro14,1
    Form Factor: Laptop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    CPU Family:  0x6
    CPU Model:  0x8e
    CPU Stepping:  0x9
    CPU Type:  0x0
    Speed:  2300 Mhz
    4 logical processors
    2 physical processors
    HyperThreading:  Supported
    FCMOV:  Unsupported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Unsupported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Unsupported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    MacOS 10.14.6 (64 bit)

Video Card:
    Driver:  Intel Iris Plus Graphics 640
    Driver Version:  1.2
    OpenGL Version: 2.1
    Desktop Color Depth: 32 bits per pixel
    Monitor Refresh Rate: 0 Hz
    VendorID:  0x8086
    DeviceID:  0x5926
    Revision:  0x6
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1440 x 900
    Desktop Resolution: 1440 x 900
    Primary Display Size: 11.22" x 7.05" (13.23" diag)
                                            28.5cm x 17.9cm (33.6cm diag)
    Primary VRAM: 0 MB

Memory:
    RAM:  16384 Mb

Miscellaneous:
    UI Language:  English
    Media Type:  DVD
    Total Hard Disk Space Available:  478144 Mb
    Largest Free Hard Disk Block:  96456 Mb
    VR Headset: None detected

  • System information from steam (Steam -> Help -> System Information) in a gist:
  • Have you checked for system updates?: [Yes/No]Yes
  • Are you using the latest stable video driver available for your system? [Yes/No]Yes
  • Have you verified the game files?: [Yes/No]Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist.
When I move the cursor onto the creeps or the heroes, black screen happens.

Steps for reproducing this issue:

  1. Start a normal game or a bot game
  2. go to top lane or bottom lane
  3. move the cursor onto a creep or a hero

1.mp4.zip

@silvanheller
Copy link

I have the same issue on my machine. Here's my System Information in a gist

@ghazalbigdeli
Copy link

I have the same issue! (MacOS using Vulkan)

@SimonHattoriWilson
Copy link

@kisak-valve Is there any updates on the fix? Unfortunately, this makes Dota unplayable for MacOS users so I would really appreciate an update. Thank you!

@silvanheller
Copy link

@SimonHattoriWilson I've been using OpenGL which is pretty stable (you can switch in the dota 2 settings)

@SimonHattoriWilson
Copy link

@silvanheller I've tried using OpenGL but found that the game becomes choppy and frame rate drops to 30-40 towards the last half of the match. On Vulkan I rarely see fps drops below 60.

@ghazalbigdeli
Copy link

@silvanheller I've tried using OpenGL but found that the game becomes choppy and frame rate drops to 30-40 towards the last half of the match. On Vulkan I rarely see fps drops below 60.

Same for me! :(

@heisen273
Copy link

Please fix this!! OS x 10.14.6 (18G103), using vulkan exact same issue!

@heisen273
Copy link

@danginsburg, by any chance are there any updates or possible ETA on this issue?
I'd appreciate any feedback, thanks for reading this.

@iLevye
Copy link

iLevye commented May 17, 2020

Having same issue but still better than opengl

@heisen273
Copy link

@iLevye unfortunately it's unplayable when your screen goes all black once you put your cursor over friendly/enemy unit.
I can't believe this issue is open for over 3 month without any significant attention from devs.

@qjjy29
Copy link
Author

qjjy29 commented May 19, 2020 via email

@heisen273
Copy link

@qjjy29 could you please confirm that black screen issue that you've described in original post is fixed by downgrading to High Sierra?

@qjjy29
Copy link
Author

qjjy29 commented May 24, 2020 via email

@iLevye
Copy link

iLevye commented May 25, 2020

I've tried everything and found a solution!

It is about Shadow Quality options in video settings. Make it High or Ultra to fix the issue!

@qjjy29
Copy link
Author

qjjy29 commented May 25, 2020 via email

@qjjy29
Copy link
Author

qjjy29 commented May 25, 2020 via email

@iLevye
Copy link

iLevye commented May 26, 2020

@qjjy29 I played a few games. I still have this issue but very rare. First time I move my cursor on a unit this issue has occur. But, it does only one time for a second.

Here is my system info:

Computer Information:
    Manufacturer:  Apple
    Model:  MacBookPro15,2
    Form Factor: Laptop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
    CPU Family:  0x6
    CPU Model:  0x8e
    CPU Stepping:  0xa
    CPU Type:  0x0
    Speed:  2800 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Unsupported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Unsupported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Unsupported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    MacOS 10.14.6 (64 bit)

Video Card:
    Driver:  Intel Iris Plus Graphics 655
    Driver Version:  1.2
    OpenGL Version: 2.1
    Desktop Color Depth: 32 bits per pixel
    Monitor Refresh Rate: 0 Hz
    VendorID:  0x8086
    DeviceID:  0x3ea5
    Revision:  0x1
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1440 x 900
    Desktop Resolution: 1440 x 900
    Primary Display Size: 11.22" x 7.05" (13.23" diag)
                                            28.5cm x 17.9cm (33.6cm diag)
    Primary VRAM: 0 MB

Memory:
    RAM:  16384 Mb

VR Hardware:
    VR Headset: None detected

Miscellaneous:
    UI Language:  English
    Media Type:  DVD
    Total Hard Disk Space Available:  476801 Mb
    Largest Free Hard Disk Block:  65434 Mb

@danginsburg
Copy link
Contributor

For those of you able to reproduce this, can you check some things for me - does this occur no matter what video settings you have the slider on? If not, which settings does it happen on?

@danginsburg
Copy link
Contributor

danginsburg commented May 26, 2020

One thing I'm specifically curious about is if you run with -dev -console on the Launch Options and bring up the console using "\" whether it rights itself if you do r_dota_bloom_compute_shader 0 which also corresponds to the "Compute Shaders" video option in the settings.

@rhysgirouard
Copy link

rhysgirouard commented May 27, 2020

Turning video quality to anything other than basic fixed the problem for me for a few seconds before the bug happening again. Changing just shadow quality to med also worked in the same way. I could not figure out how to use the console as suggested.

@heisen273
Copy link

@danginsburg It happens when you choose the 'fastest' video slider setting.
Setting r_dota_bloom_compute_shader 0 in console does not help anyhow.

I've also investigated and found out that specifically 'Shadow Quality' option causes this issue. If you set it to High – issue is not that observable( it still will turn black on some of the close-range units, not immediately, but throughout the game).

@heisen273
Copy link

@SimonHattoriWilson , @ghazalbigdeli – I've found a way to make openGL dota run smoothly!
Just use 640x resolution and you're back to stable 50-60fps!
Screen Shot 2020-05-31 at 10 33 02 AM
Screen Shot 2020-05-31 at 10 32 58 AM
Screen Shot 2020-05-31 at 10 32 49 AM

@iLevye
Copy link

iLevye commented Jun 7, 2020

For those of you able to reproduce this, can you check some things for me - does this occur no matter what video settings you have the slider on? If not, which settings does it happen on?

@danginsburg It's only related with Shadow Quality. Any other video setting doesn't change the anything. There is a tooltip on player units in game. I think problem is related with that. If creep units have same instance with player controlled units they may have tooltip too. But there is no information in that view and it scales it to all window dimensions some reason? Changing shadow quality to the "high" may change the renderer method of this tooltip? I imagine something like that as a web developer.

@Lethalmathematix
Copy link

Lethalmathematix commented Jun 24, 2020

This has been bugging me too, and I just found out there's an issue tracker here.

Steps to reproduce:

  1. Spectate any game.

  2. Change to Free Camera mode

  3. Hover over any lane creep or tower

 

Changing the Shadow Quality didn't change anything for me (while spectating).

Here's a screenshot of my video settings (macOS Mojave):

Screenshot 2020-06-24 at 10 44 51 AM

@bladerail
Copy link

Checking in to say that I have a Macbook Pro 2015 running OS 10.14.6 with Intel Iris 6100 also experiencing this problem.

I've tried setting shadows to Medium, High and Ultra as some others have mentioned above, but none of those fix the problem. With Shadows on, there are some areas where the screen no longer goes black, such as in the mid lane river. But it still happens in other areas, such as in between Tier 2 Tower and Tier 3 tower in mid-lane (Radiant side).

Hoping very hard for a fix.

@zhestkov
Copy link

zhestkov commented Aug 6, 2020

Are there any updates? @danginsburg
The problem is still exists and it makes Mac unplayable ;(

@heisen273
Copy link

@zhestkov it looks like vulkan support for OS x is finished, by looking at Daniels responses – I'm quite sure he's is not even capable of reproducing this issue, as he's not using mac os.
6 month for critical issue that makes the game unplayable and it's still open 😐 😑

@gale-slhoth
Copy link

gale-slhoth commented Aug 24, 2020

Hi tried the 'compute shaders' options too. Really trying to get Vulkan to work because Open GL gives about 60-80 FPS while the former gives 100-120.

Vulkan worked some time ago (about a year ago), but nowadays it doesn't work.

Screenshots

Vulkan Screen Prob Screen Shot 2020-08-09 at 12 38 55 AM Screen Shot 2020-08-09 at 12 38 54 AM Screen Shot 2020-08-24 at 8 12 47 PM

@heisen273
Copy link

Dear issue,

Happy upcoming 1year anniversary.

@simonfelding
Copy link

yeah

@Salekin-1169
Copy link

IDK if this the proper place to post, I've started facing this issue on Ubuntu 20.04 (intel hd graphics 620)
while cpu usage rises upto 60%
Opengl doesn't have the issue.

@ekeng-clgx
Copy link

ekeng-clgx commented Nov 13, 2021

Settings for macbook air 2015. Super slow computer. No black screen on mouse hover and runs great
VIDEO:
texture quality: MED
effect quality: MED
shadow quality: MED
Game Screen Render Quality: 75%
Max frames per second allowed: 90
[Default everything else]

@salo359
Copy link

salo359 commented Jun 28, 2022

Macbook Pro 13' 2017
MacOS Mojave 10.14.6 (18G103)
Same issue, also there is completely no light on map, all map looks like it's under fog of war.

This happens only on Vulkan API

@kisak-valve
Copy link
Member

Closing per ValveSoftware/Dota-2#2123 (comment).

@itsfinnguys123
Copy link

image
how about this guys pls help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests