Galinette

Hi, I have a brand new WarBRD + Constellation Alpha grip. I am trying to define buttons from analog axis on the ministick. For this, in the VPC configuration tool, I go to the Axis menu, I check my ministick axis, they are # 3 and 4, named rX and rY, and respond well to movements on the full 0-100% range, centering around 50%. I double click on either axis, and tick a "Axis to button" checkbox, for instance 41-60% (button pressed around center). Click save and do the same for the other axis. Then I go to Button menu. On the lower right window, I get the message: So far so good. Now I define two logic buttons. Logical buttons 33 and 34 are unused on the above window, so I map them to the physical buttons 33 and 34. I let other parameters to default. Now they show up in the button mapping list. I click "SAVE VPC DEVICE" and everything is sent to the stick. This does not work : I can't get any button signal when moving the ministick across the boundaries. Now, if I create an axis to button mapping with the "global" method (the one which lets you create a maximum of 4 buttons globally, with custom ranges) on any axis, the ones defined previously magically work. Is this a software bug? Thanks

Do you have more info about this? Is this based on your knowledge of the real aircraft or past module behavior? Because it's behaving like that for a while.

Yes, it's the same

In APP mode, the IAS is positioned properly at mid-height so that it stays visible even with raised seat, this is perfect. However, as soon as wheels touch the runway, the HUD goes to ground mode, and the speed is re positioned to the top of the HUD. If your seat is raised, you can't see it. Raising the seat is very useful for landing, as otherwise your target AoA goes at the lower limit, or even sometimes below the visible part of the HUD. But as soon as you touch you can't see your speed which is a big problem. Your thoughts?

Hi, are you sure it has been reported since the last bugfix? Because until recently, the FPM was constrained horizontally. This had been reported numerous times and fixed recently. But, this has been fixed wrong and the horizontal drift is now totally erroneous with some roll (it seems correct with wings horizontal) To me this is a new bug since it's like this only since early october.

Radar boresight mode not working I never managed to get a single lock in radar boresight mode (3° cone). Even with an aircraft at close range, well visible in the center of the circle, nothing happens. As soon as I switch to horizontal, I immediately get a lock. The boresight mode would be very useful when you need to lock a specific target and there are several aircraft visible in front.

Thanks! That did it. Is TacView slowing down things on busy servers?

Hi, Recently I noticed that on a radar lock, there is no HUD square around target, until I switch to 530D. I have the feeling, without being 100% sure, that it wasn't the case before. Is it a new bug? Or is it the correct behavior, and a former bug that was fixed? Thanks!

+25

Hi, I have a single line, for SRS SimpleRadio, none for TacView. Which line should I add? Thanks!

On previous versions, the FPM was "caged", ie only moving vertically on the hud, not accounting for lateral drift. For instance, on rudder inputs, it was not moving horizontally. This was somewhat wrongly fixed recently. With wings horizontal, using the rudder does move the FPM left and right accordingly. But... roll 90° either side, use the rudder : FPM moves up and down Track file attached : uncaged-bug.trk

No, it was somewhat wrongly fixed. With wings horizontal, when using the rudder, HUD velocity vector moves from left to right as it should. Roll 90° either side, and use the rudder with wings vertical. Velocity vector doesn't move left and right, but up and down...

It's not a bug, it's a feature. Second hand aircraft

Hi, I have purchased TacView Standard. After installation, I have the TacView mod visible in DCS, recording is enabled, but after a flight session, I only get a 1kb file which contains some header but no actual data. I have looked in DCS logs, but there are no "Can't execute..." like error regarding lua scripts. How can I solve this? Another question, how is the "Premium Support" working? Is this forum only?

But does ED use mods or a customized engine for rendering its trailers? Trees are gorgeous on the official videos... See for instance the first shot in the video below:

Hi, On every DCS video I can find on youtube, the trees look great. When I try playing with all details set to high, they look ugly, rendered as a 3-plane billboard, until I get very close, and they look slightly better but still poor. Do everyone use graphics mods on youtube videos? Screenshot and settings are attached!

Hi, What are the recommended uses of the M2K jammer in DCS? Especially: Can it make the aircraft more detectable in some cases? What about "home on jamming" missiles, are they implemented in DCS? Do you activate it, before being detected? When detected/locked? After missile launch? Do you keep it on in combat, or use it in short "shots"? Thanks for your tips!

I tried again and it worked... strange. I confirm you don't need to overfly the point to do a perfect update. I maybe tried in A/G BF mode the first time.

In 2020, REC does not even compute/display any delta now. It seems impossible to update the INS. This makes AG bombing almost useless for small, hard to spot targets.

Also, until the bug is fixed, there shouldn't be a loadout preset with mixed weapons (BLG66 Heavy Support if remember right has BLG66+S530D)

Hi, I have a cheap USB numpad that I use in VR. I would like to associate a multi position selector from the Throttle (VIRPIL, not yet received), so that I can change what the numpad does on the fly (Such as M2KC INS numpad, views, frequency input, ...) Is there a simple way to do this? Thanks!

Ah, it seems this has been fixed recently! Now crosswind approaches are sooo easy :)

Well, if we couldn't bind any controls, and had to move the throttle and the stick using the mouse, I would say we miss a feature... The feature is here (radio channel & freq switches) but the inability to bind them is a bug...

What?? Mine was improper? :)

Everything is in the title : at startup, the tires are already blown up. This happens for instance with all "Instant Action" missions. I don't know if this is only a display issue, it seems the plane still rolls well. Screen capture with Caucasus Cold Start: