Sawyer

I see most of the interesting weapons have been removed from the FAQ. I do wonder how that wasn't nailed down a week ago, but it is now, apparently.

I've always maintained that I'd happily have a "best guess" over nothing at all. I'm never going to fly an F-35, so I won't know the difference!

I had similar issues with the tanker, the boom remained in the up position, and the refuelling complete prompt on the right hand side disappeared with the sound of a radio clicking.

Because you've chosen to play a simulator?

I bought the Yak 52 in August 2018, 2140 days ago. Any chance of a major update or is it just abandonware at this point? $39.99 isn't small change.

I'm really enjoying it, but yes it does need a little work. I'd like to see some improvement to visual fidelity, although it really doesn't impact my enjoyment. The flight model is a little weird when pushed outside of "normal" parameters and the damage model is a little janky, but I'm sure these updates will come. I'm glad we've got a fully featured module release, I don't mind the price and given the updates the Gazelle got, I'm sure KW will get regular fixes.

Introduced new module: DCS: OH-58D Kiowa Warrior by Polychop Simulations Nice. I take it this will be available on the store imminently? Unfortunate that we are again without strike eagle updates.

Alright then. Not confusing. A bit illogical is probably a better description.

I must've missed something? Does this mean they can't exist on the latest and greatest WW2 map? Slightly confusing state of affairs if that's the case.

Biggin Hill airport was an incredibly important RAF Station and whilst I appreciate it was effectively abandoned from June to September 1944, after that it resumed fighter operations. Biggin "on the bump" would be great to see in the map!

Yeah I really don't get this. I do hope the plan is to merge, as Biggin Hill is a huge omission in my opinion.

I just move the pod onto target as you've described, then use "Designate" under Utility.

Well I had it working briefly, but every single time I restart my PC it has the exact same issue again. I have to disable it and then scan for hardware about 30 times over (No exaggeration) until it works. Anyone got ANY suggestions for a more consistent connection?

I'm getting the right hump with my UFC now. I've had it plugged in via powered hub and it was just cycling on and off indefinitely. As in, I went and had dinner, came back and it was still cycling. I've played around with windows settings so windows doesn't automatically turn off USB devices and it still does the same. I plugged it directly into my PC and had the same issue, I've then gone back and plugged it back into my USB hub and now it isn't even cycling on and off. Plugging it back into the PC once more gets it to cycle. I'm about ready to lob this thing across the room Now plugged back into the USB hub and I have it cycling again... I'm going to leave it overnight and see if it sorts itself out. Any other ideas would be welcome.

Thank you BIGNEWY. I had a play around, and it would appear I can't run the game on high textures anymore. I am fully up to date with drivers for my 980ti and windows.

Still crashing... C++ runtime error thrown up now. Good to see I'm getting some support! xD

# -------------- 20191004-221333 -------------- DCS/2.5.5.36986 (x86_64; Windows NT 10.0.18362) C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll # C0000005 ACCESS_VIOLATION at F13AD7B6 00:00000000 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: 'adamj' OS-Version: 10.0.18362 () 0x100-0x1 0x000000000000D7B6 (dx11backend): (function-name not available) + 0x0 0x0000000000015D25 (dx11backend): (function-name not available) + 0x0 0x0000000000003389 (GraphicsCore): enlight::TerrainShadows::operator= + 0xDD9 0x000000000001412D (GraphicsCore): deferredShading::DeferredComposer::init + 0x9DD 0x0000000000077D9D (Visualizer): smCamera_Implement::SetProjBounds + 0x4C8D 0x0000000000078209 (Visualizer): smCamera_Implement::SetProjBounds + 0x50F9 0x000000000007AD35 (Visualizer): smCamera_Implement::SetProjBounds + 0x7C25 0x0000000000574FDE (DCS): (function-name not available) + 0x0 0x00000000005635FB (DCS): (function-name not available) + 0x0 0x00000000000673EA (edCore): Common::FSM::sendOutputSymbol_ + 0x4A 0x0000000000067389 (edCore): Common::FSM::enterToState_ + 0x79 0x0000000000067239 (edCore): Common::FSM::onSymbol_ + 0x1A9 0x0000000000574143 (DCS): (function-name not available) + 0x0 0x0000000000547544 (DCS): (function-name not available) + 0x0 0x00000000001BB5FF (DCS): (function-name not available) + 0x0 0x0000000000728EB6 (DCS): (function-name not available) + 0x0 0x0000000000017BD4 (KERNEL32): BaseThreadInitThunk + 0x14 0x000000000006CEE1 (ntdll): RtlUserThreadStart + 0x21 Happens in stable too. Any mission at all. Incredibly frustrating, I've completed a clean reinstall too. crashlogs.rar

Please. I don't ask for much!

Nowhere near enough public data for that.

I've gotta admit, I was so excited for this, and now I'm getting more and more concerned and less and less likely to buy it. I'm also not a fan of the post being quietly edited, one day before the pre launch starts. Doesn't exactly seem transparent.

Got my order in, #2013. Excitement is real. Roll on Julyish! That and the MFD's will be a huge quality of life upgrade!