VIXEN413

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

Niiiice... Anything added at N35°42'28.4 E39°49'59.3? for reenactment missions...

Hey all, Love the jester pod so far but indeed, we would benefit from another additional slewing method. most of us have a TDC cursor on our throttles or sticks when we fly other jets. Those TDC are not used in the tomcat but we should make it usable to slew the pod, that could be awesome and easier then moving your head to hover an out of plan dot in a ring in your VR kit.... just an opinion...

hey all, thanks for your answers. What I wanted to say was that I was surprised, by following a taxiway center line, to find taxiway edge lights right on it while lining up 06. And that if there should be anything, it should indeed be some green leading light that you ll normally find on twy centerline... Usually, blue is for twy edges and green for twy centeline. Now, I checked on Jeppview and indeed, Nalchik does not have a lot of equipement and as you may find in a lot of old eastern countries airport, might just have the edge blue lights. Sorry for the misunderstanding. See ya all later, BR, Vixen

Hey all, following the centerline to reach the threshold of rwy 06, just in the turn for lineup, the centerline has twy blue edge lights on it. needs to be changed for the green recessed light BR

Hey guys, love Syria map... just did a night mission and came back to land in Ramat David and noticed the left papi was wrong. Papi logic should have the red lights on the inboard side (ie close to runway) white goes outboard. rwy 33 papis, were with red on left and white on right of the 4 lights I was on path with 2 reds and 2 whites and PAPI were giving me R. R. W. W [] R. R. W. W. instead of W. W. R. R [] R. R. W. W. gonna go check other fields now. lol BR...

Hi all, small prerequisite: I m running both Stable and OB version of DCS. I go MP with both versions and have applied same settings and options to both of them except that Stable is with all my maps and modules while OB is just Caucasus and the F14, f16 and f18. As I m flying in VR, I just do ONE tunning in the MDG_strokes_def lua, I reduce the thickness and fuzzyness otherwise my hud is a big green bloby thing... I never had issues with just changing those 2 values and it always passed integrity check on MP. The new OB seems not to like that and kick me out with the message "pure client required". So, is this a new thing, to have this quick edit not pass the IC or is it just something with new OB version? BR

Experienced the same issue while in GS yesterday... tought It was MP problem and took another slot. Indeed, when you go A/A whike the gearvis still in retraction, you will stay stuck in Nav head up symbology. Changing weapon does nothing to it. I tought it was strange cuz I setup my radar, Az/el etc on ground but go back to Nav for T/O. At the 3rd time I had it, I troubble shoot it and could reset the system by going out of A/A then back and recicling the Master arm (altough, like other are posting, only A/A reset seems to solve it)

Was that target jamming? I also had contacts with crazy mach numbers, and I guess that might be why the radar cant get a proper lock indeed.... Would be curious of the answer on this one...

Hi all, Would love to fly procedures on how to properly manage those 2 conditions... anybody can point me to the right direction? BR

Hey there, Few post mention ACM issues in any acm modes as "reported" now that Stable is updated as same version as OB, are these bugs fixed or were they just imported to stable? a Quick fix in the pipe anytime soon? BR

Thanks guys, you are confirming what I was thinking about this. The weather was crap (intentionally) and I had lost my target in IMC but I knew he was close that's why I went WACQ out of simplicity. Hence the use of ACM and the surprise not to be able to SOI the Flir.... Usually I lock him up in TWS or LTWS and then can SCS to the ATFLIR. As for the second part, yes, I think not being in A/A was creating an auto track like a ground movibg target and on the HSI, the MC was giving me the symbology like if I was Navigating towards a ground designated point. That's why I could not select WP, didnt had the symbology of the TACAN and steering line was moving based on the designated point iso the TAC... And that's why Undesignate cleared the issue So, to really use the ATFLIR for A/A work, better be in A/A as in NAV, the logic of the pod is the same as A/G Thanks guys...

was wondering too.. SAM is a viper thing, sort of their version of ltws..... maybe they got confused in the notes.... dunno

Hey everyone, Just noticed that if I fly in A/A mode with the master arm switch off, the weapon selected is "X" out on the hud as it should but not in the JHMCS where you just have 9X.. or AC.. not crossed. So no way to tell in the JHMCS the position of your master arm? Is that normal? BR

I saw the same behaviour and it kinda make sense since you are in ACM and the logic of that A/A mode take precedence over DDI sensors of interest. Same if U wanna go AMPCD SOI, you ll just enter VACQ... Thing is, if you are in ACM and lock a target, the Flir on left DDI Will go on him (L&S pointing) but no auto track will be done. the only way to get away from the ACM selection is to undesignate but that will send your pod to Rome unfortunatelly... So use ATFLIR in Radar mode not in ACM modes and U should be good...

Hey all, I came across 2 things that raised some questions about the ATFLIR in a simple SQ 7600 interception scenario. 1: I came close to the aircraft that I was rejoining for the intercept and wanted to get the pod on him for VID. As I was already close, I punched ACM modes and lock him up using WACQ. Now, I had the ATK rdr SOI on right ddi, and the flir on left ddi so how can I make the flir SOI? If I SCS left, the ACM goes back in WACQ search... I get the logic, it makes sense but then, going out of ACM needs undesignate and that sends the pod to Rome....Is there any way I can stay with the pod still looking where it was? Second strange thing: I just bring the pod on left ddi, rdr on right, make the flir SOI and all that without engaging A/A mode. I lock (auto trk) the rogue plane with the flir. All fine altough the pod is not in it's A/A logic but on the HSI (on ampcd), I cant change the Waypoints anymore and also cant get the position of the selected TCN, it disapears from my screen. I all comes back normal if I undesignate the flir lock... Is it normal behaviour or should pod lock and info not mess with my HSI symbology? BR

bump with more stuff and price update.

Hey all, Here are some issues we are experiencing and I think they might be related even if it looks like 2 separate bugs... Flying on private MP with a friend in a 2 ships formation over sea of Galilea at around 1500ft, he calls for an engine fire and plumets in the water... No random failure were set. Whike I m still going towards Haifa, we talk about this and he is sure he didnt do anything with controls or switches, we were just cruising and then suddentelly, same thing happens to me. Fire warning with loss of thrust, I try the autorotation but end up crashing on a hill side in the trees. Yesterday, Still the same 2 ship formation above Beirut, at around 500ft we do slow flight at around 40kts to enjoy the view and this sudden loss of power happens. I could recover 3 times but last time was fatal, too close to buildings... for him too. So we checked on double binding, no joy. It's like the throttle suddentelly goes half and we need to jerk it back in place. Collective was fine but both needles leading towards the yellow arc of the RPM when that happens. We are playing the last Stable version still. Anybody has a clue?

even more crazy, was ready to taxi on the growling pvp today. I had set my parameters on the attk rdr in TWS page and just activating NWS for taxi, radar locked a track 99.9nm 90deg off my position hahaha... really weird radar behaviour these days...

can reproduce too

did try it out too. Can reproduce as well on this mission where I mimic the 9x mission against 4 mig 29. I shake the plane on purpose and try to reproduce so dont mind the stupid ACM maneuvers but indeed, if you are applying any acceleration in any plan, the ACM mode locks totally out of direction and to 99Nm. If steady, you might get a proper lock. Tested VACQ and a bit of Bore. both with the 9x and gun. Totally reproductible. MP or SP Regards server-20210525-133552.trk

looking at this post plus the WPDSG ranging and Azimuth issues plus the bullseye issues... Smthing seems globally wrong with ranging and 3d geometry on the hornet...