raus

Hi all, must say I am loving the last updates and their added functionality. However, I have realized on my last two MP flights that the datalink came and go on HMD: I could always see the rest of my flight on the SA page, but sometimes the HMD overlay for my flight lead was not there (and we were in formation, so not fsr away). Also, at times, the symbols were not superimposed to the other planes, rather shifted by some distance, and „floating“ in open air... am I the only one experiencing this? Is it normal/my mistake?

Would be nice if we only needed one set of „page back/page fwd“ keybinds... i did not yet test the extension, and I am thinking on which keys to use :music_whistling:

Any news?? :fear:

Hi! I have resumed work on a small custom tool to generate my kneeboards and I am successfully parsing the .miz files and extracting info. However, I cannot convert the x,y coordinates of Bullseye or waypoints into latitude, longitude. I know they represent meters from the map origin, I know where each map origin is located... but I do not find the right formula. I have read that the maps in DCS are flat, so the real world formulas do not help here. If I try to extrapolate the location of a known point, it does not match for other points... I think there are some lua functions doing this, but they only work from the Sim, and this is mostly an offline app, requiring only the .miz file... does anyone have the source of these lua functions? Or does anyone know what the conversion formula is? Thanks!!!

Wouldn't it be great to have the first page list revisited?? We enter the last quarter of the year, and a lot of the features scheduled for 2020 are either [WIP] or not even started, according to that. I know the list is not 100% up to date (things like Markpoints, AGR are done...). So maybe, it could be good just to re-arrange the list, in an estimated order of completion, to know which of those [WIP] should be expected earlier, and what could be at risk of slipping into 2021 (no complains, I understand it can happen, and I'd better know what is at risk than realizing too late). @BIGNEWY @NineLine do you think you could draw attention on this, to get some info spread, eventually? Thanks!

Thx!!! You are, indeed, right :) Just made the test and it works. I was being misled by HSI ondications after setting the 4 harpoons up. BR

Hi all, Been recently playing with the Harpoon against a single Molniya. I wanted to launch my 4 Harpoons and get each of them arriving from a diferent angle, so I configured 4 Waypoints around the boat, and used them as HPTP for each missile, and then adjusted the final bearing from the HPTP to the boat. The problem is that all 4 missiles got the last HPTP entered. Is this so? Or is it a bug? Can we only have one HPTP at a time, for any harpoon? PS: btw, it took all 4 missiles to sink the boat. If only one was downed, then it would not be enough :O

Price adjusted to 180€, shipping can be combined with the joystick grip I also have for sale :)

Price adjusted to 100€

Hi, I am just wondering if anybody has disassembled the start panel. I guess it means just unscrewing all the M4 allen screws, right? If anybody did already open it, I'd love to see some pics of the internals... I am just thinking if it would be possible to replace the panel face with custom ones (split per panel) and maybe move a couple of the switches then... Thanks!!

Buyer could not proceed, due to other compromises, so still for sale

Buyer could not proceed, due to other compromises, so still for sale

Hi, I am selling my Warthog grip (A-10/F-16). Just tested for working condition, but never used, as I purchased the F/A-18C grip from Thrustmaster. The grip is completely new and I would ship it in the original packing from the Warthog. The joystick base is NOT included (I use it for my Hornet grip). Asking 150€, shipping within Europe included (need to check prices for other shipping destinations)

SOLD

Just add a deadzone to the axis. I went into „Tune axis“ in DCS settings and set a deadzone of 10. That fixed the TGP usage (previously would be zoomed all the way in, unöes I was holding it constantly). I hope that is what you were explaining, as the fix is really simple ;)

@dobroDude I am really interested in this, as I am just about to buy a Warthog throttle with the intention to mod it as much as possible into a Hornet one (fingerlifts, antenna elev control...). If you gave up on this, I would like to know which problems you did find. And if you have a plan for the scratch build, I would gladly help (I am a HW engineer, and can help with all electronic design, mechanical setup is what would cause me headaches here )

I don't think it has anything to do with the gun at all, if you think about it, the Hornet has a center mounted gun, so having a backup reticule on a side would be less than optimal, wouldn't it? As a matter of fact, I was in the Hornet HUD repair workshop at an airbase some 15 years ago, and was told that mark was used to determine proper seat height, so the pilot raises/lowers the seat until both reticules overlap, and then he is seating at the right height to see the HUD symbols overlapping real world counterparts (I hope my explanation sounds right...) Regarding the JHMCS part, I don'T know if it plays a role in calibrating it or not, but the mark has been on Hornet HUDs since long before JHMCs existed, and it is in place on Hornets that never got it, as well. Just my 2 cents

I am using an Oculus Rift S and a RTX2060. I‘ve tried experimenting with DCS PD settings and Oculus Tray Tool Super Sampling. I had some improvement, but I lack sharpness on the MFDs, no matter what I do. Everything else seems quite ok, but there‘s still this blutriness to text that spoils the fun :(

Just as the title says, the current fonts are hard to read without really leaning in/zooming, specially on VR. Not sure if this is the way it is in the real jet. Nevertheless, I (and I hope more ppl) would appreciate an option to have a VR-optimized font: maybe thinner, maybe one or two points bigger, so that we can properly read information like contacts altitude on the FCR page without needing to magnify it :) Of course, this could be offered as an option either in the VR menu, or in the special settings for the module, so there is a choice.

I would agree with OP. Makes it really frustrating, specially flying in VR, and having to lean to read the MFDs, makes me feel like a grandpa :( I cannot believe it would be so in RL, although I haven‘t been in a real F-16 cockpit

As per the title, I have a stock Cougar HOTAS, in very good condition (all switches working, mini joystick on throttle as well, etc) with very little use. I also offer a set of Cougar MFDs with less than 10 hours use. Everything works perfectly, and is offered with the original manuals. For the HOTAS, I also have the original packaging, although I don't have the original box of the MFDs. If you are interested, please PM me a serious offer. Thanks!

Hi, I am a little confused: on HUD, I get a bearing/distance indication to Bullseye, from ownship. But on the MFDs I get exactly the same (lower left corner of MFDs)... while I was expecting to have there the Bullseye bearing/distance of my radar cursor location... of course this comes from previous experience outside DCS. If my assumption is wrong, how can I get the bullseye info of where my radar is looking at? I find that quite useful when getting Bullseye coords from AWACS. If this is just a WiP because of Early Access... fine, I would just like to know :) Thanks!!

Bumping this up: still have those two frames. If nobody is interested will probably fit some HW to them and make them functional... but not having much time for that right now.

According to the Early Access manual, should be callibrated airspeed, and I made sure my HUD speed was also callibrated:

Hi, Sorry if this was already asked/clarified, but did not find it. I was practicing AAR, and locked the tanker in STT from distance to get its speed and closure rate. Closure rate seems ok, but the speed showed to be 390kcas???? I did then check the mission details (F-16 instant action - aar) and it said the tanker would fly 270 knots which I verified to be true in the end...but my radar keeps fooling me. Am I doing something wrong? Adding to the offense, the tanker tells me it is at angels 23 when in fact it is flying angels 25... so all in all my first approach was a disaster: flying too fast and low until I was near the tanker and then a festival of overcorrections :( On a different topic...is NCTR implemented (non cooperative target recognition)?