Raven_Morpheus

Hey all Yesterday I was using Trackhat Opentrack for headtracking in DCS. I also use a PS3 controller to fly as generally I can't be bothered getting my Saitek X52 Pro out. I set my Windows 7 PC to Hibernate last night. I've woken my PC up today and gone to play the game, latest version, and the game thinks TrackIR is present, even though I have no headtracking software running in the background (as far as I could see) and my mouse look control is bound to the PS3 analog left stick. However I can't see any bindings in the controls menu that would suggest that TrackIR or my PS3 controller are bound to the mouse look controls. Anyone come across this or something similar before and/or have a fix? Thanks in advance. EDIT - nevermind. Situation back to normal. I realised I wasn't looking in the right place and found the camera bindings under Axis in the controls menu. Deleted the bindings to my PS3 controller and non-existent TrackIR and mouse look works fine again. Odd that the game thinks I still have a TrackIR plugged in still though.

32gb is outside my budget. I'm considering buying just a set of 8gb 2133mhz (i.e 2x 4GB) and sticking it in the 2 spare slots on the Asus Z97-P, I'm guessing that would work also? Certainly would be a less expensive option for me.

Ok, well apparently what I've got installed currently is 2x Corsair Vengeance Pro DDR3 4GB 2133mhz, according to the invoice I just dug up. So if I get DDR3 2133mhz RAM that'd be a drop in fit, right?

Thanks Ian that's great. It seems to work now. Although I wasn't expecting anyone to fix it for me. But thanks again for doing so. Although I did have a problem to begin with. I loaded it once, then exited and went back to load the mission again, and it wouldn't load. The dcs.log file had that error about the FARPs.edm files so I deleted those, and repaired my install (again). Seems to load OK now. Crossing my fingers...

OK, so I tried a cleanup/repair after re-updating to 2.5.5.whateverthelatestis, and that mission still doesn't work for me.

Thanks, haven't tried a cleanup/repair. I have however reverted to 2.5.4.30386 and the mission now loads for me. So definitely an issue with this mission in 2.5.5 for me. I'll update to the latest version, run a cleanup/repair (although I shouldn't have to, right?) and see what happens...

Hmm. Thought it might just be a problem my end. It was working until I updated to 2.5.5. It gets past the briefing, then I get an A-10C splash screen with the progress bar, and the bar doesn't go past halfway, it just sits there. Other missions seem to work fine, of the one's that I've tried so far at least. My log is attached. dcs.log.txt

Hey all I have the attached mission that I'm trying to play, but it won't load for me. Would anyone here be willing to try it out and see if it's just a problem on my end or one with the mission/2.5.5 Open Beta? Thanks in advance. A10c-Target_Practice.miz

Ah right. So even if I install just the new 16gb I'm guessing I'll have to adjust voltages and timings in my BIOS?

Hey all It's been a while since I've dabbled with installing RAM... My PC has 8gb of DDR3 RAM, in 2 sticks of 4gb, at (according to CPU-Z) a DRAM frequency of 1066.5 mhz, can't recall what brand. My motherboard is an Asus Z97-P. I'd like to put in a 16gb set of DDR3 PC3-12800 RAM, this for example - https://www.ebuyer.com/408828-patriot-16gb-black-mamba-ddr3-1600mhz-pv316g160c9k Can I just plug the new RAM into the 2 remaining slots on my Asus Z97-P and fire up my computer with out doing anything else? Thanks in advance for any help on this.

Wasn't sure where to post this so apologies if it's in the wrong sub-forum. I'm seeing some rather unhelpful cockpit shadows in the Huey, don't know if it's the same in the other modules I have as I've not tried them yet. I have cleared, twice, my FXO and Metashaders2 folders. Pics - Amongst other things it looks like some of the overhead panel dials/knobs/switches are being cast as shadows. Are the shadows meant to look like that?

Hey all Without using 3rd party apps is it possible to export the dials from the Huey to a 2nd monitor? With the way the cockpits are at the moment I'm having trouble at least reading the radar altimeter, and certainly in some shadowed circumstances most of the dials... Alternatively can anyone recommend a 3rd party app to export the dials? If one exists? Thanks in advance.

https://www.militaryfactory.com/aircraft/ww2-helicopters.asp

Of the 3 helicopters, and 1 plane module, that I have, not including the freebies - The Ka-50 is easy as pie due to the autopilots. The A-10 is easy so long as you remember to keep it just around 140-150mph (take off speed) and don't be too high when you cross the start of the runway, about 100-200ft is good, same applies to any plane really, keep it above stall speed and just around take off speed, and not too high. Don't know about the Mi-8 because I admit to not having flown it much. I find the Huey the hardest to land. I find slowing down, transitioning to a hover, and losing height takes ages and under fire I'm a sitting duck, or something goes wrong, like ending up in VRS. Can't do "combat" landings either as I inevitably come in too hard, too fast, or in the case of a hillside, too low! Landing is THE most difficult thing I find in the Huey, it takes a great effort of concentration on my part.

Can you make a distinction between the Saitek X52 (the silver/blue one) and the Saitek X52 Pro (all black with bits of silver), I may be wrong (probably am) but there's a difference between the two, could just be build quality. Also like to add that I use a PS3 dualshock gamepad via SCPToolkit drivers, easier than getting the Saitek X52 Pro out all the time...

Anyone?

Thanks. The file size comes out a bit large using those settings though. I just recorded a 57 minute mission and it came out at just over 7gb! That's far too big to upload, it'd take hours for me! Anyway of reducing the filesize without compromising the quality? EDIT - nevermind. I think I chose the wrong setting. Just recorded a 10 minute video, it came out at 148mb, times that by 6 to get the filesize for an hour long video and you get 888mb, so far more manageable. No loss of quality either it seems.

Hey all I'm finding it a bit difficult to read the HUD in various modules, especially when it's against the sky, on my 22" 1080p monitor. Is there a way to change the colour of the HUD and/or the brightness or scale of it's text? Thanks in advance.

Probably not the correct sub-forum for this... But can anyone here tell me how to setup OBS Studio so that it doesn't impact on framerate but I get a nice clear recording in 1080p with no compression artefacts? Thanks in advance.

As far as I know you can't use it for the map view (I'm assuming you mean the one gained by pressing F10) unless it became a viewport in 2.5.x. What you can use it for straight out of the box is the MFDs in the A-10C, the Shkval and Abris in the Ka-50, the kneeboard in any module, and any other similar displays in modules you may have. With some third party software you can also export the dials and gauges from various modules. Personally I used to use my 2nd 1440x900 monitor, in portrait orientation, to export the MFDs of the A-10C, the Shkval and Abris of the Ka-50, and the kneeboard on the modules I own. Haven't tried it recently though since 2.5 was released.

So, I tried forcing 8x AA in the nVidia control panel (using override application setting), to see if I could reduce jaggies, and how much I'd lose of the 40fps I get, but it doesn't seem to do anything at all. Are the in-game AA options, which kill fps, the only options that work? Thanks in advance.

Back when NTTR and portions of the new graphics engine was released a big thing was made about the F-86 having shiny metal look skins. Whilst I don't own the F-86 I am wondering how the shiny skins are made? And if it's possible to do that on the Huey or the TF-51 or any of the modules really? Thanks in advance.

Probably. It would be nice if the game can be optimised for people on lower end systems so that they can run the game at framerates similar to v1.5.8 with similar graphical quality as v1.5.8 - I was running v.1.5.8 and flying the Huey Stray Eagle mission, one of a couple of missions I use for making sure things are working OK, getting about 100fps, certainly a solid 60fps on average, in higher settings with equal or better graphical quality (apart from the density of trees) than in 2.5.0!!. However I don't think that ED have any intention of making that the case - they are only interested in those who have top end hardware. If that's not the case I'm not seeing any indication of it. Rather silly really from a business point of view imho - why limit your game to a minority of users?

Stable. I've just got it running smoothly, in the few select missions I've tried. I've also been bitten before by updates that have been released and made things worse, or are just simply large in size, the last couple of updates I did were 10gb+! I'd rather fire up the game, knowing that I'll be straight into the game and enjoying flying, no waiting for an update to download, no problems caused by an update. Plus I no longer have room on my SSD for the open beta version, I have 85gb free, the open beta is now 87gb - and I only have the Caucasus and NTTR maps!!

That's what I've had it on since I was last tinkering with most settings. Something to do with load times being shorter. Please note though - I am not getting major stutters/framerate drops any more. The ones I am getting are negligible and infrequent now and the game is playable for me, on the handful of missions I've tried at least. I've just had a good night's worth, since about 18:30 until about 10 minutes ago (01:20), flying with no problems - I tried Stray Eagle three times for various reasons (all my own fault), and the Ka-50 How to blow stuff up mission by Para Bellum/Yurgon. Maybe I will get problems if/when I try the Huey/Ka-50 campaigns but for the moment it's all running nicely. I won't even touch multiplayer because I'm not that good a pilot. Please do. I suspect I can increase a few settings. I was more concerned with eliminating the stutters/framerate drops that were making even the simplest missions unplayable.