lemoen

The lights are borked for all planes in 2.5 at the moment, sadly. It has been reported though and I'm sure a fix is incoming at some point.

An observation: The GBUs can fly a bit further because of their fins -> more drag but also some lift. Maybe as a first approximation that cancels out drag.

You can move your default head position around with rshift-rctrl-numpad 2,8,4,6 then save the rctrl num0. You will find, either way, that there is no way to sit back in the cockpit AND see the entire hud. Choose one or the other.

People keep saying this. If you want bombs RIGHT THERE in the M2000 the CCRP with Mk82 is the only way to do it. You can hit tanks every time if you fly properly.

Can I bump this, bombs still release on trigger.

From Wikipedia: The radar horizon for the radar at a 1-mile (1.6 km) altitude will be 102-mile (164 km) and the one at 75 feet (23 m) will be 12-mile (19 km). Daniel, I think you need to sit down and think a little bit about the problem before posting all these threads. Most of them have pretty simple answers.

This isn't a headset, just a display, according to the article. For those those that think that this will require multiple 1080Tis, think again. With Foveated rendering only the part of the display where you are looking will be rendered at full resolution, which for this display is around 3x that of the rift / vive. The rest of the display can be rendered at a much lower resolution because you don't need to see as fine details there, and you can't. Researchers reckon about 2x-3x increase in performance using foveated renderring, so it may not be as bad as one would think.

Make sure your throttle axis only has one device assigned to it. It is possible your joystick or rudder pedals are also assigned to throttle, causing a conflict.

Yeah it's screwed. Some threads about it over at the Polychop section. Sent from my iPhone using Tapatalk

In our group of 10+ players, half of us have this problem. It could well be many 1000s of players being affected.

Depth of field only works for external views.

Is it 5 entirely new missions? The first one seems the same (Find some missing ship between 4 nav points). Haven't flown it yet. Just curious.

Did you clear out your fxo and metashader folders, in Saved Games?

You've burnt out your laser. Switch it off between shots. It doesn't have an infinite lifespan.

Yeah, don't fly blindly into the Blue (enemy) zones. Look at your ABRIS to know when you're about to go fence in. Then stop and do a recce. Ask your wingman to do short then longer recon flights, he'll send targets via the datalink. Then start looking there for targets. Almost anything can and will kill you, especially watch out for ZSU-23-2, manpads and the tanks with their sniper missiles. When you get the 'Under Attack' warning its time to move, quickly. When you think everything is nice now, stop and look around. You're about to die. Keep looking for missiles coming your way, the KA50 doesn't have a missile launch warning or RWR, just the Laser Warning System.

You can start telling the software to run on a specific core but then you interfere with the OS scheduler and it will quickly become a whack-a-mole situation. If your application only has 1 thread, the OS can't make it run any faster on multiple cores than it would have run on a single core. The thread will be interrupted and resumed as the OS sees fit and it may end up on a different core when it resumes. This is normal. In general, interfering with this makes the system as a whole perform worse but it may or may not have a positive effect on DCS under specific circumstances. I think core 0 is used for Windows kernel stuff so letting the OS move DCS away from that one when it needs to probably results in better performance. You can test this by forcing DCS onto a single core with the affinity trick. You'll see it runs like absolute garbage because the audio thread interrupts the main thread a lot.

Georgian oil war so far seems to work perfectly. I'm 9 or so missions in. Great fun. Deployment was great in 1.5, will do that one next.

I used some rockets to get a bunch then I carefully gunned the rest of them. Wingman did a few too.

uhm, this only applies if you keep your stick in place. I'm guessing most people will use the center-trimmer option so that once you've trimmed, you let the stick go back to the center and you're back to where you started, curve wise. Your guide is fine for FFB sticks or ones like the VKB (with brake) which will stay put where you leave them.

The OS handles this. The programmer decides how many threads to spawn and what to do in them, the OS determines where to run them, whether on separate cores or not AND which cores at any given time. There's a scheduler in the OS that allows threads to run and it can interrupt them when it needs those cores to do other things (update the clock, redraw the screen, play an email alert etc). You can set an app's priority (task manager, process lasso etc), i.e. higher priority -> interrupt other stuff before this one or CPU affinity -> try your best to only use THESE CPUs (cores in our case but the OS see them as CPUs nonetheless)

The Mirage (and Viggen and Spitfire) also has different stick lengths for pitch and for roll, long stick in the pitch direction, short in the roll.

You need to go and look for the defenders, they're not necessarily at the FARP pads.

Were you close enough? The A10C can't lase further than about 10nm I think. Secondly, where the F5 and A10C on the same laser code? F5's must be set on the ground on the kneeboard before engine startup.

OK well if you feel confident about that I'll just leave it there. It makes little difference to my performance or anyone else's performance if you believe the loads will be distributed or not.

After all that here's the simple summary. Is it multi-core? Yes, it uses more than one. Does more than 2 cores gives better loading performance? Yes Does more than 2 cores give better framerates? No.