timc

Thanks gents. I’ll try that later. I haven’t got any mods but I’ll see what that does.

As per the title, I have just updated to the latest version today and the game will not load past the 55% mark. I've tried the repair function but this hasn't stopped the hanging.

Arrgghhh. Now I'm going to have to get the Mirage (and break my no beta purchases rule)! Nice skins by the way.

English cockpit version? I swear it must be in there somewhere but I cant find the information about the cockpit - is there an English version? I struggle to get my head around what button to push at the best of times and reading it in another language is beyond my meager capabilities. Thanks.

Ok, thanks. I was starting the mission with about 30% fuel so it makes sense that there's nothing in the other tanks.

I watched one of the start up videos and followed the quick start guide but I cant get the fuel panel indicators to change from red to green. These are the DEP. CENTRAL, DEP. DER and DEP ?? which are white until I start up the GPU. They then turn red and stay that way. What do I need to do so that these go green - as they do in the start up video? Thanks, TimC

Charles/Tango4, You (and the others who have suggested a graphics card issue) may be onto something there. I've installed Gigabyte's OC Guru (it's a Gigabyte card) and cranked up the fan speed for now. I also deleted the Saved Games folder just for luck. So far I've managed a 35 min flight without issues using the same test conditions as the freezing scenario and no problems. Before I would get 20 mins max. My graphics settings are all down low so I'll move them up and test again. The downside is that I feel like I'm sitting next to an Airbus with the engines running! I'll see if I can get a stable DCS set up like this then perhaps reduce the GPU clock speed in conjunction with reducing the fan speed. Fingers crossed and thanks for your help. Tim

I am another DCS user suffering from terminal freezes. I also have a 780Ti and after 20 minutes of flying the system freezes. Sometimes it is for 30 secs or so before the sim goes into stutter mode and often I need to restart to recover the PC. Watching task manager there is a massive spike in CPU usage during the freezing caused by the System process. I have used Process Explorer to watch what is going on and it seems that a kernel thread is going ballistic; the offending cuplrit is RtlSidHashLookup. I haven't been able to get to the bottom of what is causing this thread to be so active - does anyone have any suggestions? In terms of PC specifics, I am using the latest version of DCS on a 4960K running at 4.5Ghz via Asus' AI suite, 8MB Ram with the OS (Windows 8.1) and DCS on separate SSDs. Tim

Does anyone know how long it takes for the aircraft installers to update? I am in the middle of a complete reinstall and cant install any of the aircraft I have purchased.

Best post I've read in ages.

If you land hard enough, the main gear kicks forward, ie the wheels end up further towards the nose than usual. You can see this in external view - the gear looks like its pointing forward. Normally the CG is in front of the position that the main gear touches the ground. The CG doesn't move but the rear wheels are then ahead of it after this issue which causes the pitch up. I've tried to find a photo but no joy.

Sounds like you damaged your main landing gear. That'll cause the aircraft to sit back on its tail.

Playing Arma III and getting shot in the face. Time and time again. If the huey takes any longer I may be able to go more than 15 minutes without chewing on a 6.5mm round.....

Ok, thanks. That explains why I haven't seen hydraulic pressure dropping. What about fuel - there doesn't appear to be leakage from the tanks as indicated by a dropping tank needle (I did move the selector to the relevant tank). I'll make a note to press and hold the PNEU switch next time - thanks for the tip.

Had a flight with the guys on the Shrek server last night (thanks for accommodating me guys) and redefined the term "combat ineffective" but anyway, I was hit by a SAM which knocked out the CADC and punched a hole in my wing. I was flying around for a good 10 minutes with something leaking out of the damaged wing but there was no drop in fuel or hydraulic levels. Is this kind of damage modelled? Also, with CADC out my altimeter stopped working so I tried to switch it to pneumatic but it wont work. I've had this before but am sure I have also seen it working in earlier builds. Is this function not modelled or do I need to set something else to get it working? The manual simply refers to switching to pneu mode in the event of CADC failure

Happy to show you a few ropes. I'm in the UK and have TS. PM me if interested. Tim

Stunning!

Can anyone verify my finding that the remote indicator compass still reads out by 12 or so degrees? I figured it would be more accurate than the gyro compass but it made my relatively short cross country flight very 'interesting'!

Stonehouse - what is the ambient temperature at your starting airfield? It sounds like the auto function works in air but clearly something is awry on the ground. I've been starting with OATs of 15-20 and haven't managed to fry the engine yet. Shortly after takeoff I am throttling back for the climb and this keeps the temps fine. Your experience at 250 mph and a few thousand feet altitude is also different to mine: with the rads in auto my coolant and oil temps are low and I have to manually close them to get the dials in the green. Of course, forgetting to open them for a touch and go DID seize the engine and I'm sure the local farmers were pleased with my furrow! FWIW, I can't get my carb temps away from zero using the above parameters. I will try again later with a bit more RPM and Hg and see what happens.

Ditto the above. Can I have details please?

Gunny, Not sure if this is a good set up but the P-51 is a cinch compared to the A-10 on the x52. I use POV2 for trim (aileron and pitch) with the left and right movement also trimming the rudder when combined with pinky switch. Set the latter up as a modifier (button 6 I believe). POV1 is only used left and right for wheel braking - useful for taxiing. Main brakes (ie both) for me is button 3 or 4. Toggle switches for flaps and gear. In the 'assign axis' menu I have Rotary 1 as the prop RPM control but use it inverted - that way the movement direction is the same as the lever in sim. All this is set up in the Controls menu. There is no use of the profiler software here. That's it. You could chuck in a few more and I might add radiator controls at some point but it's pretty simple. I use trackIR but don't have a particular profile that I'd say is great for the Mustang. Good luck.

Here it is, not red flag as I posted but Hawgsmoke. http://www.scribd.com/doc/80796628/Hawgsmoke-Mils

There's a link or two here that might help although the first two are broken I think.

I'm a huge fan of CCIP and dive bombing but the challenge if getting the pipper on target took me a fair bit of practise to get sorted. If you've got a good visual cue of your target location on the ground it makes things so much easier. I use field colour, road junctions and anything else vaguely distinguishing to spot where the target is and roll in on that reference. Approach the target with an offset angle of 45 degrees (or 90, 60, or 42.5 for that matter!) and you'll have the target area in sight the whole time. The point that you roll in can be measured against another reference; tha canopy or another part of the airframe. Hopefully you'll find getting the pipper on target much easier. By all means use a waypoint as your roll in point but for some reason (probably ineptitude) I find setting one up appropriate to the height and dive angle to be too time consuming. With regards to DTOF, Paulkilli (sp ?) or someone put some red flag munitions profiles up a while ago with settings fo the BDU33. These have various parameters including dive angle, DTOF, min release etc. I'll see if I can find it.

Echo - excellent explanation; thanks. Frostie - thanks for clearing that up. I couldn't connect so figured I'd borked something in my attempt to get online. Will try again in due course.