Napillo

https://www.arsenal-bg.com/c/23x115-mm-rounds-for-aircraft-automatic-guns-gsh-23-gsh-23l-gsh-6-23m-and-am-23-134

that needs to be fixed, we need AP, otherwise why would they mount the gun at an angle? If you can't barely take out ground targets, it seems like you could just tilt the gun up a couple degrees and make it for air to air use, but noooo they pointed the gun down. Also, why can't we have the 30mm ones?

No, you want to set your own OAP? the weapons use the OAP and the designated point, so the only way to get the coordinates of the OAP, you have to have the designated point and then do the calculation yourself. On the weapon itself you can specify the OAP or not, but no you can't get the gps coordinates.

I still get it, and not just from teamkills. It seems it can't load some part of the damage model.

I used to do that, but having to select a target with the tpod before they fire is kinda limiting, easier and faster to take the MK5, or the UG ones and align the CCIP marker to the target.

it also disappears when you don't have datalink. I've also had some weirdness with the radar screen, where the 60 degrees scan volume would have the lines, and many times I switch modes, the radar is already locked, and the lines are in the wrong place with respect to the cursor, moving the tdc back between the lines will then snap the lines around the tdc.

citation needed.

I removed that, it was just an extra spawn for trying something out. It does lock if you set the item scale from 5m to 15m, so I think it's ok, just odd.

the knob is covering the dot on the 'UFCP BRT' knob. It needs to be pushed to the right a bit, or the texture needs to be updated.

See screenshot

here's the track the tpod locks fine, radar locks fine, 701IR will not lock it at all. 701T will also not lock it at all. replace the Apache with UH-1H, 701IR will track, 701T will track. 701IR-wont-lock-apache.trk

There's sufficient contrast in IR, I can clearly see it, but they won't lock.

Looks like this might be a DCS issue.

They just put an image on the ground like there's a hole there, but there is no hole. runway bombs dont hurt runway.trk

Target something from the HUD, in air to ground mode, switch to air to air mode, you get 'shoot' cue if close enough. Firing an SD-10 goes towards the target diamond, but it will miss by a lot.

Chinese manual was released, it'll be already on your computer. English - not yet.

I'm not trying to lock (yet) in GMTI mode - I want to set the radar to track a specific area, and GMTI around that area. When I put a target (diamond) on where I want to look for ground moving targets, and switch to GMTI, GMTI defaults to looking back at the current nav point, instead of the current target. I know how to use EXP and DBS, yes I know the TGP can be slaved as well. I don't care about that, I want to do GMTI.

If I target from the MAP mode, switch to GMTI, it immediately switches to tracking the waypoint, not the point that I targeted on MAP mode. I would expect it would GMTI slaved to that MAP target point.

go into ground mapping, hit 'FRZ' and your targeting cursor disappears. I think it should allow you to target while the radar is frozen, otherwise what's the point of freezing the image?

it was 9/10 degrees. I was at about 40,000 ft, trying to hit someone I locked on about 44nm away. Unfortunately, it takes a while to get that high and thus the trackfile would be prohibitively large. I think my AOA + the pitch up might have been about 15/20 degrees if you add them up. I will note that I will try to get a VS lock first, and then switch to a TWS lock by hitting (2) INTC mode button to switch from VS STT to TWS bug.

that dial... that's the magnetic correction?

If you want the GMTI to work to 80nm out, all you do is go to GMTI, turn on RBM, and then switch back to MAP mode, change it to 80nm, and then switch back to GMTI. Now you have GMTI with RBM 80nm. Turning the range down, afterwards, puts GMTI in 20nm.

idk its weird, I lofted today when the enemy was at the 80% range, it lofted up, and up, and kept going. I never dropped lock (TWS bug) it just decided to loft itself further into space and leave the planet. Maybe at higher altitudes, it auto-lofts without pitching up? If so, why did it not track towards the enemy I had locked? If my plane was sending it signals, it seems like it ignored those. Also the plane flies really different at high altitude 35k+ now. I can't get much over 43k, (before I could get up to 50 if I tried) but I get great mileage that high, and can stay in AB the whole time with barely any fuel burning. Oxygen didn't go down much either. What happens in high altitudes now is I keep climbing very slowly, and my AOA keeps going up and up, but altitude trickles up, until I'm at 14 aoa before I realize it, but it doesn't act like it's stalled, still somewhat controllable. It basically gets to a point where you get the highest it can go, and it just keeps slowing down, and increasing aoa until you back off, or fall out of the sky. Unfortunately, that high up you can't get near mach 1. I then dropped about 3000 ft, about a 5 degree dive, and very quickly gained speed, but not more than 1.2, more like 1.18. I'd expect at least to achieve the maximum speeds listed. That was also after jettisoning the tanks, and I did have the dual rack for sd-10.

It used to work, I remember accidentally hitting that button for viewing the flight, and when I went out of it, I couldn't get back into it, I assumed it had blown up.

I don't get your point, it is as a reference example that you can see how it looks mounted. It's not a photo.