lemoen

Yeah but that is slow. People only want to know, via the changelog on patch days, what, if anything, has changed in each module. This is not too much to ask, the version control software they use has this information in it. They can literally dump all the commit logs since last patch day, make it neat and present it as an update log. It'll take all of 30 mins every 2 weeks, if that. If this information is not in the VCS then they are doing things very very wrong.

I think the last patch may have introduced some VR optimisations, I swear it is running a bit better, could be my imagination though #nodata

Probably fine having no change logs because the manual is kept up to date right?

Thats normal. VR takes a lot of CPU cycles to do all the calcs so your prob limited by CPU. A steady 45 is all you’re gonna get on average until DCS is more optimized. Sent from my iPhone using Tapatalk

It has the block and the flipping in skyracers video. Probably correct.

Looked right to me. In very thin air you'd expect it to lose speed at around 20knots per second (9.8ms^2, neglecting air resistance).

Yeah in the A10C its all on the HOTAS if you have enough buttons. But the point here isn't where the buttons are located, its just that you need to know 10+ keys to do the stuff (TMS U/D/L/R, DMS U/D/L/R, NWS for laser, etc.) i.e. the cockpit workload is higher compared to FC3. A lot higher in most cases. Well worth the effort though.

Decrease the gamma in the settings menu.

The truth is, the clickable cockpits have a lot more stuff going on. For instance, in the A10A/Su25T you don't need to worry about things like arming your bombs, aligning your INS, setting your countermeasure programs, enabling countermeasures, entering target coordinates, cooling down your maverick seekers, choosing which hardpoints are enabled etc. So while you don't have to remember button presses as much for some things, in a full fidelity module you have the usual button presses to remember (slewing your target pod, shkval, chaff/flare, fire button, pickle button etc) you also have a lot of other things to do in order to make the plane work. The FC3 planes are super simplified in terms of how much work you have to do and how much setup is needed to deploy ordinance. For instance: in the A10C in order to shoot a maverick: Prepare Mavericks (needs to be enabled at least 3 minutes before use so they can spin up gyros, cool seeker or whatever) Select HUD as sensor of interest (SOI) Choose CCRP mode Select Maverick as weapon Select a MFD as SOI Go to MAV page on MFD Slew maverick onto target Master Arm to ON. Fire So while this is not very complicated compared to the A10A you can see there's a few more steps involved compared to the A10A where you press 7 for A2G, Press D a few times to select maverick, Slew onto target and Fire. For releasing dumb bombs you need to arm them, select delivery mode etc. For laser guided you need to arm the fuse, select delivery mode, select auto/manual laser mode, designate target on TGP, release bomb, enable laser (if manual) etc. The TGP also needs to warm up and you need to select AA/AG mode, select contrast mode etc. The same is true for most full fidelity aircraft. You do the same things in the end but there's more to be done before you can complete your mission.

It takes a while to get used to all the controls. Pausing and looking for the controls is normal, we all do this at first. The full fidelity modules like Harrier/A10/Hornet has a LOT more stuff going on than the FC3 planes. It is worth it though. There's a lot more things to do and learn in these modules. The harrier is not complete yet, its systems (IRL) are not quite as slick as the Hornet or A10 so it's a bit more confusing to use than those planes. Can't say much about the F-14 besides piloting should be relatively simple and RIO will be more involved. Choosing a full fidelity module depends on what you'd like to do in DCS so I can't tell you which is recommended, I'd say Hornet, if it was complete, because it will be able to perform at most tasks available in DCS and will provide lots of things to learn. However, it is not yet complete so limited in a lot of ways.

The reason most games don't use multiple cores is because some things just cannot be calculated in parallel. So parts of DCS could be done in parallel (AI routefinding maybe, general AI decision making) but other things probably cannot (flight model calculations). Either way, you can not get DCS to run 400% faster on 4 cores even if you had a magic wand that could magically parallelize all the code that could be run in parallel. See https://en.wikipedia.org/wiki/Amdahl%27s_law Basically, for most games, the speedup is not enough to warrant the extra complexity of writing and maintaining parallel code. DCS I think can use it in places but maybe the same applies here (not enough speedup for the effort).

1. Can't remember now if it has training missions. I think there's a few. 2. Very easy to fly and learn, hard to master. 3. Its more modern, faster and can carry a LOT of bombs and rockets as well as 2x Aim9 and has twin 20mm cannons in the nose. The F5 is a great great module. Only downside is that it doesn't come with a campaign but plenty of MP servers to go fly on.

This won't really make the overall framerate better. It just stops it from getting worse. The game AI, path finding, rendering etc is all still done on one core only (and sound on another).

You're probably: running enough PD, playing single player, using MSAA. Try again on a heavy MP server and you'll see what I mean.

Strange, my experience was the other way around. Instructor did the takeoff, and let me fly the rest of the flight (this is my first hour mind you). He said I was excellent at straight and level and as well as looking outside instead of at gauges. Then he let me land the plane (at an international airport), on my first flight. Plane was a 60s Piper Cherokee.

With a monitor you need to calculate the scene from a single viewpoint. With VR you need to calculate the scene from two viewpoints. This costs a lot of extra cpu cycles and basically causes DCS to become CPU bound. You'll find that your GPU usage drops in VR while your CPU is maxed out on 2 cores.

The big issue with a laptop and VR is that the CPU needs to be really really really fast for VR. In my PC, i5-7600k overclocked, 32gb of ram and a Nvidia 1070, the GPU only gets to maybe 60% usage for 45 FPS and in MP it is utilised even less for 22-45 FPS.

Hopefully we'll have the Vulcan renderer by then, then the impact shouldn't be that wild.

Western aircraft won't be operated from a runway with loose stuff on the surface. Filling the holes is easy but the whole thing needs to be sealed again and then cleaned. See how they walk down highways looking for loose objects when doing road exercises.

4.8 is good enough. Going to 5Ghz will give you 5% extra speed, possibly, which means it'll increase from 45 to 47 fps i.e. negligible difference.

A10C if you want the current ultimate ground pounder with the wizzbang stuff. Lots to learn. recommended. M2000 if you want a fast yet with limited A2G and Fox1 A2A. Recommended. It has an english cockpit option now but the french isn't hard to learn. A-> off, M -> on and that's kinda all you need to know. The rest you can figure out. Also, there's a lot of material on it. Harrier -> This one is not yet complete and feels very clunky to use. I'd wait. Hornet -> Would be a great module in a while once more of its systems are implemented and most bugs fixed. I'd wait on this one too.

+1 one the jerky axis slewing. To me it seems like the vertical axis resets whenever some horizontal axis is added in, or maybe something related/similar.

In multiplayer, if a player joins after you bombed the runway, they do not have that damaged runway on their end. There is also no way to repair a runway, besides restarting the server.

They mentioned about 2 or 3 weeks ago that the preorder WarBRDs will ship this (or last week) and when they're done the throttles will start shipping. So that means throttles should start shipping in the next week or so. I'm also waiting, for a full T-50 set and mounts.

Some people like turning on VSync to stop screen tearing. In DCS this is a very reasonable thing to enable, absolutely stable 60fps is better than variable 75-110fps IMO.