Full Version: Black viewport windows after PC has been locked

Hi,

Just working through a tutorial with the demo version to see if MoI is right for me, and I have an issue whereby after the PC has been locked (Windows 10), the viewport windows in MoI appear completely black and I can't find a way to refresh them - the only solution is to close MoI and reopen it. I can save the document before I quit so I don't lose any work, but it is a bit of a pain in the ass and doesn't give me much confidence for the rest of the software.

Is there a fix for this or just something that has to be lived with?

Thanks,

Peter

---

Sounds like a graphics driver problem. If you want to dig into it, post a little info on the graphics card, the driver version and OS you are running it on…

---

Sure, I've posted system information below. In classic "IT Support" fashion I haven't tried restarting the PC to see if that's the problem. Am I to understand that this isn't a known problem?

Name NVIDIA GeForce RTX 2070
PNP Device ID PCI\VEN_10DE&DEV_1F02&SUBSYS_1F0210DE&REV_A1\4&FA0C5&0&0008
Adapter Type NVIDIA GeForce RTX 2070, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 2070
Adapter RAM (1,048,576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d1bd230cd08e7436\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d1bd230cd08e7436\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d1bd230cd08e7436\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d1bd230cd08e7436\nvldumdx.dll
Driver Version 31.0.15.2824
INF File oem158.inf (Section001 section)
Colour Planes Not Available
Colour Table Entries 4294967296
Resolution 2560 x 1440 x 59 hertz
Bits/Pixel 32
Memory Address 0xF6000000-0xF70FFFFF
Memory Address 0xE0000000-0xF20FFFFF
Memory Address 0xF0000000-0xF1FFFFFF
I/O Port 0x0000E000-0x0000EFFF
IRQ Channel IRQ 16
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_D1BD230CD08E7436\NVLDDMKM.SYS (31.0.15.2824, 55.39 MB (58,078,744 bytes), 24/01/2023 21:08)


OS Name Microsoft Windows 10 Home
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name PETER-PC
System Manufacturer Gigabyte Technology Co., Ltd.
System Model Z370 HD3
System Type x64-based PC
System SKU Default string
Processor Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 6 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F14b, 28/11/2019
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product Z370 HD3-CF
BaseBoard Version x.x
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume3
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.19041.2251"
Username peter-pc\Peter
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 20.6 GB
Total Virtual Memory 33.9 GB
Available Virtual Memory 19.7 GB
Page File Space 2.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

---

This is what it looks like when I unlock the PC by the way. Perhaps there is something strange about the fact that it seems to have full-screened itself? I normally work with it only maximised.

Image Attachments:
blackmoi.png 

---

Message 10972.5 was deleted

---

Every other open program is functional, it is only MoI that has any issues when unlocking.

---

Message 10972.7 was deleted

---

Hi Peter,

> [...] doesn't give me much confidence for the rest of the software.

> Is there a fix for this or just something that has to be lived with?

As a Mac user I don't have any relevant insight to offer into the problem you've run into, but as a long time user of MoI I strongly suspect that an answer will be found soon. This community of enthusiastic users continues to amaze me with the support they offer to other users, and Michael Gibson who is the author of MoI is beyond compare (in my experience) when it comes to supporting his users. In some software "beta" means beware but with MoI I begin using Michael's beta versions as soon as they become available because his attention to code quality in the first place and follow-up fixes in the second means I seldom see bugs last very long. I only mention the beta versions as an indication of code quality and attention to detail.

As to your issue, my hunch (along with Burr & Brian) is something to do with video drivers...

--Larry

---

You have a driver that was released 3 days ago.

I would start there. But first i would wait for Michaels response. It will be much more informed!

Maybe he has sundays off!

And to the follow up, currently the issue “is” not something people generally experience or expect.

---

Message 10972.10 was deleted

---

Hi Peter, yes as others have mentioned above it's likely to be a bug in the video driver.

If you unmaximize and resize the unmaximized window does it refresh then?

You might try rolling back your video driver to the previous one and see if that does any good.

Transitioning to and from sleep mode is a pretty complex area of the operating system and it is not that unusual for there to be driver bugs in this area.

Another thing you could try is to switch the graphics interface that MoI is using. To do that go to Options > General > "Edit .ini file" button and find GraphicsAPI=Auto and set it to GraphicsAPI=OpenGL and see if you get different driver behavior.

MoI defaults to using the Direct3D11 GPU interface which usually on Windows is the most stable but possibly not on your specific hardware/driver environment.

- Michael

---

Message 10972.12 was deleted

---

Hey Brian,
The “gforce experience” you linked to is a software for managing your driver environment and various things, mostly for gamers. Its not the driver

Also, its mostly recommended to get your driver downloads from Nvidia. I wouldn't download them from 3rd party websites

I built my son a gaming computer and used a 2080ti. It is a monster. All the effort went into matching it with the motherboard and ram and hard drive.

---

Message 10972.14 was deleted

---

Brian,
I’m sorry i didn't mean to sound like “.your post is irrelevant” and you should not post.

I had read you “haven't put much time in the area” and i was meaning to give you a bit of the filler for an “aha “ moment. You and i having a sidebar.

I always read your posts in there entirety and they are meaningful for me.

---

Hi Burr,

Thankyou for the "heads-up" on the difference of the basic video card driver(s), and the gaming environment driver(s). The posts were deleted to avoid further confusing of the forum topic.
Hopefully Peter will follow up with the details of a fix for the "blacked out viewports."
I am curious for the results.

- Brian

---