Muas

Thanks, exactly what I was looking for. Specially the link to that thread, and and how to cure that CCIP drift.

Setting a mission date prior to 24th Setember 1993, will get the Hornet a POS/INS navigation mode, as there will be no GPS assistance. Even if a full INS alignment is done on the ground, this will tend to degrade with time, raising navigation and computed weapon usage issues. Under these circunstances, how can we update our position in flight? I read about TACAN updates, but information on this is scarse... Anyone familiar with these procedures? Thanks.

Very well noted. Thanks, and keep up the awesome work.

The interior cockpit view falls back to the default camo uniform. Also doesn't load any patches as already pointed out in another thread. The helmet texture though, it does load correctly as per the texture pointed by Pilot_CH47_Helmet_Shell in the description.lua file. Meaning that pilot uniform and patches set in the descrition.lua file, will load in the exterior model, but not inside the cockpit, which at this point makes it kinda pointless to have different uniforms and patches to match liveries, then those not to display correctly inside the cockpit. This very same issue was already reported in the AH-64 Apache as being taken care of.

Just tried out this campaign and completed M01, truly amazed, as I'm mostly a multiplayer flyer. I'm not very used to the Litening TGP, as in the squadron I fly in we only use the ATFLIR, not too much of a difference, I'm sure the Litening would be more realistic in this theatre, but I prefer the ATFLIR to maintain proficiency to squad procedures. I might change it for the rest of the campaign (if allowed to) even though will discard one of the waist AMRAAMs. Thanks to @baltic_dragon for the devotion and commitement in putting something like this together. Top stuff, thanks.

Thanks for the trailing 0 tip, was trying with 00 at the end to no avail, also rouded up to 6 digit, spent almost all fuel searching, even though managed to complete the mission with 100 score, told lady FL I found the targets, but I didn't...

Winwing just fixed this. They do care about their customers after all. Thanks.

I managed to sort out in what circumstances I'm not able to delete keybind profiles and vibration profiles. If I download profiles, either keybinds or vibration profiles, I'm able to delete them. If I create a keybind profile myself (creating from game), these, they cannot be deleted. Also the vibration profiles, after I create one, or if I download and edit the settings, then it become undeletable. So the problem happens with user created files. The shared ones that can be downloaded, these can be deleted. The easiest way to replicate this behaviour is to download a vibration file, edit some setting, then save. After this, the "delete" option doesn't work anymore. If this is intentional, I don't understand the rationale. We end up with the UI cluttered with loads of useless profiles. Can anybody confirm this is the normal behaviour of the software? Thank you.

True, just that I've been talking to them for days... And me too I don't use profiles for keys, I also bind them ingame. It was the vibration profiles that got me to notice this. I ended up understanding how to tweak the shaker effect curves to my liking, but got 4 pages of useless profiles during the process... not really a big issue, but I would like to understand what is going on, that's it.

I wonder if anybody is facing this issue: I can't delete the profiles I created, either key binds or vibration profiles. I delete them but they stay on the list. Vibration profiles, every time I edit something, another profile is automatically created with a new serial number, if I try to delete the previous ones, they just don't disappear from the list. I believe it's because they get backed up at the cloud, but how can I delete them from there? I have like 3 or 4 pages of useless profiles on the UI... Got a ticket at Winwing, but no answer so far, any ideas?

I know that stock F-18C AAR mission with the Viking @322-323Kts, its a good example, and a very good training for I thing it's more difficut to tank from the Viking than from any other tanker. Somehow the aircraft gets too unstable close to the boom, probably because of the viking left engine. Anyway, a lot of precise adjustments with the throttle and that is why I like it a bit on the loose side. But anyway it's just a matter of practice, after a while we can even set altitude hold AP and autothrottle and get away with it. My problem is when I have to remove my hand fron the throttle to do something else, then the levers fall all the way up to AB detent, and it even disengages the autothrottle... that's the only thing that bothers me.

Speaking of SimApp vibration effect... anyone knows how to get rid of the unused profile files that keep adding up in the list?

Agree. I watched someone disassemble it in youtube and he didn't got to the friction collar, then I realised it's too much unscrewing and disconnecting, one might even spoil something during the process, so I quit the idea. Didn't get to that point yet, although I relieved the tension on mine, as I fly mostly the F-18, and tiny throttle adjustments are required all the time for formation, AAR, carrier landings, etc, so I need it pretty loose... WW should improve this with some kind of counterweight to the levers to balance it, I believe that would be the best.

Actualy, I do have that product, which I used successfully on other devices before, but I'm not sure how the Orion 2 levers works, I have never looked into its guts to check what's the friction materials, enough to give it a try... maybe someone around has done it before. Thanks for the tip.

My only issue with the Orion 2 base is that either I set a very high friction on the levers (I use F-15EX grip) or else they fall over to the front due to their weight. I have the finger lifts, but if I want a smoother effortless movement on the levers (low friction), I will have to keep my hand on it at all times, otherwise they will fall over. A counter weight should have been taken into account... any workaround for this? Thanks.