christiankirk81

You got upwind and downwind mixed up... Focus on being on-speed and stable while on downwind...key is to not fight the trim with stick pitch movement, let it settle till you fight the sweet stable spot... extend your downwind if you need to, once you get better and quicker at being on-speed and stable on downwind, you can shorten your groove gradually... If you have a track of your traps, we can help diagnose your opportunities... Keep at it...when you feel too frustrated and about to break stuff...stop and get some air...keep grinding :)

Now AIs got Skynet-level technology now...interesting...:megalol:

Same issue for about a couple of days now since latest patch... EDCORE: try to write dump information EDCORE: # -------------- 20200419-022049 -------------- EDCORE: DCS/2.5.6.47224 (x86_64; Windows NT 10.0.17763) EDCORE: C:\Windows\SYSTEM32\VCRUNTIME140.dll EDCORE: # C0000005 ACCESS_VIOLATION at 63FC12DE 00:00000000 EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'chris' EDCORE: OS-Version: 10.0.17763 () 0x100-0x1 EDCORE: 0x00000000000012DE (VCRUNTIME140): memcmp + 0xEE EDCORE: 0x0000000000099BE5 (Effects2): ed::Random::genInt + 0x68955 EDCORE: 0x0000000000086D46 (Effects2): ed::Random::genInt + 0x55AB6 EDCORE: 0x00000000001068A7 (Visualizer): RenderParserImpl::DrawTransparentAll + 0x87 EDCORE: 0x000000000010C14C (Visualizer): RenderParserImpl::isEmpty + 0x4A3C EDCORE: 0x0000000000140E9B (Visualizer): smSceneManager::CreateSceneManager + 0x743B EDCORE: 0x00000000006E0E17 (DCS): woLA::loadNewInputLayout + 0x3064E7 EDCORE: 0x00000000006F1BE3 (DCS): dDispatcher::InitDatabase + 0xDBB3 EDCORE: 0x00000000006C8264 (DCS): woLA::loadNewInputLayout + 0x2ED934 EDCORE: 0x00000000006C8629 (DCS): woLA::loadNewInputLayout + 0x2EDCF9 EDCORE: 0x00000000016969F6 (DCS): AmdPowerXpressRequestHighPerformance + 0xB099F2 EDCORE: 0x00000000008AAB2E (DCS): uiAsyncNet::onGameStop + 0x67DCE EDCORE: 0x0000000000017974 (KERNEL32): BaseThreadInitThunk + 0x14 EDCORE: 0x000000000006A271 (ntdll): RtlUserThreadStart + 0x21 dcs.log-20200419-022049.zip dcs.log-20200418-090644.zip dcs.log-20200418-071917.zip

Had my UTC mk II Pro for about a year and 3 months now...still flawless!

I'm assuming you're going to re-use your current power supply? Is it 10 years old as well? Other than that, the build looks pretty solid, congrats in advance :) Edit: just read the supernova being relatively new...note to self...read the rest of the post after the link...lol!

Welcome to the forum and welcome to DCS World! A few more questions so more of the folks can help you out. It looks like you have specs that should be able to run DCS in high settings without these hiccups. Are you running any sort of overclock? Have you stressed tested these and are they stable? I ask because normally these cause hard-locks, and in some cases an overclock actually reduces game performance. Does this happen only on DCS? do you have other games installed? If you can post a screenshot of your settings as well?

In AceCombat probably...but the real A10C max is about 381 knots with a never exceed speed of about 450 knots. Try practicing to modulate your pulls on the stick to find the sweet spot on turns or pull-ups...I usually gradually pull till the horn and no further.

It remains "latched" when you have wings folded. Paddle switch to disable NWS completely and Pinkie switch again for regular NWS mode. It's always been this way since release irc.

What I did was I adjusted the Throttle curve to match the AB point when hitting the detent on the Warthog Throttles. Shift+Enter in-game will show control inputs indicator (Red Box), with a bar on the throttle indicating AB point. Not sure if anything changed since the last updates but that's how i got over this issue.

I see a new hotfix is about to be out, but doesn't say anything specific about the bindings being fixed.

They provide the smaller plate for the TM Warthog Joystick if you ask for it.

Wheelstand Pro Warthog Deluxe V2. http://wheelstandpro.com/products/wheel-stand-pro-for-thrustmaster-hotas-warthog-saitek-x-55-x52pro-x65---deluxe-v2- There's a center mount adapter too.

I'm also holding out to upgrading to 8th gen. I'm torn between pulling the trigger now or wait for the 10nm ones. P.S. I already bought the Rockit88 deliding tool and Thermal Grizzly Conductonaut. Planning to delid the current 6700k. If I bork it during the process, then on to the 8700k or 8086k.

This looks decent for the price your paying for it. It would have definitely rocked DCS World 1.5-2.0. For DCS 2.5 and OB, You can get away with 60 FPS in mixed settings on 1080p. The 980TI is no slouch, it was my main GPU till I had to RMA and it was replaced with a 1070. It had similar performance to the 1070 in most games. You should definitely OC the 4770k for more performance. You can upgrade Board, CPU and RAM later when budget allows.

Yes the 8086k is supported in the Z370 chipset boards.

I guess you forum handle was ominous. This is indeed "odd" lol! Have you tried a repair of the installation? In the start menu under DCS Open Beta, there should be a Repair DCS option.

I think it's some borked lua config files causing the issues. Specific to the F18C only apparently. Perhaps you can try clearing (rename or backup) the config files specific to the F18C in the Users\Your windows profile\Saved Games\DCSOpenBeta\Config folder? It'll load a default fresh one if it can't find it. Just be careful with the main folder as it keeps all your options and configurations including graphics settings and keybinds for other A/C.

Perhaps setting each category to default first? Then clearing and reassigning each? I just used Wag's profile for his TM Warthog on the F-18C and just did my personal preference changes from there. He posted his Warthog files on one of the posts in Controls sub section. Edit: Just to add, I don't think he used TARGET for these. Neither did I. and it works with no issues. I think the only things I changed is that he had the rudders and brakes mapped in the throttle. Which you can change to your preference.

I'm stumped as well. Does it only do this in the F18C? Do you have the A10C? If you do, try clearing the same and assigning in A10C, the rest of the buttons are mapped by default on the A10C with the TM Warthog (except the usual issue with all axis assign on every controller which need to be cleared out). If it works on the A10C, then there may be an issue with the profile you have for the F18C and perhaps may need to build it from scratch? (It's painful building from scratch but hey, at least it get's you flying).

Okay, one last thing I'm thinking. There's a section wherein the bindings assigned are for a specific aircraft. This is set for the aircraft you intend to fly correct? F-18C Sim? or Game? Edit: I see on the first screenshot you do have it in F-18C Sim. Only thing I can suggest at this point is to not run any TARGET Profile so it doesn't combine the throttle and joystick. How to you assign the axis? Do you double click on the line item under the column of the controller you wish to assign, then move the designated axis? or do you select from a drop-down list?

I set a deadzone and saturation, no curves. I set a deadzone of around 13-15 for both x and y axis, and set saturation to around 40. It's a trial and error phase. I just mirrored exactly how I had it as a slew on the A10C.

Okay, that's what the default issue for any input device. before you reinstall, try this. Under T-Rudder column, select a binding and click on clear category. This will clear any assignment on the T-Rudder. Then select axis, and manual bind your rudder and wheel brakes axis accordingly. You may need to invert the wheel brake axis (depends on the device, i had to invert on the crosswinds).

Are you using a TARGET Profile? Before moving to the Crosswinds I used to have the T-Rudder without issues. But I didn't use a TARGET profile nor did use the TARGET Software ever. I had separate columns for each device, Throttle, Joystick and T-Pedals. Some of the Axis may be named the same, but as long as it's the axis under the correct device column, it should work.

I just map what's intuitive and close to the switches of the real A/C. Say for the Hornet, the Upper Left Corner SYM switches to the A/A and A/G Modes and the Lower Left as Master Arm On/Off.

Difficult to diagnose without a track sir.