Raven_Morpheus

Hello Having recently bought a Gigabyte Geforce GTX 960 2GB (mini ITX version) I've found I'm getting better framerates in DCS than I was previously with my Sapphire Radeon HD 5870 1GB, in fact most of the time unless I'm looking directly at a FARP, for example the one in the Stray Eagle UH-1 mission, I get reasonably playable framerates. So, I thought about increasing the eye candy a little. Here's my current in-game settings - And here's my graphics.lua - -- available through options.graphics Plugins = { "DXRenderer.dll", "ZweiBlau.dll", "AVIMaker.dll", "Weather.dll", "NGModel.dll", "edterraingraphics3.dll", "Effects.dll", } Precaching = { around_camera = 200000; --50000; around_objects = 5000; --10000; around_types = {"world", "point"}; preload_types = {"map", "world", "mission"}; } PrecompiledEffects = { mode = "USE_PRECOMPILED_EFFECTS_FOR_UNCHANGED_FILES"; --mode = "USE_PRECOMPILED_EFFECTS_ONLY"; } VFSTexturePaths = { "./Bazar/TempTextures", "./Bazar/Textures/c-130", "./Bazar/Textures/Batumi_buildings", "./Bazar/Effects/EffectTextures", "./Bazar/Effects/EffectRiverTGA", "./Bazar/Effects/WaterEffects", "./Bazar/Effects", "./Bazar/Textures/old_textures", "./Bazar/Textures/f-15", "./Bazar/Textures/e-2d", "./Bazar/Textures/f-15e", "./Bazar/Textures/An-26B", "./Bazar/Textures/An-30M", "./Bazar/Textures/Patriot", "./Bazar/Textures/kc-135", "./Bazar/Textures/e-3", "./Bazar/Textures/il-76md", "./Bazar/Textures/a-50", "./Bazar/Textures/il-78m", "./Bazar/Textures/uh-1", "./Bazar/Textures/Su-27", "./Bazar/Textures/Su-33", "./Bazar/World/textures/TexturesBMP_weapons", "./Bazar/World/textures/WorldTexturesBMP3", "./Bazar/World/textures/WorldTexturesTGA3", "./Bazar/World/textures/WorldTexturesTGA2", "./Bazar/World/textures/WorldTexturesTGA", "./Bazar/World/textures/WorldTexturesBMP2", "./Bazar/World/textures/WorldTexturesBMP", "./Bazar/World/textures/WorldTexturesBMP1", "./Bazar/World/textures/ShipTexturesBMP", "./Bazar/World/textures/Y_FInal_Texture", "./Bazar/World/textures/Y2_FInal_Texture", "./Bazar/World/textures/Y3_FInal_Texture", "./Bazar/World/textures/Y4_FInal_Texture", "./Bazar/World/textures/Y4_FIame", "./Bazar/World/textures/Y5_FInal_Texture", "./Bazar/World/textures/Y6_FInal_Texture", "./Bazar/World/textures/Vehicles_misc", "./Bazar/World/textures/A-10_Weapons", "./Bazar/World/textures/AH-64_Apache", "./Bazar/World/textures/gunners", "./Bazar/World/textures/KA-27textures", "./Bazar/World/textures/MI26_textures", "./Bazar/World/textures/UH_60_textures", "./Bazar/World/textures/T_Textures", "./Bazar/World/textures/Ka-50_general", "./Bazar/World/textures/A-10", "./Bazar/World/textures/L-39", "./Bazar/World/textures/yak-40_tex", "./Bazar/World/textures/NAVY_Textures", "./Bazar/World/textures/Railroad_trains_texture", "./Bazar/World/textures/Su-25_common_textures", "./Bazar/World/textures/Su-25_Georgian_Skins", "./Bazar/World/textures/Su-25_Russian_Skins", "./Bazar/World/textures/Su-25_Ukrainian_Skins", "./Bazar/World/textures/MI-8MT", "./Bazar/World/textures/Mig-31", "./Bazar/World/textures/F-18C", "./Bazar/World/textures/P-51D", "./Bazar/World/textures/Tu-22m3", "./Bazar/World/textures/mq-9_reaper_textures", "./Bazar/World/textures/Su-24M", "./Bazar/World/textures/Su-24MP", "./Bazar/World/textures/AeroWeapons", "./FUI/Common/", "./FUI/Common/Net/", "./FUI/Fonts/", "./Bazar/ParticleEffects/textures/", "./Bazar/Effects/ParticleSystem2/", } ModelPaths = { "./Bazar/World/Shapes/", "./Bazar/Terrain/Structures/High/EDM/", } Camera = { Low = { near_clip = 0.2; middle_clip = 4; far_clip = 50000; structures = {10, 1000}; trees = {1000, 1500}; dynamic = {300, 20000}; dynamic2 = {300, 20000,0.5}; objects = {3000, 10000}; mirage = {3000, 15000}; surface = {3000, 15000}; lights = {50, 10000}; districtobjects = {100, 100}; districts = {2000, 2000}; lodMult = 1; lodAdd = 100; }; Medium = { near_clip = 0.2; middle_clip = 4; far_clip = 50000; structures = {25, 3000}; trees = {1000, 6000}; dynamic = {300, 5000}; dynamic2 = {300, 5000,0.5}; objects = {3000, 10000}; mirage = {3000, 15000}; surface = {3000, 15000}; lights = {100, 15000}; districtobjects = {200, 200}; districts = {5000, 5000}; lodMult = 1.5; lodAdd = 0; }; High = { near_clip = 0.2; middle_clip = 4; far_clip = 100000; structures = {10, 10000}; trees = {3000, 15000}; -- {1000, 10000}; dynamic = {3000, 15000}; -- {300, 20000}; dynamic2 = {3000, 15000,0.5}; -- {300, 20000,0.5}; objects = {3000, 80000}; -- {1000, 100000}; // 3000, 100000 mirage = {3000, 15000}; -- {1000, 20000}; // 3000, 20000 surface = {3000, 15000}; -- {1000, 20000}; // 3000, 100000 // 10000, 100000 lights = {3000, 15000}; -- {100, 20000}; districtobjects = {200, 200}; districts = {5000, 5000}; lodMult = 1; -- 1.5; lodAdd = 100; -- 0; }; } --[[ -- these params are set via options shadows = 1; lights = 0; mirrors = 0; textures = 2; water = 4; scenes = "medium"; effects = 0; heatBlr = 0; MSAA = 2; HDR = 0; TranspSSAA = 1; environmentMap = 1; ambientMap = false; ]]-- DebugColoredTexture = 0; ScreenshotQuality = 90; ScreenshotExt = "jpg"; FogParam1 = 6; FogParam2 = 1.1; PilotNames = false; maxfps = 120; RenderEffect = 0; render3D = true; cockpitOnly = false; treesVisibility = 1500; sync = false; MFD_render_params = { two_pass_always = true; dist_multiplier_fov_base = 0.3; second_pass_start_fov = 0.1; second_pass_far_clip = 100; single_pass_near_clip = 10; } -- íàñòðîéêè Ëóíû Moon = { Ktex = 1.7355; -- êîýôôèöèåíò, ó÷èòûâàþùèé ðàçìåð ëóíû íà òåêñòóðå 512.0/295.0; Smax = 3; -- êîýôôèöèåíò ðàçìåðà ëóíû ïðè óãëå ìåñòà ðàâíîì íóëþ Smin = 2.5; -- êîýôôèöèåíò ðàçìåðà ëóíû ïðè óãëå ìåñòà >= Hmax Hmax = 45; -- ìàêñ. óãîë ìåñòà â ãðàäóñàõ â ïðåäåëàõ êîòîðîãî ëóíà èçìåíÿåò ñâîé ðàçìåð moonLightColor = {63.75, 71.4, 89.25}; -- öâåò ñâåòà îò ëóíû } Stars = { c0 = 0; c1 = 2; c2 = 9; c3 = 10; flickerEnabled = true; tau = 15; period = 20; } So, what options impact the most on FPS? I.e. what can I increase without losing too many FPS? Also Is there anything I have set that I can lower and gain fps without sacrificing the current look of the game? TIA

Hello I've tried the A-10C in-game training videos/missions but they are so full of "waffle" and those annoying "press space to continue" moments that I get lost, confused, and generally feel like I'm not really learning how to operate the A-10C systems in a basic manner. I have the great "how to take off and blow stuff up" mission and PDF for the Ka-50 (sorry I forget who made it, but I thank the guy that did) and I found that a very easy tool to learn the basics of the Ka-50. So, I'm wondering if there is anything like that for the A-10C? TIA

Thanks. Think that might be a bit expensive though, upon reflection. Buttons are likely to cost about £1 each, the controller board something like =>£25, keyboard, to cannibalise for the button tops, a couple of quid, project box about £5, USB cable about £1-£2, so I'm looking at =>£50 just to make a PVI-800 key pad!! I mapped it the other day to the numerical pad on my current keyboard and that works fine, although I'm missing a few buttons, but I never use those ones on the PVI-800 anyway (don't even know what they're for!) - I think I'll stick with that.

Ah cool I've just found the wiki about snap views (I knew it was called something like that but wasn't sure if it was snap views and if snap views would do what I wanted). I've tried just now to set views up for the panels in the Huey and it works great. Although this doesn't appear to work - I press RCtrl+Num0 and it just goes to an off angle view of the Huey dashboard and the snap views aren't set to toggle. Same thing in the Ka-50. Hmm. It works great, and means I don't have to do contortion with my head to get the view right with my head tracker... As for the key pad problem, what about making a 25 button button box - would that work, and would you (or anyone else) happen to know how to do it? I'm assuming some momentary push buttons (with customised keyboard keys attached) and a Leo Bodnar button box card would suffice (and a project box to fix it all to)?

Hello Just came across this... Fantastic find but I'm wondering something - is it possible to have random cockpit colours, So for example if you load up Worn Black you get either black or blue cockpit? Or can you only have 1 per skin? Also, any ideas on other liveries and their cockpit colours (I see only 3 were identified when this thread was posted)?

Hello Apologies, I know this is probably the wrong sub-forum but I wasn't sure where to put this... I've had a couple of things on my mind for a while now so I thought I'd ask as I'm drawing a blank using google and whatnot. 1) Is it possible to set up custom views so that I can look directly at panels. For example would it be possible to set a view so that I'm looking at the overhead panel on the Huey as though I'm looking at it in a top down view, or as another example would it be possible to set a view so that I'm look at the PVI-800 in the Ka-50, again as though I'm looking at it in a top down view? 2) Multiple keyboards/numberpads? I'm thinking of getting one of those USB numberpads to use as my PVI-800 and putting labels on the keys (so that I don't ruin my main keyboard). Does DCS support multiple keyboards/numberpads or would I have to have some sort of programming software to make the USB numberpad work? TIA

Last chance before I put them on ebay. EDIT - sold on ebay for £60.

I've managed to learn how to "take off and blow stuff up" with the KA-50 and I can do very basic waypoint navigation (I think I could do slightly more than switch between waypoints or airfields on the PVI if I read a little more info), I've managed to learn the basic startup procedure for the UH-1H off by heart (although I quite often forget to turn on my radar altimeter) and firing guns is left to the AI unless I want to fire rockets via the pilots gunsight, and that's fairly straight forward. I can't for the life of me remember how to select waypoints in the A-10C, and I have even less of a clue of how to fire weapons. Despite having been through the in-game tutorials. One thing that I find difficult is remembering where all my keys are mapped to on my hotas. The other day I was trying the tutorials again and I had to check which POV Hat I had mapped to the Coolie, the DMS, and several other keys - and that was just for the navigation tutorial!!

Opentrack with DIY IR LED array and PS3eye (unmodified, I just made a cap that slides on with the red/blue lenses of a pair of card 3D glasses to act as an IR filter). My IR LED array (3 IR LEDs in a similar shape to Mano's but smaller) runs off 2 AAA batteries (rechargeables) but I also have another that runs off USB but I found the cable rather annoying over long periods of time. Wish I could work out how to make a dual power (USB and battery) IR LED array though, for those moments when the batteries die... I've just looked at EDTracker and it looks great (and reasonably priced @ £30-£40 if you want a prebuilt one) but it would be better if it was wireless (but I don't suppose that's feasible) - having an annoying cable dangling all over the place is why I went battery powered!

This is great news. I've been watching J.A.G recently, and there's a lot of F-14 action in that, mostly either stock footage, or borrowed from Top Gun, but it's made me want to buy and build a 1/72 model kit and also look for a flight sim with the F-14 in it - unfortunately so far no good flight sim (imo) with the F-14 exists, the only one I found was an addon for FSX. I only hope this isn't as hard to operate as the A-10C - I am baffled by anything but getting on/off the ground and basic flight in the A-10C!

Unfortunately an extension is not something I can make use of as I don't sit at a desk on a chair, I sit on my bed with the joystick between my legs, thus I can't put the base on the floor to make use of an extension. Having said that however, and having said my X52 Pro is crap compared to an Xbox 360 joypad, when it comes to hover/transition to/from a hover, I have just disproved that theory. I was wondering if the problems was the curves I had set a while back for the X52 Pro pitch, roll and rudder axis, because I never set any on the joypad axis, so I reset them to default and tried Stray Eagle again... And either I'm getting better at doing it or removing the curves worked because I managed to make as good if not better landings than I did the other night with a joypad. I still can't do those kind of "rolling" combat landings or the ones where you see pilots coming in and flare all of a sudden to come to a stop, I have to transition to a hover and then manoeuvre into position (quite often whilst dropping and rotating/sliding sideways a bit wildly), so I'd be a sitting duck if there were any enemy troops around. And it's only because I know where the LZ's are that I manage to land properly because I think if it were a proper SAR mission where I didn't know where the troops are I'd have to circle a few times once I've found them to be able to even start landing, so again I'd be an easy target. Definitely happy with tonight's attempt though, just hope I don't come back to it a few weeks/months down the line and find I can't do it, again...

Thing is my Saitek X52 already feels quite loose anyway, it's not as though I need a ton of force to move it. Unfortunately the MSFFB2 is getting rare and rather expensive for just a joystick, plus the fact they are all used so no warranty if it breaks 5 minutes after you get it. I just wish I could get the sensitivity to hover/transition to a hover like I can with the Xbox 360 pad with my Saitek X52 Pro stick, but I've tried all sorts of things to no avail. Although I've yet to zip tie the outer spring to see if that makes a difference, that centre plate probably doesn't help either. Collective control is also worse with the Saitek X52 Pro Throttle imo, I found it much easier to control the collective using the joypad's D-pad up/down set in-game as the buttons for the collective.

Yep as the title says, I used an Xbox 360 pad to fly the UH-1 and rescue Stray Eagle. Why? Because I wanted to see if I could. Thing is I'm now a bit miffed, because I find it far easier to get into a hover and land using my Xbox 360 pad than I do using my Saitek X52 Pro. In fact the landing portions of the mission were far easier than I've ever had them with my Saitek X52 Pro! I mapped the collective to the D-pad, pitch and roll to the right stick, the rudder to the triggers and pilot trimmer to both shoulder buttons (because when using the rudder I can only press one of the shoulder buttons dependent on which trigger I'm using). It wasn't great for level flight, but it just seemed much easier to hover and transition to/from a hover. So why is my Saitek X52 Pro worse? My track is attached if anyone wants to watch it. Stray Eagle - 2 decent landings 360 PAD.rar

Actually scratch that second query. Just checked and it's not happening now. Must've been fixed in a recent patch or something. It only happens if I am holding my joystick in a position and press t or my trim button multiple times but that's because it's registering my joysticks position and adding to the deflection in-game each time because I haven't returned my joystick to centre. My bad.

Not my stick, I've checked that already. Unless it's an issue peculiar to the Saitek X-52.

Yes this is how I've been flying the Huey. I've been reading different recently. Thanks guys for clearing that up. Next question then - In the Huey, when I press the trim button or t on my keyboard, the actual stick in the cockpit moves (to one side or the other, I forget which way) and the position is also moved on the controls indicator. This happens whether I've got central position trimmer mode set or not. If I keep pressing the trim button the stick keeps moving the same amount in the same direction each time and I can end up with the stick in the cockpit completely deflected to one side (and the controls indicator shows the same position). This happens even if my joystick is at centre. Is that normal behaviour? It seems odd to me as it seems a degree of deflection is added each time the trim button is pressed.

Hey all I keep reading conflicting information about how trim works for the helicopters in DCS, specifically the Huey. Now, I've worked out how to use the trimmer in the Ka-50, it's this - Press and hold trim button (t on the keyboard) Move stick Release trim button This avoids fighting the autopilot. Now for the Huey I've read 2 different things - The 1st is just press the trim button when stick is in position. The 2nd is as above for the Ka-50, press and hold the trim button then release it when the stick is in position. So, which is correct? TIA

I have one set of Saitek Rudder Pedals for sale, only used a couple of times for about 5 minutes each time. These - http://www.saitek.com/uk/prod/pedals.html I'd like £75 for them but I'm open to offers. UK shipping only. Payment by paypal only.

Thanks guys, your advice is much appreciated. I think the problems I was having on my ingress to the LZ in Stray Eagle were because I was following too close behind the 2 Cobra's, if I hang back a bit (i.e. lose sight of them just after take off) I don't encounter so much hassle, presumably because the Cobra's have done their job. Different story on the way back to FARP Dallas though, I keep getting my ass shot to pieces following the return flight path marked on the kneeboard, I think I might be better off going back the way I came... Doesn't seem to matter what I do to avoid it though, the AI seem to be crack shots and/or have magic heat seeking bullets! And if I try to be aggressive and go up/down/left/right a lot I tend to crash (or get into difficulty that is likely to lead to a crash, and usually does!). Also generally I'm doing ~100 knots IAS during general flight so it's not as though I'm cruising when I get hit!!

Hello Wasn't sure which sub-forum to post this in so apologies if this is the wrong one... Just wondering, probably a bit of a n00b question, but how do you avoid AAA (guns, SAMs etc.) when flying in the Ka-50 and Huey (particularly the Huey)? I just played the Stray Eagle mission (for the nth time as it's the only one of the stock Huey single missions I like (I can't get up to the summit of Mt Elbrus quickly enough and I'm rubbish at strafing runs in the Huey). Just as I was approaching the LZ (probably about 30 secs or so away) my pilot and right door gunner got shot, ended up being inconsequential anyway as I crashed into the hill side (as usual, really can't master landings in the Huey!!). However the above caused me to question how to avoid the AAA gun(s) that killed the pilot and right door gunner because I realised I have no idea how to?! TIA

Yeah I think everyone is holding out for EDGE. We were promised it for the end of February this year if I recall. 2 days to go... :music_whistling:

Sadly my GTX 960 is not as much of an improvement as I had hoped. I did a test mission (flying by keyboard, lol!) using Stray Eagle and looking ahead away from the FARP I get decent fps, in the 40+ range. However if I rotate the helicopter to look at the FARP the fps drops to 20. Which is almost as bad, if not the same, as it was with my HD 5870! Haven't even bothered putting my 2nd monitor on yet, I will assume I won't be much better off in the Ka-50 with the Shkval and Abris on my 2nd monitor. :( Oh well, at least the new GTX 960 seems to have resolved the issue I was having in general with my PC, I think, seems OK so far...

Thanks guys. Got the card this morning, installed it, fired up DCS, fired up the Stray Eagle mission and I was getting 40-50 fps just sitting cold on the pad. Looking around behind me dropped the fps to about 16 but I'm not likely to look behind me that much, and looking to the side (at one of the Cobra's about to take off to my right) was no worse than looking forwards. I think I might have playable fps in DCS now (I already had semi-playable fps (40fps average in empty mission maps) but FARPS and Airports in the stock missions killed the fps)! Will test more tomorrow when I have time.

Hello I just bought a Gigabyte nVidia GTX 960 2GB video card - this http://www.gigabyte.com/products/product-page.aspx?pid=5369#ov My current rig is as follows - AMD Phenom II x4 @3.2ghz Gigabyte mobo GA-880GM-USB3 8GB 1333mhz DDR3 RAM Sapphire Readon HD 5870 1GB Corsair 650TX PSU 7200rpm HDD (IDE) I bought the GTX 960 because I believe my HD 5870 is failing on me (it is 5 years old!) and tech reviews I've seen seem to indicate the GTX 960 is an upgrade from a HD 5870(?). I keep getting days when I resume from sleep (at least the PC being on sleep seems to be a common factor in causing this issue) and after a few minutes I get a black screen with vertical grey stripes (kind of looks like a pin stripe suit) and then in some cases no output at all, the other day I was lucky to reboot (via the on/off button) and get into the BIOS to change over to the onboard mobo GPU because I was getting flickering with the black+grey stripe screen even on POST!! The problem doesn't happen if I leave the PC on all the time, and it goes away when it does happen if I pull the 5870 out and plug it in again but it's been happening more and more recently so I thought I'd upgrade my GPU to rule that out as being the cause... On the Huey mission Stray Eagle (as an example) I get about 25 fps whilst sitting on the FARP pad and significant drops to 10fps around airports in the Huey campaign, with a mix of low to medium settings (textures on high) in 1080p. Can I expect any boost in FPS in DCS with this new card?

Hello I run 2 monitors, however they're 2 different sizes and native resolutions. One monitor (secondary) is a portrait monitor at 900x1440. The other monitor (primary) is a 1920x1080 monitor. Is there a way I can size the two monitors in Windows so that the combined area of both is only 1920x1080 and then obviously use that resolution in DCS World and still have multi-monitor output?