VIXEN413

I found a hardware fix that I m happy with... up to you guys to try if u like it. As I said, the real TDC in the jet is an OTTO force sensing ministick. Apply a little bit of pressure to a direction and the cursor will move slowly but apply a lot of force, your cursor will run like in the video above. Most of our throttle have ALPS ministick (just like playstation sticks) that are based on angle to provide a deflection. They have short arm and lots of angle so it's mega easy to overcontrol them. With previous TDC speed I realised I was almost always bumping them to full deflection witch is not the way it should be. So on my winwing tdc ministick, I set the curves to 0 then popped out the cap to place a roundel of foam underneath. I had to find the right thickness so that the cap would meet resistance while moving. took me 2' but you can take out that cap super easy... It allows for good smooth movements near the center for more precise work and, by applying more force, you can still get the fast cursor speeds. It's also closer to the feeling offered by a force sensing ministick... For Virpil throttle, the cap is different so you ll need a different way to place some orings... hope it helps

in the Hornet, the throttle grips are made by Mason industries and use OTTO switches allround. the TDC is a non moving (or barelly moving) force sensing ministick (look for it, U can buy it on Mouser for 750USD). Now, the way it works by registering force applied giving as a result a cursor speed movement makes sense for the sensitivity U have from such a device. U can be precise like that. TDC on Virpil (CM 2and 3), winwing f18 throttle or also Thrustmaster mod for the tdc will all use ministick like the ones U find on xboxes where, due to the deflection and moment arm, it is very difficult to be precise around the center and you will overcontrol almost everytime... That's why this change has made Cursor operation on our hotas way more difficult... the speed and sensitivity of the TDC now in game does not fit with harware on sale for home sim use... I worked around the issue by using 60-70% curves on those axes to slow it down near the center to keep a bit more dexterity but even then it's harder the it used to be... the real fix is the 750$ OTTO ministick... Right...

Hey there, as per title, It seems I cant get the ddi buttons to animate when I click on them. AMPCD buttons works great but DDI pb dont move anymore when pressed. On the UFC, all buttons move when clicked except the I/P button (but action is registered in the control assignment) Anyone else noticed this behaviour? Same in OB ST or MT... BR

True that but even if it plays with bigger angle and more bars, it is still a reduced scan volume... should not take that much to complete a full swipe of the area, no? can any SME give their thaughts on this? BR

Hey there, I think the fact that I can get an ACM lock earlier or later depends on target track generation and it is linked with the bug discussed here as well about how the mission computer generates those tracks. first recorded game track I got WACQ lock at around 3Nm and on the second one just around 8Nm. Dunno, it seemed inconsistant today in general. I noticed that, usually when I recommit after a skate or abort, the hafus are dissappearing then reappearing on the ATK RDR and just as they reappear, I guess the mission computer regenerates the track and then I can get a WACQ or ACM lock. By the time, the 10NM mark is past for a while. Irony is that I have a tally way before it gets me an ACM lock... late WACQ.trk late WACQ2.trk

Noticed that WACQ does lock stuff up only around 6-7 Nm... was it not supposed to be able to do the job on a fighter sized pkane up to 10Nm? BR

Hey there. Yes, I do fire the HARM but only after I do the reset of the A/G mode. look at the bezel of the left DDI after I release the JSOW I try to change the weapon from J82 to HARM or RT by pressing pb7 and 8 but nothing happens, you see on the screen the button clicking physically but the page is stuck. on this track, I try many times before finally resetting A/G and then I m able to select HARM weapon page and fire them

Hey there Bignewy, Thanks for looking at it. Indeed, I just setup a quick mission but still had one unit from the high digit sam mod. I ve redone it with SA11 BUK so you ll see what I mean. So again, same deal, a 360° to setup the JSOW (still with the target elevation issue as mentioned in another bug report too) and an ingress to target, popup and release all 4 JSOW, I roll inverted then back in normal flight towards the SAM site. At this point my stores page is still in the JSOW sub page and when I try to click on PB7 or PB8 for HARm or RT, the page does not change. Either by using the mouse or with my DDI button. I need to recycle A/G mode to "unbrick" the stores page.. Hope you can view the trk now and see what I mean. Thanks Best regards stuck.stores.page.trk

Here are 2 tracks showing the issues. I ve quickly redone the mission with ingame standard sa10 iso the high digit sam. First track is extracted from flight in VR so that might not be the easiest to check but the second one will show the issue too. On both tracks, I start with a wide 360 to setup the JSOW and can reproduce the elevation bug when WP designate (it's also part of another bug report). Then I proceed to ingress, popup and release the glidebombs and I want to click to the HARM or RT weapon on button 7 and 8 and nothing happens. I m using MFD's and the input on the bezel is registered as you see the button clicking on the screen, same if I use the mouse to click on it. Workaround as you can see is to get out of A/G then back in and then click on button7 for the HARM (I later get teh Pullback message on hud so I know technically, I dont need to acces the page to shoot it in SP but all this is prior hud messagel. SA10.trk stuckstorepage.bug.trk

got a chance to test it again, and indeed, the bug present itself each time you edit a WP elevation in FT and then designate/undesignate that WP for weapon useage (in this case a JSOW). It seems to divide the altitude by 3 each time, just like if it was a conversion feet to meters. Also, when you have a WP set with an elevation in feet, upon designation, it shows in the "mission" sub page of the JSOW/JDAM but converted as meters. It should indicate feet there as well IIRC. If the WP elev is in feet, it feed the mission page in feet and if in Meters, it feeds it in meters. But now, it looks like any WP, with it's elev either in Ft or M, when designated, will be converted in meters in the JSOW mission sub page and if you send over an altitude in feet, it divides it by 3 to convert in meters.... Work around is to work in Meters only but still, annoying bug lol tgt.deg.alti.bug.trk

looks similar to the issue I reported in the JSOW bug, related of designating/undesignating...

Thanks for having a look at it. I llbe home sunday. will try it out again and hopefully, make a track of this since I could repeat the issue 2-3 times... I ll try again with the mission I have, targeting SA12 (high digit SAM mod for this miz) but I ll check too with ingame SA10 to see if that mod did not create the issue.... wich I doubt since The issue is just while doing a setup of standard armament in the hornet... BR

Hello, I ve been trying to kill a SAM site with JSOW and HARMS and ran trough some issues. There might be few multiple aspects to the bug but essentially, it was all while doing the same flight. I ll try to make a track ASAP but I m away from home now. My run begins with an airstart (for this test at least), low altitude and 35Nm from the SAM site, msked by a mountain ridge. WP0 is the spawn, WP1 is the Target location. 1: setup of JSOW. Master Arm, A/G selected, go to store page, I select the JSOW, the timing start, I set it up the way I want, Go TOO for pylon8 (with 2 bombs then step to pylon2(2 bombs as well) to go TOO. Tgt dsg on WP1, ah, I need to change the target altitude as WP1 has an overfly alt. I do this for Pylon8 but have to do it again for pylon2. I type again the alt (2900ft inthid case) and bam, he shows 2000 on screen. I do it again, still, does not take the correct altitude that I inputed. I deselect and WP1, edit the WP, it works, Designate it again as TGT, again, wrong altitude on the mission part of JSOW store page. each time I undes redes, the system cuts the altitude of the target by 2.... very stange behaviour. Eventually, it worked by undesignate, edit once more the correct alt in WP then redesignate and it was finally ok. 2: Running in, pop up attack from behind the ridge, I release them all 4, and on store page, I click on button 7 to open the HARM page but nothing happens. Same if I click button8 to select the RT I had on center pylon... all other DDI buttons are also inop and I need to get out of A/G then back in to unbrick the store page and select HARM in SP... Not ideal situation as I already had the telegraph poles flying towards me.... Seems there is smthing wrong with the JSOW (and probably JDAM too) Will try to post a track when back from work. Anybody experienced the same behaviour? Best regards

Here we go, made a small track. Could replicate each time. In the track, you see me going on MIDS contacts from ATTK RDR to AZ/EL and altitude shown are not the same at all. At some point, the lead contact is picked up by onboard sensors and shows 25 but then contact is lost and his alt on AZ/EL reverts to 36 while still showing 25 on the radar... BR azel.alt.issue.trk

I ll try again but could not have a track last time... will see. Thing is, wherever your radar is pointing, speed and angels of a MIDS contact are given by donnors. If I leave my cursor on such a contact on SA or RDR, the alt stays the same if that contact does not change it's altitude. on AZ/EL, even when leaving the cursor on a contact flying at a fixed altitude, the value changes witch does not make sense. And also, adjusting the radar scan volume on that contact should not change anything because the altitude is just given by donor (not corelated by onboard sensors).... What puzzles me is that I have a certain altitude on RDR and SA but a different one (erroneous) on AZ/EL

Hey all, came up to an issue today, Had a group, 4 ship in front of me, A/A mode engaged, AZ/EL page on left ddi, ATTK rdr on right ddi and SA on AMPCD. going from a screen to another with castle switch, with TUC, SA and Rdr show same hostile (in this case) altitude but AZ/EL gives me different altitude for the contact... on the AZ/EL screen, even if visualy, the 4 hafus were at different altitude, they all showed 36, witch was the alt of the highest contact...

The vid raises a few questions too... D/L UFC options, shows link4 options but how to get the other MIDS info page with VocA and VocB? does a second press on D/L does the trick or is the link 4 options comming if ILS is selected on and MIDS option coles on D/L press if ILS is off? Also, are the voice message from approach frequency and ownship definitive or are we gonna get some updates there too? if flying Mode 1 or 1A, ball call should state also "coupled" in the call, no? BR

yes. it's working fine and as intended. also the bumpt to other screen function works fine. BR

set a deadzone of 2 or 3 for your cursor in axis X and Z as explained in another post, this solved the issue...

Hi all. For all of you that have the cursor getting frozen when touching the sides or swapping screens, the solution is easy: SET AXIS DEADZONE TO 2 OR 3. Totally solved it. I realised, back a few months ago, I had the same issue with the hornet with the MGRS grid, after upgrading my hardware to a winwing ST throttle. My TDC could not click because the ministick is so precise, it was still registering a movement and was not enabeling the depress function. This happens with high sensibility ministick like on my winwing or on CM2/CM3 or PS4 controller. The Warthog seemed less prone to that issue but if you encounter that problem, in anycase, give it a deadband... BR

Hey there, Right, I guess that one is on me. I tested last stable too and had same behaviour so I guess nothing changed. On my rig I have 2 DDI so I usually press PB on the sides of the screen to make my selections but while doing the test yesterday, I didnt connect all the USB of my rig and used the TDC over margin to changes settings, Something I usually never do. That must have got me... need more sleep I guess.. BR

I dont know, Radar manual states that the cursor of TDC can be use to select a value by depressing it and releasing it. The rest of the sentence does not explicitly states that the cursor will park itself back in upper left corner... and since both behaviors have been seen on different patches, I would like to know if this was a correction in behaviour or a glitch created by the update. I experience cursor issues with the apache and was wondering if there would be any correlation too. BR

Hey all, It seems I have some issues with the cursor stopping functioning at some point with the Apache so I tested rapidelly the hornet cursor on the radar and noticed a change. Atk rdr, if I go with the cursor on the margin to a value in front of a PB, I can depress the cursor to change the value (for ex, bars, azimuth, RWS/TWS swap, range arrows...) We use to click what we needed and then move the cursor away from there but now, after we depress the cursor, he goes upper left corner, for any items you change... It use to do it for the swap between TWS and RWS but not the rest. confirm the logic changed? Best regards

Same for me. I can bind the x and z axis of the hocas cursor and see it moving in the control setup so I know the binding is fine. once in the cockpit, I can move the cursor but if it touches the side of the screen, it becomes frozen and I cant move it anymore. I swap the cursor to the other screen where it appears in the middle but still cant move it around with the cursor hat. I press cursor enter, screen swap again and again and still no joy despite having correct input sensing in the axis setup... other modules cursor works fine still but hornet cursor has a different way of moving then before too. I ll repport in hornet bugs.

Hey Urga, hey guys, Was walking around in Protaras and Capo Greco Cyprus yesterday, first time back since 2-3 years altough I m in Cyprus often for work... Went to a viewpoint and noticed that they took away the antennas that used to be there and also the tip of the cape is open to civ public. Might wanna consider taking the antennas away from there too... Also, buildings are growing like mushrooms in Limassol... soon will be time to add those big structures lol