wowbagger

Agreed, the topic of this thread is the adaptive brightness thing which has never worked as intended, or perhaps as 'wanted' by many players. It really needs to be made optional through some method.

That may be. I definitely had it behave, last week, as decribed in the original post of this thread: ie, the axes moving relative to the heading, up=away in direction of heading, while the map is oriented N up. I'll have to double check if it is consistant, or possibly user error (user error is easily achieved with this module).

Agreed. When the Hind was first released I started playing through Spring Tension using it. As I recall it mostly works without issue. I never finished because of real life distractions, now you've reminded me ... time to finish it.

Ya, I haven't clicked on that thing in years either. For those who haven't see it yet, Briefing Room is quite brilliant. Yes, it's one extra step outside of DCS itself, but the results are far better. If the quick mission generator could replicate Briefing Room .. well that would be the way to go in my opinion.

Lovely! This bird needs a lot more content. Thanks!

" ... good to see you guys. So glad you decided to join us. Over."

Even more annoying that the tourists can seem to manage it. Can't understand why this has been unaddressed for so long. It is game-breaking for so many missions and campaigns. There cannot possibly be a Dynamic Campaign of any kind without this very basic and frustrating aspect of the battlefield fixed. Can we not get this bumped up the list of priorities?

Now, if only the startup file wasn't encoded and was instead in a Macro_sequencies.lua which could tailored, like virtually every other module.

Year two bump.

Sorry ... that just sounds so funny, here on the DCS forums.

Fantastic, thanks!

The F1 is one of the very few modules that doesn't work with the vaicom kneeboard extension (the C-101 being another). It would be lovely to have it adapted to be able to work like most of the other modules. Cheers

Thanks for the thoughtful, honest reply. I appreciate you can't please everyone, and squeaky wheels .. etc. Recently, a couple of other campaign makers were asking why players seemed to have less interest in campaigns. I think there might too limited a view of what a dcs mission "should" be like - a lot of which is driven by some vocal players who don't necessarily appreciate that it's a game, is supposed to be fun and ought to be accessible, and can be enjoyed many different ways. Anyway, thanks, I appreciate your reply and the position you are in. Hope it works out in the best way. Cheers

Ya, this is a let down. There are some very vocal parts of the community which don't necessarily represent the majority. The multiplayers tend to be far more vocal than single players, and I think the cold start players are much louder about it than hot starters. There are so many cold start options. You can also just hit autostop and then start up as you like. I'm not saying that everything should be hot start, and there are times when I prefer cold start. But more and more I think about flying a mission, look at the clock, think about sitting through one more start up ..( I mean it's the same freakin thing, every freakin time) ... and often decide not to bother. The short, easy to get into the air aspect of this campaign was what made it stand out amongst the morass of Hornet campaigns. Shame.

Yes, that seems to be the answer. Will give a try next time I'm ship hunting.

Ya, that's my problem I know. Viggen vs ship requires overwhelming the defenses, but I am usually playing by myself ... and with regards to flying the Viggen, always playing by myself.

On the flip side, my RB-15's manage to penetrate the CIWS all the way to the ship ... ... almost never. I will try switching over to RB-04s.

So ... 'move more slowly'. Okay, thanks for the reply. The F1 is, overall, fantastic! Gorgeous inside, and tons of fun to fly.

Both the U/C safety lever - Open and the U/C safety lever - Close act to toggle the lever instead of simply opening / closing respectively.

I notice with the F1 that if I press buttons too quickly they don't register. As an example: On a toggle switch. Down (release) = master arm guard open Up = master arm on Up (release) = master arm off Down = master arm guard close If I switch the toggle from down to up, the first action (master arm guard open) works, but the second action (master arm on) fails to register. As another example: Flaps lever with three buttons on the axis. bottom = flaps extended middle = flaps half top = flaps retracted If I move the lever from bottom to top, the middle button (flaps half) registers, but the top (flaps retracted) does not. It only works if I move the lever quite slowly, but not if I employ it with what I consider a normal movement speed. A similar problem occurs with the gear lever (using simplified gear option). I haven't noticed this in any other module, it feels specific to this one. Any advice? (Don't say 'move more slowly' please.)

Kerbump, +1

Bump +1 This is desperately needed to be able to navigate in so many different circumstances.

Or word of the campaign ... or even a single non instant-action mission.

Just to add to this; because of this thread I decided to make the exact same change over the weekend. So far it seems very worth it. In Liberation/Retribution missions, it went from 50's to 120's (fps). I'm using it with a 3080ti and it seems to be constantly switching between cpu bound and gpu bound which is where I want it. (edit: this is pancake QHD) Thank to everyone for the advice.

Ya, unless it comes from Razbam, there's no way to do this that will ever pass IC. Best you can do is limit the number of them, from the EW page.