Pocket Kings

I noticed you "only" have 16 GB of RAM. On what map took these crashes place? I can imagine the Hornet + Syria being too much for your gaming rig, which is still a fine machine except for the low memory.

That's the reason I clone my Windoze install before applying ANY updates, be it DCS or Windows Upbreaks. If it doesn't work for some reason and I don't have the time to investigate or I don't care to do the work of those fine programmers at Microsoup, I simply rollback to the last working state. Without these features I don't dare to work with any "product" that has a track record of being notoriously unstable.

Guys, I don't want to sound rude, but being a programmer myself I can tell you: In-House, Alpha, Beta, Testing, Stable These are the stages we use. Nick in an interview with Growling Sidewinder a few months back said that ED changes their release strategy towards more frequent but smaller steps. 2.7 beta being the exception of course. Then two weeks of testing, then watch the community bug reports closely, then fix and move on to the next stage. That's exactly how I work alone / with fellow programmers in a team. Just because beta has been stable for you in the past, doesn't mean it will be in the future, especially with the paradigm shift. Or to phrase it differently: Beta became more of an Alpha 2. Believe me, apart from the annoyance, the benefits for the development efficiency are huge with that kind of approach. With new updates, expect more frequent crashes and glitches than you're used to, but you can for sure expect a better bug fix management at ED.

Both, however the anti-aliasing issue is more of a problem while making screenshots, not so much in cockpit view. Yesterday I accidentally used fog. That prevented me from observing the shadow flickering in the valleys.

Damn I re-flew in the Caucasus mountains, deep in the valley and at 11 KM and I couldn't reproduce it. There were even low hanging clouds in the valley. But as I said, I've seen it too as few days ago. It's especially visible near sharp edges like rivers or at the base of steep mountains.

Things won't return to "normal", sorry to break the party. Remember Fukushima? -> No normal since then in some hardware areas, prices didn't return to prior levels. Or remember the tsunami? -> Same thing. My suggestion: Max out RAM, it helps a lot. I've been assigning 16 GB to my gaming VM, wasn't enough. Using 24 right now, works for Nevada and Caucasus, maybe I need to assign even more. Speed wise, stick to 1866, you won't notice the 2% gain while loading the map, not worth the price difference for a whole new kit. Then, overclock that CPU to the max stable and buy a beefier cooler which is compatible with newer sockets (multi bracket) ... and your current of course.

Is surround sound that important? It's not a shooter where perception of enemy activity is vital to your movement. I'm flying with one of those cheap bluetooth speakers, sometimes with a headset. Can't tell the difference honestly.

NEVER do this kind of approach again. Next time you wanna play an old game that whines about unknown DX version and the likes, install a Win 7 into VirtualBox or VMWare Player. I'd stay far away from any downgrade scenarios or tinkering for your "main install".

Some 1080ti's support SLI, that's an alternative to prolong the lifetime of the system and it doesn't cost what normal people pay for their first car.

Which was obvious that it had to be AHCI and/or UEFI partition, but you already found out about the solution. Sorry I couldn't reply earlier, I'm new to the forum and couldn't reply due to the 24h limit.

Good evening, I suggest you follow the "official updates" thread. Cheers

Weclome to DCS, I'm new myself here but neither new on earth nor to flight sims. I hope you'll get hooked, I'm pretty certain old timers appreciate the value DCS delivers, yet it has a long way to go for 2.7 stable. But we're here to help and enjoy the ride. Anyway, what gear do you run (flight controls, computer specs)?

For the sake of a complete checkup, could you please post your /etc/pve/nodes/xyz/qemu-server/123.conf where xyz = hostname of the node and 123 = QM ID? I'm working with VMs on proxmox clusters all day, so maybe I can be of help. Win 10 machines are the kind of things that lighten up my day... NOT.

These two are good examples: I know, they are most likely shot at different heights. But notice in the first picture the reflected clouds look like minecraft blocks and in reality they reflect well more defined, waves or not. Because with increasing height, waves don't matter as much. The amount of light rays that reflect with the right trajectory to hit your eyes lessen. Thus the light intensity to the eye decreases, not the crispyness. I hope you understand me, English isn't my first language. If you look at images from the space station, notice regardless of the severity of wind speeds or nearby storms, sun reflections on the water never look bulky like minecraft? The same is true for 33000 ft, or 60000 ft, or 3000 ft. This one is a great example: It doesn't look out of touch with the sky. Those screenshots above the Black Sea do, imho. I'm not blaming anyone at ED. Being a programmer myself I recognize that sometimes results differ severely from intentions. And I'm not even in the graphical department where we have two major chip architectures and a plethora of chip generations. It just doesn't look right.

I didn't save the track but I still have the mission and can re-fly it. Takes just 25 minutes. Will do it this weekend. Screenshots enough or do you think I need to record?

I've notice the same. Clouds ten minutes prior to the screenshot looked too bright and milky. Then, THIS (I suppose this screenshot qualifies for "cinematic"): Gamma ~ 1.5 at the time of the shot. Been testing a lot of values. I also noticed that gamma is key to good screenshots. The rendering engine seems capable enough though to produce the desired results with the right settings.

Maybe that's a useful feature, but as of now (no dynamic weather) I beg to differ. Suppose you build the coolest mission possible, long range approach to target area, destroy ship X, shoot down interceptor Y. Now half an hour into the mission, unguided bombs onto target Z. There's simply zero visibility sometimes, you cannot lock anything. That would be super frustrating for yourself and your buddies. And again, circling over the target area doesn't help, the thick low hanging clouds stay where they are. Might as well drop the bombs into the dark.

Anyone can call me an armchair pilot, quarterback, president, whatever, I don't mind free speech and I think discourse is healthy in the long run. However, I remain the right to call anybody who says the first screenshot vs the latter looks "perfect" to have issues, at least with eye sight. We all have at least been passengers on airplanes over waters. I've traveled quite a lot but I have never seen such an unified "soup" in my life under no weather or light circumstances. For sure, both do not look perfect and far from the real thing. But try to ask normal people, e.g. non armchair pilots, for their opinion. I don't believe they would call the first screenshot "bang on reality".

In addition, on maps like Nevada and Syria, basically every sandy map, ground dust can travel extreme distances and heights. I suspect a real F15 pilot wouldn't fly ultra low for extended periods of time since sand isn't the kind of "ingredient" you're willingly adding to the jet engine. Having said that, a windy environment should also stir up some ground dust into the air.

I don't run anti-virus. I run everything as a VM within proxmox with a custom made firewall in front of it. The Win 10 VM can only route to the ED servers for updates and stuff. Not even usual browsing is possible within this Windows VM. Snapshots of the Windows VM every 10 minutes, rollback if need be. BTW Flappie, I'm a new forum member and didn't realize that certain areas are forbidden for me within the first 24h. In your other thread, the crash due to the audio device in your VM, could you please post your /etc/pve/nodes/xyz/qemu-server/123.conf being 123 the ID of your Win 10 VM?

I had the same issue with the Su25-T while approaching Sochi, but not as severe as your video shows it. Within F1 (cockpit view) I could glance down at the instrument panel and everything rendered fine. Once I centered my view, or left or right, everything went black. Outside views and flyby view were not affected. That was an interesting experience, landing instruments only as a DCS novice.

Do you realize that the weather is static once the mission launches? So the random generator would just kick in before starting the server. While the map runs, the weather is fixed. I suggest you try out every cloud setting one by one. And while you're flying Caucasus, watch out for the shadow glitches or flashes on the ground. And when you see them, press the screenshot button, please.

Spot on. I was approaching Kutaisi with my Wingman and noticed those glitches while heading south over the mountains into the valley by the river while leaving the lowest layer of clouds. Tried any shadow setting, still happens. But yeah, I already felt that "flat" seems to propel these glitches better (or worse) than default. However I tinkered with the graphics settings a lot since 2.7 because I only run an GTX 1060 OCed version. Finding a reasonable priced card is impossible right now. I already thought that the coast line of the Black Sea looked weired compared to 2.5.x.

Confirmed, I noticed those flashes while replaying a track. However they occur when I'm below the lowest "deck" of clouds, mainly in the under 3000 ft range. I only noticed them near the edges of rivers. I initially thought my graphics card had issues since it hit 60°C. I'll keep my eyes open.