Raven_Morpheus

Just going to add my $0.02 to the thanks to ED for EDGE. I just finished installing it and went to try the Ka-50 mission Altitude which used to run like a slideshow from the start, due to the number of building nearby at ground level, and it runs great now, solid 30fps minimum. I also tried Stray Eagle in the Huey and that's even better, I'm getting >50fps when looking out the cockpit (I saw 70-100 on the fps counter!) and looking behind me at the crew I get decent FPS as well - they and the other Hueys on the FARP used to tank the framerate, bringing it down to the 20's. I will have to start the Huey campaign first mission to see what approaching the airport and farp full of Hueys is like because that gave me sub-20 fps as well. And I think I set my settings higher than I have them set in DCS 1.2. Need to test some more but I think I didn't need to go buy a new PC with an i5 CPU after all (still using my ATI Phenom II x4 955 @4ghz)...

Hey all I'm using Open Track to track my head movements, and I've noted that in the Huey, (the only aircraft I've been using recently, it's probably the same across all aircraft) that if I move my head forward but then point my head downwards to look down the view in fact stays forward but also moves up as though I've hit an invisible wall and the view is sliding up it. If I change the Z axis to the in-game zoom axis it works better (i.e. I can move the view forward and look down properly) but it's still not ideal because my default zoom seems to be too far forward and I can't seem to set it so that the view is not zoomed in so far by default, I keep having to move my head forward and reset Open Track's centre so that when I move my head back to my heads normal position the view is not so zoomed in. Has anyone any ideas why it doesn't work properly and of any fix? I've tried using PeterP's real neck mod but that doesn't seem to make a difference (or is broken by the latest version of the game). TIA

Hey all I just bought a new PC and I'm wondering how my experience in DCS 1.0 will improve (if at all, we're nearly at the end of September and 1.5 is not in sight (I thought it was supposed to be coming this month?), unless I've overlooked something?). I mainly fly the Ka-50 and Huey, although I do have the A-10C module (but still can't get to grips with it properly). My new PC is this one - http://www.scan.co.uk/3xs/configurat...xs-custom-1150 Specs - As in above link but with these changes: Case - Antec Three Hundred (same as my current case), added as an extra because they don't offer the case I want and I'm short on space so can't really go bigger. CPU - Core i5 4690K Haswell Refresh OC'd professionally to 4.6ghz Mobo - Asus Z97-P Cooler - be quiet! Pure Rock - Performance Air Cooler (little dubious about this as it's the cheapest one) PSU - 750W Corsair RMi, Modular, Silent, 80PLUS Gold (yay no random unused cables!) No GPU as I already have a nVidia GTX 960 mini ITX 2GB No HDD's (I'll use my existing ones as I have room for a spare clean Windows installation) No DVD drive (I don't even use my current BD Rom!) No OS (why would I need Win X when Win 7 runs fine for me) So, given that, with a nVidia GTX 960 and an AMD Phenom II x4 955 @4ghz, I currently get bad fps (in the 20s) around densely object populated areas (like airfields full of Hueys or FARPS in the Huey/Ka-50 campaigns) but decent 60+ fps in the wilderness, what can I expect with the new PC?

Saw that earlier, mostly I fly the Huey and Ka-50, so whilst handy for the A-10 it's not quite what I'm looking for unless I can easily modify it to work for the Ka-50/Huey? I've come across iDisplay but that seems quite laggy so far, even over a USB connection... And neither Hawgtouch or Helios work properly over iDisplay as the touch inputs on my Android tablet aren't recognised!

Hey all I recently bought a Tesco Hudl 2 (UK supermarket own brand 8.3" Android tablet running Android 4.4.2). So, I'm now wondering what in DCS I can use it for - i.e. can I export the Ka-50 Abris/Shkval to it or A-10 MFCD's/CDU or even Huey guages or the kneeboard (I currently have the kneeboard exported to a 2nd monitor via a viewport)? I mostly fly the Huey and Ka-50 though but A-10 stuff might be useful. TIA

Hey all Anyone here got a pair of Soundblaster Tactic 3D Rage headphones and use them with DCS? Just wondering if they work OK (I'm thinking about the "3D" aspect) and how well? TIA

Say what? Noticed that line in the sale pitch. What is 1.5 and what's happened to the release of 2.0 this year?!!!!

Hey all I may be starting a new job soon and thus may have some £ spare to spend on some flight sim equipment. So I'm thinking of "upgrading" my HOTAS. Currently I have a Saitek X-52 Pro, I am not convinced it's all that good after a year or two using it, for example I find it (or I cause it) jerks in it's movement sometimes, for example I can be pulling back on it and all of a sudden I see the diamond on the controls indicator go straight down to the bottom!! Also it's generally not all that smooth when trying to get past the centre point. I tried the magnet mod and that actually made the stick hyper sensitive and nothing I've tried (and I've tried lots of solutions) resolves the "sticktion" around centre. However I do like the amount of buttons and programmability of the X-52 Pro (and it's predecessor the X-45). I'd like to either get a Thrustmaster Warthog or a Saitek X-55 Rhino to completely replace the X-52 Pro, or a CH Fighterstick to replace the joystick. I mainly fly helicopters in DCS, especially the Huey, and I also fly planes in IL2 1946 and Cliffs of Dover. I also don't have rudder pedals (I sold my Saitek Pro Flight ones, too big for me for where and how I was sitting, long story) but if I can build a stand for my stick that I can fold up and put away after use I may go back to using pedals, so I need to consider lack of pedals for the moment... So, advice please? TIA

I tried modifying the A-10C HUD, using the info in that same mod (which is based on an older version of the game) to make the lettering bigger and I found that anything but the default value means you can't' fit all the text on the HUD and it ends up looking all wrong at best and unreadable at worst. I think the only way around it is either to use a snap view with the view zoomed or zoom in manually.

A 5yr old LG 21" 1920x1080 primary and a 7r old Bush 19" 1440x900 in portrait. Can't afford, and don't have the room for a newer large single screen, if I could afford it I could probably fit at most a a single 32" on my monitor arms, but then I wouldn't be able to run multi-monitor and I'm not entirely sure they'd even take the weight...

The part I'm disappointed about is that this has left me not knowing if I should sell my Oculus Rift. I have kept hold of it just to see what it was like in DCS 2, but now having no estimated release date has left me not knowing what to do with it. They haven't even said if we are looking at this year and with the VR headsets out early next year you can see my dilemma. I just wish they hadn't waited until June to say that they don't have a release date after the Feb news letter. Can I see your dilemma? Not really, I don't have an Oculus Rift. Nor do I, or am I likely to, have the sort of funds required for an Oculus Rift or any other upcoming VR headset - $350 or more!! Have to be blunt, and I apologise for being so, but your dilemma seems like what is commonly termed a "first world problem"... I would however think the answer is quite obvious, if you only want a VR headset for DCS 2, and DCS 2 is not even out, and you are not going to use the Oculus Rift for anything else then sell it.

Quite disappointed to not see any sort of a release on the horizon in the latest newsletter. Forgive me for saying this, and I'm sure I'll get a lot of hassle for it, but I'm starting to wonder if whilst people continue buying DCS1 content there's any incentive for ED to release DCS2? Just getting a bit tired of the "it's not ready yet" routine. Again apologies for saying so.

I also have the X-52 and generally find the two rotaries to be utter rubbish unless I want a narrow band axis. And I also experience the "twitching" when the pot is in it's middle position. I've got my X-52 plugged into my motherboard, and all power management options for my USB ports are disabled so I'd say that being on a powered hub is a red herring. I found the rotaries on my old (2nd hand by the time I got it) X-45 to be much better, never experienced any "twitching" with those and they seemed more accurate and easier to make fine adjustments on, so I think it's down to the quality of the pots, the knobs on the pots and the general design of how it's put together - my X-52 rotaries seem far too stiff and they aren't really knobs like the X-45 ones are. Personally I prefer the throttle of the X-45 over the X-52, the throttle of the X-52 may have more buttons but it seems stiffer (even with 0 tension on the screw), less smooth, the slider is anything but precision, and the rotaries as has been said are rubbish, and the X-45 throttle has that really handy rudder axis rocker on it. The X-52 stick is better than the X-45 though (as far as the sticktion/spring tension is concerned), if I could I'd combine the X-45 throttle with the X-52 stick - sadly Saitek made both HOTAS so you can't mix and match unless you want to plug in both HOTAS at the same time! To eliminate the "twitching" you can set a deadzone on the middle of the axis via the control panel options. That's where I find the rotaries exhibit that behaviour - it seems there's a point where it's not quite in the exact middle (despite you feeling it "slot" into place) and then it starts "twitching".

Wow! Where did you get those from?

Thanks. I must have been having a blonde moment last night because I've just gone back and checked and the mission I had saved with the carriers, was missing all the aircraft I had laid down, despite me having opened the mission I wanted to edit. I guess I must have used a blank mission and not realised it. Doh!!

Hello I created a single mission with all the aircraft I can fly in DCS World available from Batumi airport (the TF-51, UH-1H, Ka-50, A-10C, although I just realised I've forgotten the Su-25). However I've just added (just by left clicking to place the item) one of each nations aircraft carriers 10nm off the coast of Batumi so that I can take off from Batumi and go land on the carrier (with a helicopter) and doing so has removed my choice of aircraft when the mission is loaded and the mission just starts with the camera looking at the Russian aircraft carrier. What have I done wrong?

From my experience with the same HOTAS you only have to assign the pinkie or clutch buttons to a function in the game the same as you would any other key, however with the clutch button you need to go into Control Panel and then right click on the HOTAS icon and then go into the properties of the X52 Pro (where you see all the axis and buttons listed) and select the MFD tab and then untick the box that enables the the clutch button as a clutch button. As for the mouse hat, you can map it like keys but it requires setting each axis on the mouse hat up as bands and then each band has different % where stuff happens, for example it's x axis may have 3 bands 33%, 66%, and 100% and on 33/66 nothing happens but on 100 it makes whatever keystroke you assign to it. You have to do that in the SST profiler and use the profile you make each time you want to use the mouse hat as buttons. I've never done it but have seen it done on a few profiles I've downloaded, and yes it's not the greatest piece of software.

Check it in Windows Control Panel. If it still does it then it's a fault with the hat switch itself, probably loose wire/connection, as indicated by the fact you have to have the throttle in a certain position (presumably making the connection at this position and no other). If it doesn't do it in Control Panel then it's a problem peculiar to DCS, but I've the exact HOTAS as you and I can't say I've ever had such an issue.

Thanks guys, I got Helios working, eventually after having to do a repair install of Windows 7 because my .net framework was corrupted, but I think I'll stick with Hawgtouch for now as I have it nicely setup for the Ka-50 and A10-C. I can't seem to find a Helios profile for the Huey that has working radio devices (VHF/UHF/Nav Comm/ADF etc.), I think the one that does the knobs work but there's none of the indicators work (so I'd still have to look at the panel in the cockpit!) and that's a bit of a deal breaker as I wanted to put the armaments panel and the radios on my second monitor.

Ok thanks. I'm trying to install Helios on Windows 7 but I'm getting a message telling me I need .net framework 2.0 and I can't install it without?!!

So that'd be a no then. Does helios work in a similar way as Hawgtouch? The reason I've been using Hawgtouch is because I can click on the switches/buttons on my 2nd monitor and this stops me having to look down. I don't even have a touch screen and I was under the impression Helis only works on touch screens? If not is there a Huey profile that allows inputs via clicking the mouse on controls?

Hello I've recently been playing about with Hawgtouch, and found it very useful for the A-10C and the Ka-50. So, has anyone got any panels for use with Hawgtouch for the UH-1H? Panels such as the Armament panel and radio/nav devices panels would be great. TIA

The Gigabyte GTX 960 (ITX version) I ended up buying is silent. Can't say it's hugely improved my framerates, in fact in some games (Il2 1946, Cliffs of Dover, Project Cars) it seems at times like it's made little to no difference, but for DCS it's given me slightly better fps (in some situations, but still the same poor FPS (in the 20's) when for example looking at the FARPs in the UH-1 Stray Eagle mission, just not quite as low as they used to be) and made the game more playable. Can't comment on 960 over the 560ti as I "upgraded" from a Sapphire Radeon HD 5870.

Hello Just a quick question, I'm wondering how are the waypoint co-ordinates expressed on the Ka-50 PVI-800? For example, in a mission I have a 1st waypoint and the PVI displays the following for it - 1st line reads 42'09'7 1 2nd line read 042'23'7 I'm assuming the 1 means it's waypoint 1. But what about the rest, are they longitude, latitude expressed in minutes, if so what's the 7 on each line supposed to mean and why are there 2 lines that differ? TIA

Thanks, I thought that might be the case. I increased shadows to high and didn't notice a hit on the fps, not sitting on the FARP in Stray Eagle or the apron in the Ka-50 mission "how to blow stuff up", but I also didn't notice an improvement, I either gained or lost 1 or 2 fps at the most. I've been able to increase civ traffic to medium and draw distance to high though, and they don't seem to impact all that much. I also tried overclocking my AMD Phenom II x4 955 BE CPU (which I'm very hesitant about doing as in the past I've blown a mobo by doing that and my parts are out of warranty) and I can run it at 3.9ghz, up 0.7ghz from the stock 3.2ghz but that (combined with running Gigabyte OC Guru with a 1407 boost and mem clock of 8k mhz) didn't make a blind bit of difference, but opentrack crashed and I believe it was as a result of the overclock... I think the biggest FPS killers (for me) are scenes being on high, cockpit shadows being on and water being on anything other than low (or off if there was such a setting).