carcinomic

It makes me almost angry how long I've been trying to figure this out and missed something so obvious, THANK YOU. Per the version of Chuck's guide I had for ACLS, DLC deployment wasn't part of the steps listed, and it had worked prior to update-- but it was the ONE thing I was missing to not see AP CPLR after the update was implemented. Just tested it out and had a nice facepalm, but at least managed a decent 2 wire while enjoying my coffee. Cheers!

Ah, that's a bummer for me then. I seem to have everything set up, also have supercarrier... I hear ACLS lock on 6 miles out, fly mode 2, on AoA, glideslope, autothrottle, doing all radio comms. Autopilot is on, acl switch is back, TACAN, ICLS, ACLS and link 4 set up for carrier. landing chk lights up, ACL ready, AP/REF. but I never once see AP/CPLR at 3 miles out like I used to. following Chuck's guide to the T. what changed? I even have an old youtube video of it working so I'm really not sure.

Hey, so... From what I'd heard they're redoing the tomcat ACLS/landing through redoing the autopilot entirely... I can't even get AP CPLR to show up anymore. This being said I keep trying with the hornet. I usually get UTM fail. Pretty well versed in ME but this is acting very strangely, sometimes I can get ACL 1, sometimes it's UTM fail, ofc made sure to establish TACAN, Link 4, ICLS, and ACLS, everything put in correspondingly. But sometimes I can't even lock a TACAN signal in the Hornet? It's usually really straightforward... But yeah since whatever update-- any plane with automatic carrier landing hasn't been able to do so. I understand this is probably complicated as all and I might just be better off waiting for the next OB update, just wanted to feel out how many others are seeing the same thing. Rig for reference: i7-8700, 32GB DDR4, M.2 NVMe SSD, Oculus Rift, GTX1080Ti.

First of all thank you, this looks like it was a TON of work and I'm getting even better FPS in VR even in Syria, Marianas so that is definitely appreciated. RB75, RB05, hi or low drag bombs, and rockets all do what they should for the sake of instant action missions, flying around is a delight, radar doesn't even slow FPS, same with time compression; idk what you guys did in this regard, but yeah there was a HUGE increase in performance here so thank you. Running i7-8700, 32GB DDR4, 1080ti, Oculus Rift, NVMe M.2 SSD, and unless the map has a LOT going on I see a consistent 45 FPS/eye that I previously did not, with most settings turned up to max-- exceptions being MSAA at 2x, SSAA/SSLR/SSAO all off, clouds to standard, anisotropic filter at 8x, pixel density low at 1.1, preload radius at 50%, ground shadows to flat. Cons/Questions/What Happened?: I'm having major difficulty with waypoints (even clicking a waypoint button seems to direct back to landing from instant action or single missions, nothing loads from data carts on standard startup) as well as easy comms to AI wingmen, tower; do I need to press FR22 to do this now? I set mode A/G for tower, special channel 1 for wingmen but get no response now. But yeah everything else is great, just need waypoints working so I can play with RB04/RB15/BK90. Thank you again for your continued work on an excellent module!

I'm having issues with the TPOD as well, not just things being way harder to spot. I can't seem to laser-designate anything since the 2.5.1 update. There's always a glitchy-looking set of frames that vaguely display the laser code, and it flashes every half second or so. Entering in the correct laser code in LST mode doesn't seem to change this. Anyone else having this issue?

Thank you!! Your guides have been so helpful and have made me want to try so many new planes, I am so grateful you've taken the time to put them together!

Just checked your thread, that is REALLY weird. Your system specs posted in the other thread should suggest no issues here-- you've got more RAM and a better graphics card than I do, you're not running VR, you also mentioned using the lowest graphics settings possible and it still messed up. Is anything kinda stuttering before the freeze, is anything else running in the background? Wondering if this also has anything to do with Windows 7 vs. Windows 10? It's really hard to say! I managed to work past the issues I was having after talking with Heatblur on Facebook-- used DCS repair, reinstalled the AJS37 Module, then played with graphics settings a bit. I lowered terrain detail, water, preload radius (about 50%), and turned off shadows entirely. It was a system resource issue on my end for sure but I can't see that being the case for you. Temporary workaround-- have your wingmen do your dirty work, turn on and use that radar for VERY short periods of time, turn it off ASAP... If I think of anything else I'll post up. Sorry I could not be of more help!

I was looking through the log and this one struck me: 00036.415 ERROR WorldPlugIns: Failed to read serial number for 'AJS37' I have the receipt and the code was necessary to get this working anyway. Please let me know what I can do to troubleshoot or any progress working on this issue.

Slow down a bit, let your opponent stop turning so hard or wait for a second for them to change direction. Another suggestion is to "lead in" to your missile release, in other words aim slightly for where your opponent is heading, at the limits to which you can still get missile release tone. In general firing air to air is best when not in a turn, but the rules of engagement do not dictate this always being the case! One nice way to help is by using object labels-- it lets you know the exact distance for optimal weapons release based on how you fly your plane, in what kind of circumstance, etc.

I ran the DCS World Repair Utility and tried the same mission-- here's a much shorter log file. dcs.txt

Here you go! It was running alright for a while, then I tried that "Hunting the Hunter" mission, freeze before waypoint 3. dcstxtlog.txt

Hello, Didn't see anything related to this particular issue so I thought I'd ask here. AJS-37 Viggen seems to have trouble working as soon as I turn on the radar, for example about to use an RB04 in ANF mode. Most aspects of this module work with no issue-- free flight is fine, navigation works fine, rockets and unguided weapons work fine, the RB75 collimated sight works fine, air to air combat is fine, mission builder is almost no issue but for some reason the game crashes any time I turn on the radar to search for ships. I'm using Windows 10, AMD Phenom X4 @ 3.39 GHz, HDD, 8 gb ram, NVIDIA GTX 970 and Oculus Rift VR. No other modules I have seem to have any issues at all (FC3, F-5, A-10C, Mirage 2000C, MiG-21bis) but this one crashes every time. Kind of sucks because I really want to play some anti-ship missions! It works like 20% of the time but usually the game just crashes. Anyone have any advice?

So this has been a really helpful thread. I'm obsessed with this method now, it was such a pain trying to control the F-15C on the ground using brakes, rudder, and a prayer. I did it enough to know how at least... :doh: The takeaway I got from this-- -watch your speed (160-180 kts), rate of descent/AoA (20+), -try to keep your nose around 5 degrees above horizon line, but your velocity vector on the start of the runway no more than 5 degrees below the horizon line, -flare appropriately/apply airbrakes/cut throttle at the right place and time, -let back tires land first, hold the stick up so your elevators contribute to air resistance, flaps are more useful on approach than here -never push your nose up more than 10-13 degrees above horizon until around 100 kts before bringing the nose gear down gently and pumping the brakes until a stop. above 15 degrees results in damage. -More payload, more forward power but stay below 200 kts, lower your approach altitude so there's minimal impact on landing. This is a really cool way to be gentle about landing, and the best part-- have directional control of the aircraft on touchdown which was the biggest issue on my end. Now I can manage a clean landing with a busted tire. Speaking of which, anyone know how/why the F-15C's tires just pop on takeoff sometimes? Or why sometimes it seems really difficult to just keep the F-15C going straight down the runway?