Georgio

Up until recently I was running DCS and Hornet on an iMac via Bootcamp. The Mac had a NVidia 6800 notebook GPU, this is about as bad as it can get specwise, but even so I quite happily played on low settings. Now I have a new rig with i7/1080Ti it's a different story with the eye candy...:D

Crazy that you can have a target same level right infront and yet the radar can't see it. Finding the only way is to use the AIM9 in uncaged mode.

Been doing some delving and it seems that HID devices could be causing the issues I'm seeing. Looks like one course of action is to unplug all game controllers and then delete/disable all HIDs in device manager to resolve the conflict. I'll give this a try tonight.

I know there are issues with the Warthog and the Hornet in particular but I wonder if someone has any idea about what could be happening with my Hornet problems. • So I'm using a warthog that works perfectly in all other modules. • I have Target but I'm not using it preferring to keybind the hotas ingame for the Hornet. So it's in the default A-10 mode effectively. • The keybinds are recognised and saved in the Hornet controls screen for both sim and game. The problem is that when I actually get ingame no keypresses are recognised either for the Warthog or even my keyboard. Literally the only things that work are the axis's so pitch/roll/throttle are fine but no keypresses are registered. I've tried deleting/reinstalling the hornet module, trying the warthog in different USB ports, repairing etc but nothing works. It's almost like as soon as I go into the Hornet module it disconnects the warthog and keyboard but retains the axis commands, bizarre and very frustrating. If anyone can offer some other ideas of what to I'd be most appreciative as I've had the Hornet since release but held off from flying it properly until my new rig was ready and now that it is the Hornet is borked....:music_whistling:

I wear glasses and have had no issues with the Rift. You have to be careful putting the headset on but once on it's fine. The experience of VR is a game-changer for sims without a doubt.

Makes you wonder if all the people having problems are due to RAM issues if your 32GB monster is fine?

Sounds like you need to let the devs know your system specs....:thumbup:

This is superb, just what I need but why is there a delay to October please?

Mossie would be most welcome. As one of the most versatile planes ever, the scope for missions would be fantastic.

Yep I'll never get the chance to fly a real A-10 but it does seems under-powered and too much like on rails, i.e. no inertia on turns.

Looks like a full 84GB download to 2.5 stable, is that right?

Long time DCS user though I did have my modules dormant. So saw all the fuss about 2.5 and decided to reinstall on my iMac as it's the only computer I have at home at the moment. Wasn't expecting a great deal given that an iMac is effectively a lap top with a 27" screen, so no real graphics card just a 680MX chip. Anyways, I must say that I'm very impressed with just how well DCS works on such a machine. I get smooth, fast tracking with my TrackIR, the graphics are far superior to what I remember but also the frame rates are pretty good considering. In short I'm having a blast with 2.5 Beta, so take your time and get the 2.5 release absolutely right...:thumbup: Hopefully when GPU prices normalise I'll be able to get the components together for a dedicated VR machine but until then I'll just carry on enjoying the fruits of your expertise.

The only good thing albeit years away is that if the big GPU companies are making big bucks from their cards presumably they're reinvesting into the next generation of GPU's to make them even better. Silver lining and all that.

Yup but then that takes you to the scenario already mentioned that to run A-10 in game mode is like having a Ferarri and sitting in it making 'burruum, burrrruuum' noises instead of actually driving it. :thumbup:

I think it's because if our friend is having problems downloading then the complexity of A-10 is going to fry his brain. ;)

I'm guessing that being slammed into the straps and the noise gives you a pretty good indication of how open they are. Personally I think they work just perfect but always have to have a quick look over the (virtual) shoulder to see how open they are. :pilotfly:

I went steam because of Cliffs of Dover otherwise I wouldn't have bothered. I really hate the way they try and sell you stuff you don't need all the time. Also I had a nightmare when I had to install steam three times in as many weeks on different computers due to hardware failure. I don't really see the so called advantage over a standalone download either

All this chat reminds me of the bombs from 'Free Running' i.e. "Ok bomb, now drop and go do your thing" Bomb " Sorry I can't do that" "what but you're a bomb" Bomb suddenly realises it's conciousness, thinks it's God and blows up. Classic.

Agreed, a masterpiece that reminds me of loading up DI's Tornado many years ago. :D

Quality and depth costs; It depends on wether you like to drive a Ford or a BMW, both do the same job but it's all in the style :thumbup:

Needs a HAL9000 screen to pop up with a 'I'm really sorry about this Dave but I'm afraid I'm going to have to stop your flight sim as it's causing my logic boards to....Mary had a little laaaaaaaambbbbb, it's fleece was white as....' ;)

Pilot error already... :music_whistling:

All you need to know about landings is to keep your speed to about 120-130 knots, so from the approach deploy speedbrakes, flaps etc to get the speed down. Then drop your gear and retract the speed brake to keep your speed at 130 - if it looks as though you're gaining speed, deploy speedbrakes again. Aim your velocity vector -O- , the mini plane symbol shown in the hud at the runway threshold , i.e. the end nearest you, at all times. This velocity vector basically tells you where the plane is headed, so if you keep it on the runway threshold AND keep your speed to 120-130 knots then you will end up at the runway. Then reduce power slightly and flare to get the wheels on the runway. Apply full speedbrake to slow then use the brakes sparingly to stop. Easy :)

We're talking about making things simple for fighter jocks to understand and retain information, so 'china hat' 'coolie hat' etc, etc, makes it obvious to even the most ham-brained which switch is which. Hell, I've had a FLCS/TQS & Cougar and it's only now that I'm learning what the switches are called. :)

Make sure you shut down all unnecessary background programs; I'm still using XP so use 'Kill it all' which you can select which programs to leave running and which to kill. The more horses you have for A10 the better she'll fly... :D