Art-J

I think for now they're dependent on each F-4 skin. SEA ones for example yield helmet painted in green and brown camo. I guess we'll have to wait for upcoming pilot customization feature to be finished and implemented in order to change helmets independently of skins (unless it's possible to switch them now via some custom description.lua editing....)

Are you asking if E-shop will allow you to buy it when you don't have the map installed yet? I'm not sure, though I can't see why it wouldn't. You can always install the map as a trial first and then purchase the campaign to play it. The game doesn't care how you got the map as long as it's installed and authorized correctly. Just remember that you'll have two weeks to complete the campaign which sounds like a lot but might actually be not enough for more detailed and complex campaigns.

As per manual, this is where screens from tape recorder and (upcoming) gun camera will go. Not sure yet about Jester folder though.

He's talking about quite unique for this module modelling of virtual stick forces vs stick displacement, which works as intended with physical FFB joysticks but yields partially non-realistic results with non-FFB ones. A couple of guys went full drama-queen mode about it and don't feel like flying the plane because of it. Ironically, it's an offtopic part of this discussion if you want to read, albeit devs don't plan to rework it anyway, not now at least. https://forum.dcs.world/topic/349269-force-feedback-settings-discussion/ Edit: Mike offered a more thorough explanation on the issue here: https://forum.dcs.world/topic/349348-suggestion-spring-joystick-control/

It might require a tweak in the sumulation, as the manual linked to here... https://forum.dcs.world/topic/349516-spoolup-time-of-j79-engines-too-quick/ ...suggests 3 seconds from 65 to 100% while it seems "our" Phantom spools up even faster. Still, 3 seconds is mighty impressive!

It's there in manual allright, just in earlier phase - Pre-start -> before inspection -> pilot -> step 21 (page 734 in current pdf version).

Apparently you cannot, that's the point. Only offset it somewaht by disabling "blending" in special options. That being said, DCS Bf-109 was using similar approach for first few years after release ("forces" vs displacement simulation of virtual stick movement by non-FFB joysticks) and we were taking off, shooting things down and landing it anyway. So maybe it is a question of getting used to. Time will tell.

So we've got one opinion that repair command fixes the cumualtive damage and one that it doesn't . Never used it in multiplayer but I'm curious now which version is correct then. Logic suggests it should be the former. In either case one just needs to remember that cumulative damage simulation is a thing in DCS and bumping into the limit reduces that limit on each subsequent application.

Some guys had this problem yesterday indeed. You can get around it by forcing the module installation manually, using relevant command in powershell window. Check out his thread for instructions:

Ha! Thanks, clicking elsewhere seems to do the trick indeed. Might be not a bad idea to mention it in this "frequently asked issues" thread you're working on

Keep in mind that the whole "early project announcement" thing, which resulted in a sudden flood of planned modules mentioned in newsletters last year, was encouraged and done by ED in order to avoid developement effort duplication (which already happened in DCS in the past). So, yeah, 3rd parties tend to announce projects that are still years away from completion just to "book" certain aircraft or map before someone else does it or to avoid wasting time on something already started by other party.

I'm still at manual reading and cockpit familiarization stage - love the embedded manual concept in itself! Its initial implementaion has some issues here and there it seems. All default keybinds ("M", open, close, toggle) work correctly... as long as I don't start actually browsing and reading the pages . Then they stop working completely. Looks like I can only "reset" them by hitting Esc key twice (to bring up DCS pause screen and close it), then they start working once again. Mouse seems to be OK all the time, clicking, scrolling, dragging, resizing and whatnot, no issues here. Having to spam Esc key frequently to make binds work is not a big problem really, but I figured I'd mention it, 'cause I'm using the maunal a lot now . P.S. - for the record, I didn't tweak UI res override, or any other special option, they're all stock for now. I'm also a pancake user, at 1440p, Win 10.

Folder structure looks allright in both your screenshots. You probably have some old custom mod in there which interferes with Heatblur's product. A VSN one perhaps? Do the usual thing, get rid of any flyable custom mods, run a repair command, see what happens then.

Dzięki za poradnik, oj przyda się .

A shot in the dark, but have you checked if your game/simplified flight mode hasn't reset itself to ON after an update? It shouldn't, but it's known for making trims inop in any module.

I don't own these maps an my update was about 30 gigs. Keep in mind the F-4 skins alone are 13 gigs and you're downloading them no matter if you own the plane or not.

If you don't mind using so-so quality custom mods, there's an old one from Hawkeye available somewhere in the mods section, and it includes He-111 and Ju-87 If I recall correctly. No idea if it's still compatible with 2.9.4, though. EDIT - there it is:

You haven't missed anything, as noone said it. Some folks just ass-ume that today's scheduled would-be release hour automatically applies to tomorrow as well. No, it doesn't, albeit we all hope the patch shows up sooner rather than later.

I'd like to remind that in early days of the whole kerfuffle some Russian members of ED top brass were arguing on the Russian part of the forum (where more info is often available compared to English one) that taking over and developing the Eagle was not their problem/business as they considered ED to be more of a distribution platform rather than producer for this particular piece of software. There was a link to that thread posted either here on one of previous pages, or in one of the other threads, not gonna waste time looking for it again. I didn't check what the final conclusion was. In either case, in worst scenario, if solution isn't found and RAZBAM calls it quits, it doesn't seem like ED is going to rush to "save" the Eagle, Harrier and Mirage or if they even have capability (source codes) to do so. As for any EA preorder, there's never and wil never be a guarantee that product is going to be worked on. The only certain thing is a hefty pre-order discount and If you consider it to be a good deal even for incomplete product, buy it (as I did with F-4), if not, don't buy it. It's your money and your risk management.

To be fair, modules not getting a single fix or feature for months or more than a year are not unusual even on ED side (Yak-52, Combined Arms, ex-Belsimtek ones, Supercarrier etc.) so one never knows what and if is really "maintained" in DCS ecosystem and such disclaimer cannot and will not be shown on e-shop website unless the company literally goes belly up like VEAO. As long as RAZBAM stays afloat and in some form of business relationship with ED, their products will most likely remain available for purchase even if their effective development and maintenance is questionable after lead systems programmer leaving the company. Still, that will just put Eagle on the same level as Yak for example, so not eligible for refunds (EULA or not) as it is not "abandoned" in theory, just stalled in further development.

@talvikko I'd suggest using OvGME (or any other mod manager) to disable and enable that edited file with just a few clicks whenever DCS update comes. It's less annoying than editing it everytime after it gets restored.

Some guys got them, some haven't yet. Orders which include vinyls seem to be taking longer to ship. More comments here:

Yes, I believe Pete means total as shown on percentage slider in the mission editor. I seem to recall about 68'ish % means full wing tanks and empty fuselage one, but could be wrong. Frankly, for your training purposes, even that 60 is way more than you practically need, 'cause there are no WWII maps in DCS currently that would allow Mustang to really stretch its legs.

^ Nah, It's VSN mod only, but for Navy enthusiasts that will have to suffice for now.

Isn't it related to combination of special options and mission settings after one of the patches years ago? More details at the end if this thread: