Ogata_Rina

Basically if you use TDC to select 4 bar in RWS, it will automatically switch to 40 degree, and selecting 6 bar will switch it to 20 degree, as TWS requires. Selecting scan bars with MFD push button do not have this bug, as shown in the start of the track. According to the popular radar reference manual, this shouldn't be a limitation. hotas_scan_bar_bug.trk

It's been a month, any update? Honestly MSI is a core functionality of our hornet lot 20 so I hope it’s a priority.

Disabled Process Lasso, reinstalled driver, disabled XMP (which is stable in every other game and memory test), and I'm still able to recreate this bug. It's probably a driver issue, but it's not a priority by any means, no one should even considering using motion blur in VR lol. I just coincidentally found the problem since I was running my desktop setup in VR. Obviously I would not run DCS with default DDR5 clock, so I will just turn off motion blur for now. A really really really easy fix for this bug is just to force motion blur off in VR. Seriously no one should even consider using motion blur in VR. dcs.log-20250406-113427.zip

Got the same problem with motion blur causes 100% game crash in VR. CPU: 14700k at Intel default setting GPU: RTX-5090 Stock clock stock VRAM RAM: 64GB 6400MT/s CL32 VR: Pimax Crystal Light at 0.9 render quality dcs.log-20250404-051222.zip

GS is very dynamic, so try to make your fight 2v1 or 1v1 by cranking (hornet radar have 70 degrees horizontal gimbal, you can comfortably maintain 60 degree radar track). GS bandits will usually keep their nose on you, so you can kinda predictably drag them out of other enemies. Almost everything will have a kinetic advantage to you, so don't support missile until active for the initial shot. After first shot trade, it's very important to spot the other guy first. Practice your radar mech, know which mode you should be in, practice using hotas, practice some of the "hornet tricks" like saving radar modes with different weapons, clear radar screen by switching to GUNS and switch back, SPOT mode on MSI tracks, etc. Unlike any other aircraft (other than JF17), you can't outrun your opponent. Inside 10 miles with no friendly near by, you're better off trying to kill the pursuing bandit than turning cold. Don't be afraid to merge, but make sure you do your heater gameplan (idle/no AB when you don't have tally, pre-flare when you're spiked and no joy), and don't pull the paddle and lose all your energy. Most importantly, carry at most 6 amraams, remove pylons that you don't need, unload to quickly accelerate, loft your missiles.

reduced the ghostingon the scan line by quite a bit. New DLSS still can't perfectly draw a solid scan line but much better than old DLSS and no ghosting.

First screenshot is with new transformer model, second one is with old CNN model

Well if they're gonna merge with the prev thread go for it, otherwise consider this as a 1yr bump.

1. When commanding AACQ from RWS with a valid trackfile (radar has existing azimuth and elevation data for that target), the auto acquisition scan center is sometimes completely off from the target. From the track that I provided, when I play it back, sometimes the AACQ acquisition scan volume would be completely centered around the trackfile, and sometimes it would be either offset from up or down, indicating incorrect elevation setting. 2. When commanding TWS from STT with the DDI pushbutton, sometimes TWS Auto scan center would be completely off the target either up or down. Quoting from latest F/A-18 Early Access Guide EN (Page 174): Looks like in TWS Auto it should be automatically centered on L+S target or target centroid. This behavior is currently very inconsistent, and sometimes the scan centroid will place the target right at the edge of the scan center when there are no other targets present, causing it to lose track inconsistently when the radar contact itself is solid. Anyway, track is attached. Notice scan center is inconsistent after commanding STT or commanding TWS from STT. When I commanded TWS for the last time inside 40 miles, the scan center placed the trackfile on the top the scan volume, causing it to lose track after I shot the AIM120. This defeats the purpose of TWS Auto in the first place. From my last post on TWS BIAS, someone posted an unclassified source document that was taken down, and that document has complete description on how TWS and STT scan centering should work. STT_TWS_Antenna_centering.trk

The quick way is to switch to guns and then switch back to clear any trackfile in the radar memory

As shown in the track, when you enter TWS Auto from AACQ in TWS Manual, or, from selecting and deselecting RAID in TWS Bias, you can still move scan elevation up and down. Even after STTing the target and deselecting STT (not using SCS right, which rejects target for a short amount of time), you can still move the scan volume up and down while in TWS Auto. This makes TWS Bias basically useless, since you can't recenter the TWS mean point after "biasing" the scan volume around your desired targets. It also happens sometimes when you enter TWS auto from STT by clicking the MFD button. TWS_AUTO_BIAS_AACQ.trk

Problem is I don’t have to be on 4,5,6,7Y, those stations being in the map will jam the datalink. Also, maybe document this somewhere in the manual, instead of letting people find out every now and then.

So few days ago I reported a bug that in multiplayer cold start fighter to fighter datalink doesn't work: turns out it is not the case. It was two tankers with 6Y and 7Y tacan channels interfering with F18's TNDL. After a night of debugging deleting units one by one I narrowed it down to channel 4,5,6,7Y, but I didn't test with other channels. Attached are two tracks, one with tacan 7Y, notice I have no tacan bearing/range as well as any PPLI. When I switched to 3Y, PPLI returns. I didn't record 4,5,6Y's operation but these 4 channels are what I found out that jams datalink so far. I want you guys to know this is by no means a priority, mission makers can easily avoid these channels. Take your time to fix it and test it. 3YMIDS.trk 7Y_NOMIDS.trk

As title said. I did all the necessary communications only with no ball call, but ball call is not needed for case 1 recovery anyway. I also did one with ball call, didn't record the track though. In neither those cases was the meatball visible on the actual station. It is only visible on IFLOLS overlay, but the overlay disappears at ramp to hand off to the actual IFLOLS, which isn't visible. This only applies to carriers with working deck crew. I tried it with Stennis, and the meatball was clearly visible. I've deleted metashaders and fxo. NO_BALL.trk

Supercarrier IFLOLS is now only visible in the overlay. I have volumetric light turned on, the meatball isn't visible whatever I do. Tried it in both Case 1 and Case 3, both with ball call.