maxTRX

Don't quote me on that one but I think the elevation for O/S, if left blank, would be automatically entered by MC when within ranging limits. I have no idea whether DCS models it this way or any other way. The 'other' sim did. Anyways, I don't think this would work with SLAMER's. As far as continuing from O/S, idk

I'm not sure how this works in the real Hornet but it would make sense to exit ACM back to whatever setup and mode was active before entering ACM. Currently, it follows the same behavior as switching between RWS and TWS. Say your RWS was 'SET' to 4bar/80az. Switching to TWS the bar setting is maintained and the az. narrows to 40. Going back to RWS will not bring back the previously set parameters. It carries over TWS settings. Whatever SME's and the devs do with this is up to them. If they decide to keep it this way it would be nice to hear the confirmation of 'correct as is' and perhaps why this mech is followed... no essays, just a quick explanation. For now, at least for me, the best way to return the radar to 'SET' condition is by cycling the weapons switch. So, If during the BVR fight I ended up in TWS (4b/40az, 10nm range) and want to go back quickly to RWS (4b/80az, 40nm range - preset with 'SET') I have to switch the radar to RWS before cycling the weapons. If I had Amraams selected initially and I wanted to cycle the radar to preset format for Amraams, I would push the switch to heaters then back to Amraams. Just pressing the Amraams won't do. In my view, that's not the proper mech in the real thing but... it's a band-aid for now and I can do it quick. Forgot to mention: one of my 4-way switches on my WH is programmed for pushing some important OSB's on the right DDI (common for radar), TWS/RWS is one of them . Gotta do what'ya gotta do.

I've seen the HACQ behavior you described, except I couldn't see what the heck was the radar locking as the mode was entered. The second attempt would acquire the correct target.

I wasn't even aware of this bug since I always exit ACM (except guns) by pressing 'Undesignate' button and the fastest way to get back to your pre-configured setup for RWS for any weapon is by cycling weapons select switch to that weapon. If ACM was entered from TWS, this method will bring you back to TWS with Az/bars and PRF previously set.

I'm happy with it. I also run it on 3070 (in a desktop tho') in full res. at 90Hz, no AA in game. Smooth enough even on Syrian map but... I've only been playing SP so far. FPS... eh, it's hanging in there but no stuttering and no crashes whatsoever. I can make a bet if I played online the results would probably be mixed. As far as SA goes, there is TIR and other gadgets that can give you equal or better SA. For me it's 3D that makes a world of difference and once I get my my hands on some decent interface and I can use my fingers to push in-cockpit buttons and flip switches... I'm all set

Hehe, you know... one thing (thread) at a time.

, anyways I'm glad you reported this and it lands on some priority list.

Another bug to list? I was wondering about this issue when tinkering with HACQ yesterday. Topper's option 'c' makes sense. I guess getting back to 'SIL' from ACM wouldn't really matter... the neighborhood knows you're there once you entered ACM scenario.

Got it, Thanks Yes, I actually saw 'something' at the extreme edges of my peripheral when twisting my head left and right. With my current FOV in Reverb G2 it is impossible to use and... I'm not pulling G's so the normal cue is fine. Just have to be careful not to strain my back when twisting and pushing off arm rests, hehe.

The radar is buggy too... (too funny...)

It looks like it's always enabled even with Amraam selected. When I 'enabled' it with SCS down with Aim9X selected, I could see 'Uplook' across HMD but no change in behavior. The reticle was always moving up at a faster rate then my head, which does help a bit. Since I've never seen how the real uplook works, I'm assuming this feature is there already... except it's always on in HACQ/LACQ. I was using VR.

The radar was in HACQ mode from the start of the vid and circle or no circle, the HACQ mode should have no restrictions. The entire implementation of HUD masking sucks... in my view. I'm sure many would agree.

Ok, finally got it sorted out. The Litening pod: When first turned on it defaults to 'VVSLV' boxed and it seems like that's a requirement for the pod to automatically slave to radar when L&S is designated in any mode. Fine, the nuisance is that whenever radar designation is broken, the 'VVSLV' option comes back unboxed, so if the pod slave to radar is needed, we have to box the 'VVSLV' again before radar lock or box 'RRSLV' after the L&S is present. In ATFLIR, the 'L&S' slave is boxed by default and it remains boxed after the L&S designation disappears.

Just to make sure... SCS forward forces AGR and takes the computer out of the selection loop? You can go back to computer controlled ranging by pressing 'Undesig.' (will also undesignate your target if designated) or SCS toward the radar page.

The HUD masking... again. On top of the the main issue that is easy to spot, there seems to be a slight dead zone around the HUD, where the radar will not acquire. I selected HACQ for my HMD and flying in a slight offset toward the target I pointed the HMD aiming cross (the circle is not visible in the transition area around the HUD) at the target and nothin happened, so... it looks like in order for the HMD to take over I needed to offset my flightpath more. Not a big deal. I was just wondering if the real Hornet ignores the area around the HUD

I only had enough time to do one test. I wanted to see in what type of acquisition would slave the Tpod to AA radar automatically. I know I've seen this happen before but not on this flight. In this test I locked the target in STT and the pod did not slave. It showed 'RRSLV' option which I selected and the pod snapped to the target. It's usually more useful to have the pod locked in point track so that's what I did. I merged with the low flying bomber, turned around and settled above him and sent him a Fox2. The pod tracked fine. I've only seen tracking issues with a very fast turning targets, as in a gunzo fight. It'll track but it gets very jumpy. Another question popped up after the bomber I was intercepting crashed. The pod seemed to be stuck in the direction of the crash indefinitely. I double clicked 'Undesignate' button on my stick and the pod changed to snow plow? That's what it looked like to me. Another double click and nothing happened. I had to press 'VVSLV' to make the pod follow VV. That's probably a bug. Short clip: On a side note: Did anyone notice the new 'flaming aerial wreckage' effects? I can't get enough of blasting stuff out of the sky now. A little consolation for all these bugs in the recent OB.

You don't need to go ACM if you're joining up for an VID. Within 8nm or so, switch priority to FLIR and PTRK the bogey while still maintaining the radar lock (TWS is fine) I find it very helpful in this kind of scenario, especially with HMD on. Should you loose your radar lock for whatever reason, the FLIR will stay on, even when banking and putting the target in the blind spot or you had to re-position above and even in front of the bogey, the FLIR should re-acquire easily. If you do go ACM you can still change sensor priority by pushing TDC button on FLIR DDI. If you just want to work with FLIR, reset the radar and stay on FLIR DDI. When you box VVSL, with or without the reticle, just point the VV on HUD and PTRK. That's the way I do it... currently

I was also thinking along these lines. The list of fixes was just too long and I was getting hyped to go and see for myself but I didn't get that far

There are serious issues in the latest OB update. One of them is WPDSG with Tpod (either one) The first time you designate, everything seems OK. Pull some G's or undesignate then try to re-designate the waypoint and things get out of whack. It's already been reported so I won't bore you with details. MavF slaved to Tpod... in my opinion behaves like the whole system was designed by people that didn't feel like finishing the code... if that's the way it works in RW. My view might be too simplistic but if I designed this handoff thing, the mech. would go like this: Designate the target with whatever, the Tpod is tracking, priority to MavF, Uncage - all Mavs go slave mode and are following Tpod, not locked on anything. Priority back to Tpod and stay there. In range and the MavF locked on 'correct' contrast- the firing solution pops up and Rifle. Next MavF online and looking at the same target. Your priority is still on Tpod, slew and re-designate, the Mavs follow... repeat. Easy and intuitive. Without the pod... Uncage the MavF's and slew them to target or line up the target in the HUD with Mav's triangle - uncage (all Mavs) slew, F/C (well, if possible) or let the Mav snap on the target, in range - Rifle. The next Mav is already looking on the scene... NOT boresight. If you want boresight - cage... Am I an oddball or what, hehe.

I was just wondering how are the beta testers tasked. Do they just jump on whatever they wish to test or are they given specific areas to work on? I'm hoping that each tester is given a priority to test specific areas assigned to them, immediately notify 'someone' if problems are encountered then they can feel free to 'play around' with any other aspects of the game. The last OB update really got me edgy... to say the least. The first day or two I played with SLAM-ER's and things were going fine, it was somethin new and it was WORKING Then today, it was time to play with both Tpods and Mavs and I was disgusted. It's all out of whack. Same with A/A radar, w/o going into specifics. I checked the bug forum for the Hornet and it seems like some players spotted some of these game breaking bugs so, that part is good. Well, I'll just shoot SLAMERs and do carrier ops for the next...

In the Hornet, when landing on a runway make sure your antiskid is on. Even in no wind condition the steering usually starts acting a bit crazy when slowing down. With antiskid on, no problems whatsoever... as long as your rudder and brakes are properly programmed.

I tried PP once (via waypoints) and it worked. Since this was a test, I also had waypoints located over the targets just in case and I'm glad I did... My mission editor was set for MGRS grid and that was the format for my targets. In cockpit, I didn't see an option to input MGRS into SLAMER's memory, so... I had to select 'data' on my HSI, box 'precision', change to 'LATLN SEC' for lat/lon format, then copy the WPT data from the waypoint collocated with the target... . I didn't have the DL pod loaded and watched the missile from external view. It worked fine. As I was writing this, 'jppsx' posted above mentioning altitude for TOO. Definitely the altitude is required for any type of targeting.

OK, so altitude control works but to live up to my call sign I have to b***h about other things: terminal flight profile not working and the SLAMER setup is 'weird' if precise altitudes need to be programmed. If that's the way it's done in RW... Here's a short clip of flying SEAD for my own SLAMER's

All right , I guess my problem was as usual with me... trying to do too many things at a time. In all my tests I was loaded with 4 SLAM-ER's and tried to get them all ready and pre-configured before getting to my launch point. I could swear though I tried to setup the wpts then alt. for each of them without touching anything else. Apparently I goofed somewhere. The mech. is definitely weird but it works and I was able to get all missiles behave the way I wanted them to behave. Something funny happened to one of my missiles as I was doing minor adjustments on my DL screen. It was flying above water at 200 ft. and had about 12 nm to go when I decided to change my target to a different building. I boxed force corelate and initially slewing worked great, then I must've pushed on my TDC too much and the missile tumbled, hehe. I quickly switched to F6 view and sure as hell the missile went out of control and into the drink. Anyways, I'm slowly getting the handle on this weapon.

My 'realistic TDC' is always unchecked since I use a WH and DL cursor is working fine. Box 'F/C' if you want to designate any point in the view, otherwise the cursor jumps between objects/shapes.