All Activity

I see you already tried repairs. Try to open the options.lua and set the launcher to 0 to prevent it from opening. If DCS then starts, try another repair. EDIT: One more thing, try to delete the _download folder, and try a repair again. Can you show us the exclusions in your AV?

Some of us are slow readers, so please give us access to the manual a good bit of time in advance so we can actually fly when it releases. Please. (full disclosure, I'm actually a fast reader, but claiming to be a slow reader makes a better argument in favour of this )

OK, just deleted it now in the savegame\DCS folder and still getting the DLL errors, so I don't think it's even getting to the launcher step For some more context: The failure point is during the "Verifying Installed Files" phase. I've done the sqlite file - No change I've deleted (.OLD'd) the DCS folder in saved games too - No change

If you're using the launcher, there is a sqlite file I think that's been causing people issues. Do a search and you can likely find out what one it is and deleting it has solved some problems. I disabled the launcher as soon as it came out so I haven't paid enough attention to remember what the file is.

Likely you were using the Stennis carrier. It's "non-supercarrier" so has never had the full new deck crew. It used to have original deck crew but that was removed until ED can figure out how to have the original crew on it but the new crew on the others, so currently it has no crew at all.

Thanks Rob, good point. Yeah I have it excluded, I also checked quarantine logs and nothing from DCS was captured in there. I have a horrible feeling I'll be DLing the whole game again

That is a good point that the actual MFD displays also don't need SimAppPro (they're just an extension of your windows desktop being displayed).

1st thing to check/do is an exclusion from your anti-virus for DCS folders, then try a SLOW repair because your AV has probably quarantined some files. If you can't get it to run a repair try restoring the files from in your AV.

What an horrid thing about the imgur in the UK. My quota is done on the forum, so I can't put images here. That website, regardless of its first page content, was really easy to make images shareable. @HC_Official Thanks for the heads up. An excuse can be just that, an excuse. The means to do evil in disguise.

Depends. If you want lights and stuff that needs telemetry from the sim, yes. Just like Thrustmaster etc. For just buttons and axis that use Direct Input, no. You don't even need need the WW software to configure the MFDs. You can edit the monitor.lua yourself, or even have Helios make it for you. And Helios does not need to run for exports to work, only if you are using a Helios profile profile which needs telemetry for the instruments. Cheers! Edit: Sniped by my buddy @rob10!

Hi all, I currently have the following symptoms: On launching DCS.exe I receive the following errors; GraphicsVista.DLL is not designed to run on Windows etc Weather.DLL same message DTC_manager.DLL same message Launcher does not open. I tried to manually run DCS_Updater and perform a 'slow check'. This runs until approx halfway through the process and the repairer closes without messaging and then the launcher opens. On trying to open the the game, repair or update it fails halfway through and opens the launcher. So I am a little unsure how to progress. I can't run the game, I can't repair the game and I can't update the game. Apart from redownloading the whole game again (Oh god I hope not. It's almost 1TB on disk!) does anyone have some things to explore first that I'm missing? Thanks folks

Depends what you're running. For controllers like stick, MFD buttons, throttle you don't need it to run for inputs. HOWEVER, for the lighting of A-A, A-G buttons to sync with DCS or for the UFC to actually display info from the game you do need SimAppPro running. Although I agree it's not the greatest software, generally it doesn't cause a lot of issues.

Is Winwing software required to be running in order to use their peripherals? I've only had experience with VKB and Virpil. The beauty about both is that all settings are uploaded directly into the devices themselves, so there's no software that's needed - thus no incompatibilities. I was under the impression that Winwing operated the same - but maybe I'm wrong. Does Winwing require software to be running in order for it to work? Is that why there's a conflict? (Otherwise, if not - I'm very curious to know how winwing could create problems with DCS running as administrator if they have no software running at all - it should just be like any other generic device)? What's going on there?

Haha true. I’d love to be able to ask someone who flew the real jet

My sound is glitching as well in the F4E. It doesn't seem to be related to the speed brake since it starts a soon as I load into the aircraft even with the engine off. I tried reinstalling but didn't make a difference.

Brother, we would need wind tunnel to figure this out

If this is even going to be possible. I hope so!

Yeah, and you're not alone. But I think the lights are baked into the textures, (no real lighting in other words), hence why you can't turn them off until "lights out" textures are available or they make them actual lights. All lighting that do not cast light on the ground/other objects are textures. Long standing wish in the community is to blow up power stations with the relevant effects. Cheers!

Hi, Loving the campaign so far! After taking out the MiG-23s, I get instructions of 060, 20, low flying enemy planes. I turned 060, however, could not find the bandits. I assume these are BRA calls. I also tried to find them via Bogey Dope, but at that point I got a picture clean response. Looking at tacview, seems like the enemy aircraft was more like 090 at the time of the call, and I missed them by around 7 nm. I'm not sure if you have any control of that call or that's a prerecorded voiceover, just letting you know it's hard to spot them. It did not affect my mission score at all, but I had a spare AIM-9 left at the end Attached is the tacview FYI. Have a good one! Tacview-20251001-175055-DCS.zip.acmi

Ill put a reminder there about the winchester call.

Thanks for the explanation. I won’t say I’ve fully digested it yet lol, but I have a better understanding of the other factors involved. Edit to add: it’s a bit mindblowing to think, not only of the interplay of the different parts of the control architecture, but of how that interplay changes in different flight regimes. It’s quite an orchestra that aerospace engineers are putting together!

If the left aileron going up reduced drag more than the right aileron going to neutral, you should still see adverse yaw id think. Think about it. The left wing would see less drag than the right wing, thus wanting to move forward more. That would give a right yawing force. But then you have to think about the parasite drag from the left aileron sticking up into the airstream. That would cause some drag on the left wing. But even when making full stick deflections you see proverse yaw. And in that situation the upward going wing sees the aileron move down below neutral. I have thought about the stabilators movement during rolls possibly causing the proverse yaw. That very much could be it. And because its text and things are lost, I’m not trying to argue or anything! Just having a nice conversation! In case that wasn’t clear

Haven't flown 2.0 yet, but... just turn SAS off and you'll be living the life. A program manager I worked with who was a UH-60 Maintenance Test pilot once told me "The Black Hawk is the helicopter for helicopter pilots who suck at flying helicopters - until something breaks". If SAS is screwed up or there's something wrong in the mixing box, you're gonna work haaaaarrrdddddd.

Is this more clear for you?

Or fly above 100 kmh when shooting