Bla-l29 Test Point
Catherine Rubeo
That would work perfectly if slew speed was updated everywhere. But it hasn't been - it has been updated in a single context of where TDC input is used. That makes a problem, because for many of us, it's just way too fast as-is.
Virtual CVW-8 - The mission of Virtual Carrier Air Wing EIGHT is to provide its members with an organization committed to presenting an authentic representation of U.S. Navy Carrier Air Wing operations in training and combat environments based on the real world experience of its real fighter pilots, air intercept controllers, airbosses, and many others.
In my mind the ideal solution from a user experience standpoint would be to have a series of sliders in the special options to adjust the TDC sensitivity on all formats:
HUD
ATTK
AZEL
SA
HSI
TPOD
GRID
Because although the new speed does make it easier to do things like bump ranging on the ATTK format, its going to be absolute hell to try and enter MGRS with it, at least unless you have a force transducer for your slew control. It seems that instead of trying to cater for all controllers and ending up with a one size fits none solution, ED should just let the player decide what they want, especially when it comes to issues like this that are wholly dependent on hardware being used.
This is a great suggestion. The pattern is already in there (with Realistic TDC Depress). It's clear, customizable, and should be a straight forward implementation. Tucked away under "Special", it won't clutter up the controls page nor require additional bindings. Each screen should simply multiply the slewing speed by whatever the user has set in there.
As neither the community nor ED (and to be honest probably not even 99% of real life Hornet pilots) know the relation in speed between different screens in the real aircraft, and we all have different hardware, it makes a lot of sense to leave it to the player to fine tune it.
I personally don't see the problem as long as you use an axis for the TDC since you can just change the curve and saturation as well as deadzone in the axis tune setting making it as slow as it was previously again.
Yes, they intended to do that, it's in the patch notes. Reason is a 2-years-ago request on F18 forum by some users, supported by 2 seconds of a Youtube video where cursor, on an unidentified BUNO and model of F18, slewed so fast, but you could not understand, by watching those 2 seconds, if radar was in test mode by ground crew (radar was turned off by simply slewing in the video, that's very suspicious) or if it was in actual working mode (I hope ED asked their SMEs for confirmation before the change).
Some users are now even asking to fasten FLIR and SA cursor too on F18 forum (request was moved in wishlist by Nineline).
I cannot fly anymore proficiently F18 due to this change and I am really furious this time with ED, because I support the team by buying a lot of modules and I would have appreciated a more reasonable and mature approach on this 'feature'.
Even if real slewing should be so fast (and it's an 'if', until an official statement about confirmation by SMEs), we are on a sim, not on real plane with real HOTAS, therefore we emulate the real thing with a limited hardware and not a lot of us own a top-tier 350$ throttle with sensitive hat-switch for slewing, so a custom slider for slewing speed would have been a more intelligent and inclusive customer-care solution by ED.
Saturation and curves on axis are not a real solution too, because you can indeed limit a bit the actual speed of cursor on radar by playing with them (I did it setting saturation to 60/100), but cursor moves like a turtle on SA and FLIR page then.
Besides, ED seems to have forgotten that they implemented TDC slewing by keyboard bindings too, so they let user theoretically slew by keyboard.
Well, I challenge ED's staff to slew by keyboard the cursor with the actual lightning speed.
Inviato dal mio BLA-L29 utilizzando Tapatalk
4) is the Maltese cross. If you see it all the time, you'd better turn on your radar, because it's off or SIL (or EMCON, but it's not implemented in DCS so far afaik). Or you are weight on wheels all the time and you never take off, which I hope not, you should enjoy this module in air, it's fun after all. (Coming back into topic, the plane in video could have been on ground and could be operated by ground crew for testing purposes, because bars were moving before Maltese cross appears on screen, so weight on wheels is a probable option).
Point is: ED is known to be overly cautious to reference to real documentation, then makes a change basing assumptions on two secs of a video, totally out of context because we do not know anything about Lot it was filmed on or contingent situation? Posting that video again by BN, in this thread, as a justification for changing slew rate in sim (change only partially made, because they did not change cursor speed in other pages) does not get me very comfortable, to be honest. I would have been really ok with a more articulated answer by staff, like "This is a video we were being aware of, we asked our SMEs/consultants about the slew rate, SMEs/consultants confirmed the video".
The maltese cross (indicating the radar is not emitting) was always there, but because of how cameras and CRT displays work, it appeared as if it wasn't there. Look at it again, pretty much all the symbology wasn't there until it quickly faded in. That is something often seen in videos of CRT monitors, including a lot of real life cockpit videos.
I see now, thanks. Point stands though: did ED ask its SMEs too before adjustinf slew rate or did they rely only on video (of an unknown Lot in unknown conditions)?
And, to sum it up after discussion, above all, are they going to at least accelerate cursor for all pages (SA, HUD, FLIR, etc.), so that everyone can easily customise curves on its own hardware once for all? Because I adjusted my curves to my hardware, radar is now again usable for me, but curves did adjust even for SA, FLIR, etc., making cursor slower than it should be, since faster slew rate was only applied to radar.
Inviato dal mio BLA-L29 utilizzando Tapatalk
That's a good news. Please, do this a customizable setting. Since the slew rate was increased, it is literally impossible for me to use the radar page with my low quality TM WH throttle's mini stick. An option for slew rate for different pages/systems would be needed.
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.
Why is the speed of the TDC not updated across the board? The SA page is still on the old speed. If they were all one speed it would be fine they can do lightning speed and you can modify the axes limits so that the speed is adjusted to your preference.
This way the extremes of the range will still enable the "original" faster speed for SA, while the inner shallower parts slows down the too fast cursor speed for the FCR for "fine" sorting, but you still can use range or azimuth bump by yanking TDC stick to the edge. Adjust the initial steepness ("center sensitivity") and the point of transition arc with the sliders as you see it fit for your own taste...
4a15465005