Sn8ke

Going to have this printed to coil binding at kinkos. which dimensions should I use?

The Marine Corps also exclusively uses the Litening pod.

Here are a few more:

Hornet hype Took these yesterday: VMFA-232 “Red Devils” are the Marine Corps first/oldest fighter squadron, full of tradition. They are the only naval aircraft where all the aircraft in the squadron depart from standard squadron colors and sport red markings. The squadron had to obtain a special waiver to do so. This is the Squadron Commander’s jet.

I can only select up to 'High' in the in-game configuration settings. If I'm not mistaken, we used to be able to select up to 'Ultra.' Now the cockpit shadow quality looks like the saw-tooth blade of a hack saw. It is almost an annoyance rather than adding to immersion. Is there a way we can get that back to ultra?

Same issue here

Resolved: Installed the latest updater. Worked afterwards.

While installing the latest update (9/22/17), the following error message popped up: (See attached image)

Awesome, thanks for the info. This is an awesome multiplayer campaign. As you can see via my signature, I run a fairly robust system, so I was caught off guard by the stutters.

Grimes the original files have a stutter issue and I believe not compatible with the latest update. Can you send me the updated files? Thanks!

Download links are b/o

Ok cool. What is the key combination?

When you refer to recenter do you mean TrackIR5 recenter or an in game recenter?

This has reared its ugly head again w/ the latest updates. Can anyone else confirm?

Did the developers actually adjust the neck position/headsize/ viewpoint setting for this latest update?

This is for sure an issue. Just did a fresh system build, reinstalled DCS w/ latest update. I've used PeterP's proper neck position view.lua mod for years. With the Warthog HOTAS Throttle zoom lever in detent, I should be in default correct position. With newest update, it's out of whack; way too far up to instrument panel. Not in the position it should be. I'm surprised more people haven't posted about this.

Can it be confirmed this mod works with the latest DCS updates? Just curious because I just reinstalled DCS after a new build and the mod sets the default view very close to the instrument panel unlike before.

Just upgraded to Windows 10 Pro 64 with a fresh OEM install and system new build (7600K @ 5.3ghz // Asus IX Code). Everything appeared good-to-go until my Logitech G510 Keyboard would work in windows but not during the boot process to get into BIOS. Bought a generic software free plug and play keyboard to resolve that for now. Now to the bigger issue: I installed the up-to-date Thrustmaster Warthog drivers. Plugged them in, etc. Opened the TARGET device analyzer. The throttle was indicated and appeared functional, the joystick did not appear. I opened firmware update to investigate. Throttle firmware was indicated up to date. Joystick indicate '0.' I clicked firmware update, after about 15 seconds a red 'X' appeared with a "b\Bootload 0x0000000C error message. This was while plugged in USB 2.0. Uninstalled drivers, restarted, changed USB ports, reinstalled...same thing. I pulled up a document by Thrustmaster detailing the "Bootloader method" for installing the firmware. Step by step, negative results. Is this a known issue, and how do I correct this?

Anyone using such an array with success? Why use RAID0 with DCS, and most importantly, why NOT use RAID0 with DCS?

I'm aware when running SLI, the TGP settings must be either 512 every frame or 1024 every frame. I indeed have this set, however when I have my TGP set to whita ht or black hot, I get 3d object flicker. TV mode I don't. Is this a known issue or is there a work around? Thanks for your time in contributing helpful input.

I am using two 1080's in SLI, I have a confirmed g sync monitor (ACER XB280HK). I've used g sync in DCS relatively successfully, However recently when I have g-sync on the NVI, v-sync set to app controlled and off in game, I am getting a displayed FPS greater than 120, well above my monitor's refresh rate of 60 hz. I have the latest Nvidia drivers 382.33. I even used DDU to roll back to drivers which g sync worked with negative results. Has anyone had a replication of this issue? Is it possible the g sync is b/o within my monitor's hardware? Thanks for any helpful input.

From my experience, this issue replicates itself within minutes in most multiplayer servers. I Have a core I7 CPU @ 4.9ghz and two 1080 GTC SC's in Sli. Gsync going on a 4k 28". After several minutes, my steady and smooth 60 FPS starts behaving erratically, jumping up to 70+, then down to 40's and back up to 60. When panning with Track IR 5, the screen doesn't tear, it just skips all over the place. I turned of gsync and used only Vsync...same problem. I turned off sli and used no NVI profile...same problem. Is this known and how do I fix this?

RIP F-14 Lol I knew it was too good to be true.

There is an app called 'DDU' - Display Driver Uninstaller. Very useful for rolling back drivers or reinstalling drivers.

I tried that, negative results. What I did do which worked successfully was roll back my nvidia drivers to 368.69, gsync is working now. From my experience, nvidia driver updates are never gsync friendly.