Spetz

Sorry about that..I'm not at home right now or would post a screenie.. In the ME, when you place an asset, you have the symbol buttons that are for flight planning, load-out, waypoint action, radio freq's and failures (more or less depending on airframe). If you set the KC-130 up for "Tanker" and "Activate TACAN" via the 2nd button (waypoint options) and change from TACAN 1X to anything else, it does not actually change the TACAN frequency leaving it on 1X. Below this on the very bottom you have the tab button that is labeled "(Advanced) Waypoint Actions". When you drop a KC-130 on the map, the "Tanker" and "Activate TACAN" are automatically populated in this area, with the default 1X for TACAN. from what I see, and the issue that I was having was that I was adding and adjusting the options via the top symbol button, but it was getting over-ridden by the bottom "(Advanced) Waypoint Actions" tab, so when I set it to 16X above, it defaulted to 1X below, and only read that information. Hence, nothing ingame for 16X, but received signal for 1X. If I adjusted settings on the bottom section only, all changes were reflected in game and everything worked. Really hope this explains this better....

Ok, figured out the issue. Thanks for the mission so I can see how you had it set up. From what I see, if you use the ME small button for advance waypoint options vice the "Advanced Waypoint Options" tab on the bottom, everything you put in via the smaller button is overwritten by the larger one and doesn't work. Tested on all maps and works fine. Cheers

Thanks. I'll test the mission tonight. It's strange that it's not working for me. I even noticed that the bearing in the top left corner to the TACAN on the MPCD is displayed before I even turn TACAN on via the UFC. So I get it straight... Press TCN on UFC, Press ON ("ON" displayed), enter TCN # + ENT, Select TCN on MPCD, Ensure both T/R and AA (ODU 1 &3) are active with ":" and it should work. I've tried it airborne and on the ground. The only time I get a proper TACAN signal is if it is on 1X, not any other TACAN number. If your .miz doesn't work for me I will record a trk and submit it.

I run the desktop resolution the smallest possible with VR. I figure it might add an FPS or two as VR doesn't care what the desktop res is set to. And never had my mouse cursor go outside of it unless I alt-tab to do it.

If I set the KC-130 TACAN to anything but the default 1X, TCN mode will not pick it up. This is for Causcasus map, not tested in NTTR or Normandy yet. For example, in the attached mission, TACAN is set to 13X. Enter it via UFC, select TCN mode and nothing. Change it to the default 1 (despite setting it in the ME as 13) and it works as it should. MOOSE LUA and RAT script is installed for this mission but same results without it. CAU_AV8B Refuelling Practice MOOSE.miz

I'll do it when home from work but I deleted them after they didn't work. Regardless, I'll fire two together for both maps in question, test and post if required. Anyone have a basic working one they can post so I can use it as a basis just in case?

**** Solved**** SEE POST 6 BELOW.

Back to the original questions..... the Mirage was my go to jet for ages but just picked up the Harrier four days ago and can't see myself letting this one sit at all. Loads of fun. Hopefully we get as good a quality manual as we did for the Mirage..hint hint...

I just wish we had the option to remove the doors on all the variants.. :(

And still nothing yet.. Unless it's like my old army days where we would put netting across the windows when parked to reduce glare...

Sounds great using externals, but didn't notice any change when in cockpit. I turned down the "World" sounds a bit, perhaps I have to crank them to hear the difference inside?

That looks great! Keep at it!

Ctrl + Z.....:) Actually, I don't believe there is anything you can do to change clients passage of time in multiplayer.

Thanks! Will DL once home.. After I fix my rift.........

Same, no issues on 391.01 for me.

AlaskanGrizzly's last past was a month ago, is he not supporting this anymore? Anyone know?

Exactly.. Western doctrine and policy is considerably different than both Chinese and Russian regarding new platforms and IOC/FOC status. It is likely that Russia brought them over to do some system tests and give it that "Combat Proven" check mark in light of the PLAAF getting it's J-20A's. Syria is a low threat air environment and the perfect place to conduct some testing and possible weapons trials in the short few days they were deployed.

I would do a repair of your DCS install and then unzip KBB again and run it. If there was anything changed during the repair you will have a folder called _backups or _downloads...something to that effect in the root DCS folder, it'll be the first new folder in the DCS directory anyway..

Or perhaps it's for Russia to be able to market the aircraft as "combat certified" for export? Perhaps it was for of the Defense of the Fatherland celebrations? Perhaps it's in reaction the the PLAAF getting it's J-20A? Just because it flew to Syria for a few days doesn't mean it's now IOC, and just because it's not IOC, doesn't mean it can't forward deploy.

Just read through the last 60ish pages after a fast search. This may be already implemented, but does KBB offer the ability to add pilot body kneeboards as seen on the Mirage 2000 pilot to other pilot bodies that don't have them? Does it offer the ability to modify those pilot body kneeboards already ingame? I like to have freq's / TACANS etc available just by looking down in VR instead of opening the kneeboard and flipping pages. Apologize if it's already been answered, but I didn't see it, only the original unanswered questions pertaining to it.

As much as I would enjoy having NVG's, I don't have any issues piloting the M2K in zero vis/complete blackout conditions. You just have to keep a good eye on the horizon line and altitude, staying above the mountains. Oh, and make sure your pressure altitude is set to your runway altitude (zero feet) on departure so you don't descend to fast on landing :)

https://forums.eagle.ru/showpost.php?p=1590249&postcount=21 Try this..

Looking directly at the gauges etc in VR without direct sunlight there is no reduction in visibility. When you notice the gauge glass / AoA indicator going opaque and the finger prints etc on the radar screen is, for me, when sunlight is traveling across the cockpit while turning. It, IMHO, makes them a lot more real then full visibility all the time despite direct sunlight etc. That said, they are never to the point where you can't read the gauges (so far). Try it out, you can always remove it.

Thanks for the improvement. Finally started the updated campaign last night and although not as visible in VR due to resolution, it does add to the "realness" of the cockpit. I made it into a new JGSME mod and it worked perfectly.

I updated to 390.xx the other day using DDU. First instance of DCS refused to show anything but black in the headset, but looking on the monitor is was tracking as it should. Redid the install using DDU and it has worked fine since. No decrease in FPS noted. Specs below :)