Thanks so much for the clarification ❤

Have a wonderful day!

@l909

Hey, sorry for tagging you directly. Just curious what "feedback" means in this case?

I was more or less curious about what might happen with controller support for the game. I tried to be as verbose as possible in my initial post to give as much information as possible.

I know there is no explanation owed lol but I suppose I'm just asking for clarification about what "feedback" means in this case considering controller support already 100% works on the Steam version with more or less a very tiny amount of development/QA... there's genuinely no roadblock stopping this from happening, rarely is it ever just a "click of a button" but it kind of is this time lol.

Sorry again for tagging you, but I'll admit I'm a little disappointed it just got labeled feedback. I think maybe the post got misinterpreted as a general suggestion, when really I was pointing out that the controller UI already exists and works fully under the Steam Version...

So it's less "please consider adding controller support" and more "the feature is already built, it just needs a way to be switched on for the Steam Build (PLATFORM_WINDOWS)"

Not trying to be a pain, just really hopeful this will make it one day.

Thanks for your time!

I might not really be able to do much, but it'd be good for the devs to see. I'd upload it

Awesome! I'm glad you got it figured out.

Just double check in there for any new "Crash_" logs. If you don't see any, enable the logging thing from the launcher, or with the -dologs launch argument then just wait for it to happen again lol

Instead of pasting it that way, do this instead:

Scroll up in the thread until you see

"Public attatchments/Private attatchments" with buttons for uploading files.
Upload the file(s) to one of those

Do you usually only see performance reduction when you scope into a forested area? Or even while using the eye focus zoom in the same scenario?

I get a huge performance dip when I do this, and I've figured it's caused by the anti-aliasing on the trees.

No matter what setting I have it on, I get massive FPS loss zooming into a forest, whether through a scope or the eye focus zoom.

It only happens when zooming in, never looking normally. Only fix is turning anti-aliasing off completely.

I guess AA is just a huge hit with that many trees. Still odd it only happens on zoom, It's almost like they're loading the highest LOD possible even if they are still super far in the distance.

Are you running -dologs as a launch arg? You can also do this by opening the Vanilla launcher, going to parameters then checking the "Logging" box under the "Advanced" section.
You shouldn't need this, but if it's not generating a log upon crashing you might need -dologs or the checkbox
(They do the same thing, just 2 different ways of enabling)

Also - check here - It's possible you might have missed it....if the crash reporter dialog never opened up after you kill it from task manager

1. Press Win + R

2. A "Run" window will pop up

3. Type %localappdata% and hit enter

4. A file browser window will open

5. Open the folder named "DayZ" or "DayZ Exp" depending on whether you are expierencing issues on Experimental or Release

6. Attach any files named "crash_2026datedatetimetime.log" <-- The date/time will be in the file name so you can be sure you are grabbing the latest one(s)
   
   ^^^ Just incase I would also attatch your latest DayZ_x64datedatetimetime.RPT
   Make sure to use -dologs/logging checkbox. this will log everything going on in the game right up until you close it.