Page MenuHomeFeedback Tracker

Inventory dissplay on Hi resolution monitor setups
Closed, ResolvedPublic


I currently have 3 x 24" monitors (BenQ XL2430T's) running at a combined resolution of 5760 x 1080 on an Nvidia GTX 1080Ti (Desctop and game runs across all three monitors as though it was one large display, This is setup using Nvidia control panel - "set up multiple displays - surround display{F582232}" option

But when accessing the inventory system in DayZ it becomes all distorted (See attached screen shot) this was not a problem in 0.62 and the early version of 0.63 I could drop the resolution to play across just one monitor (Which would eliminate the problem), but in the recent patches (Probably just before BETA, it is no longer possible to select a preferred screen resolution in game (It defaults to native resolution either in full screen mode or windowed mode. I have also been told from people running high resolution wide screen monitors (Not just muti-monitor setups) that they are getting the same problem.


Operating System
Windows 10 x64
Operating System Version
Windows 10 Pro, 64 bit
Steps To Reproduce

Access inventory system on any wide high resolution monitor setup (The exact resolution that this startts to be a problem is unknown as I have been unable to test)
but does occure at 5760 x 1080 and I have been told by others it occures at lower wide screen resolutions.

Additional Information

3 x BenQ XL2430T monitors connected via Display port cables running at 144hz to a NVIDIA GTX 1080Ti
Configured to use surround dissplay using Nvidia Control Panel at a resolution of 5760 x 1080{F582240}

Event Timeline

Is there any way to drop the game resolution in Config. files etc. (That work) as a temporary fix as the inventory in its current state on high res. monitors is a game breaker.

Since 1.01 the inventory system now appears fixed, although some items are still invisible (Just greyed out with quantity number showing). I will submit more information (And screenshot) at a later date when I get time.

Check in 1.02 :)

This ticket could now be closed as the problem has been solved (A few patches back)

Geez closed this task as Resolved.Dec 18 2020, 1:16 PM
Geez claimed this task.