Zoddom

cruising at 42000 ft. GS server.

omg youre a genius, it actually works. I noticed the login window popping up first after the Bluescreen but didnt think much of it. Guess there was an issue with the autologin, as this was the only setting in the lua.

Nevermind I was looking in documents all the time... Here is my log file and the .old file , thanks for the help guys. dcs.log dcs.log.old

I dont have a DCS folder in saved games. I have the standalone version, if thats different from Steam.

Yes, but thats not my problem. My problem is that DCS just doesnt launch, it just gives me a black screen, but no BSOD. So I guess some files mustve gotten corrupt after last BSOD, but repairing doesnt help.

I tested my RAM over night and it found a few errors. But I understand thats normal with low timings on the RAM? Anyways, my main problem is DCS not launching anymore, and repairing didnt fix that.

Well Ive only ever really had it in Tarkov I believe. And as I said, my mainboard and ram are only about a year old and I only run XMP Profile in Bios, no other overclocking. Just checked my pagefile and it was just 3,5Gb, upped it to 12.

Yeah I know this error, I've mostly had it with Escape from Tarkov before, but I havent had it in a while. So I doubt its something on my hardware end, my RAM is 2 years old and I only use XMP and havent changed anything other than Infinity clock in Bios.

Thanks, I'll try. But what exactly does this and why do you think its Windows? update: sfc /scannow told me there were broken files that couldnt be repaired. Doesnt really help me, I attached the excerpt from the log though, if you wanna have a lookCBS_short.log. As for DISM, what exactly do I need to do here? I dont know how this works.

My game crashed with a BSOD (something like sys memory management error). I was flying over the Normandy 1944 Paris area (I dont own 2.0 yet). I already tried cleanup and repair, system restarts and single-/multithreading. All I get is a black screen. Any ideas? :(

What Ive always been wondering: is there any advantage to doing it manually? Or is automatic just fine?

I just leave it on all the time. With it off you have to control prop pitch manually I believe, which is too much hassle for me to even learn.

Im wondering the same, Im missing 40GB of disk space to download the update. Will it even be using all that space one its installed?! I only own 250GB ssds and I really dont want to put it back on my HDD windows raid, but if I do, can I just copypaste the folder over without worrying about fucking up my installation?

You can simply fix this in the mission editor, as I wrote in my original comment. But yes, would be nice if the whole Mirage campaign could get an overhaul, as the many updates in the last year have influenced some other parts of it aswell.

How does this work now? I cant seem to get the VTB to switch ranges by just driving the TDC into the top or bottom anymore. EDIT: okay I think I found the problem: if you lowered the Y saturation for the TDC axes, apparently the "momentum" of the TDC isnt enough to be recognized as touching the top/bottom "hard" enough to switch ranges. Is that correct? Anyways the TDC does feel far more precise now even with 100% axis saturation, did anything change there?