ScAvenger001

I quite like the PLAT cam view. It's pretty much exactly what I was hoping for. The size of the boxes will need to be revisited, though. As it stands, it's possible for a landing aircraft to be so far below the glidepath that the ramp is between it and the camera, but still inside the black box. WIP, I assume. Also, there's a checkbox for a voiceover but I didn't hear anything.

About a year ago, we had this conversation: Now that it seems like the Hornet really is only two weeks away, I wanted to know if there's been any movement on this feature? Tacview's been such a great training tool, and it would sure help if it could be used here as well. Thanks!

(Tested in "ready on the ramp" mission and several homemade missions) Sometimes the channel will change in the opposite direction of what it should, usually in the vicinity of M channel. That is, going from channel 2 to channel M by using the down mousewheel, the result will be "2, 1, 2, 1, M" instead of "2, 1, M". This also sometimes happens going up: instead of "M, 1, 2" it will be "M, 1, M, 1, 2." It's not fully constant, so give it a few tries. Seems to happen more with comm1.

Trying to stop from a relatively high speed (~25kts+) leaves a huge rubber trail on the ground, and below 10kts the main wheels lock in external view. Antiskid is definitely on the "on" position, not NWS. Tested this on the "Cold and dark" mission and the "ready on the ramp" mission. Also, the rubber trail seems to be being drawn from the nose gear rather than the main gear.

I was hosting a server for myself and my wingman, and we noticed that if one of us was unfolding our wings for takeoff, the other didn't see the animation start to play until the wings were almost completely unfolded.

I was thinking about all the naval aircraft that are coming up and I thought, "it would be really handy if Tacview had some tools for evaluating carrier traps, and maybe landings in general." Even just an and an indication of which wire was caught would be very useful. I haven't been following the thread, maybe it's already on the upcoming features.

I set up a bunch of flak cannons and flew a group of B17s over them. The B17s took serious losses, but visually they seemed to be exploding of their own accord: there were no visible flak bursts near or on the target aircraft.

I reported that in a separate thread. Basically there are a lot of lighting issues currently.

The anticollision beacon isn't blocked by the frame of the aircraft, and shines on certain parts of the aircraft interior when it shouldn't. Most noticeably, it shines on the front console. This makes flying at night with NVGs problematic, since the cabin brightness is constantly blinking as the beacon goes by.

* Dome light on "white" setting is very very bright. * Dome light on "green" setting is white, about like what the white setting should be. This is only true prior to engine start, once the engine reaches full RPMs the light will fade to green. * Dome light during engine start is magenta.

Although there is clearly a beam of light coming from the Huey, the ground is not illuminated. Tested on the ground, in flight, both Normandy and Nevada. I think the searchlight is also having this issue, but I didn't look into it closely.

Markpoints and steerpoints are static points in space. If the target gets out from under the steerpoint, using the steerpoint to aim with won't work any more. Thus, locking on with the TGP and using it as your SPI. The flashing P means the TGP is in IR-pointer mode. The IR pointer is basically a type of laser that's visible in night vision, so you can easily point out targets in the dark. It can't be used to guide laser-guided weapons, though, so make sure you're in L(aser) or B(oth) mode before dropping those bombs.

Tacview seems to be swapping Super 530s for Magics with the Mirage. It shows Magic launches as Super 530Ds, and the Super 530 launches are shown as MATRA. A feature I'd kind of like to see is a "friends" list. Usually when I'm reviewing a recording it's because I want to see what my buddies and I are doing. With that in mind, if we could make a list of callsigns and have tacview automatically highlight aircraft with those pilots (e.g. render them in green and yellow instead of blue and red or something like that) and maybe move them to the top of the drop-down lists it would make it easier to sort out complex situations.

On the first use after spawn, pressing the Decoy Release Program Knob Up or Down key sets the Decoy Program to "A." That is, if I click the knob to program 3 using the mouse and I press the knob up button, it will go to A instead of 4. It only does this on the first use, afterward they function normally.

--redacted--

I tried it some more in various weather conditions. First I did another try in 29.72 pressure and got the same result, so it is reproducible. Default weather (29.92), took off with the baro altimeter reading 40 in the hud, when it showed 20050 the f2 showed 20526. Winter, clear sky (31.10), took off with the altimeter reading 40, when it showed 19990 the f2 showed 18848. Note that this time the instrument is reading too high at altitude while the rest of the time it was too low. Also, it's worth noting that gradually increasing drift was also reflected in the radar altimeter as I flew over the sea. The radar altimeter showed the correct altitude over sea level as I flew over the sea while the baro altimeter lagged behind.

I set it correctly on takeoff. Batumi is 33ft, the hud read 40 on takeoff. The drift crept in gradually as I climbed.

The barometric altimeter has some drift in non-standard weather. I took off from Batumi (field elev 33ft) in the conditions of the Summer Clouds & Wind preset. By the time my altimeter read 20,000 feet (according to the HUD, didn't check the gauge), the F2 view showed me at 20,920 feet. Do real altimeters behave this way? I don't think so.... Conditions were: temp: 26*c Clouds: base 1969ft; thickness 2526ft; density 5; no precip QNH: 29.72 Wind: 26k ft: 14kts @ 071 6600ft: 16kts @ 243 1600ft: 21kts @ 160 33ft: 10kts @ 160

Wow, I never would have noticed that tune button without it being pointed out. Thanks. The Gazelle's flight manual says that the FM radio in particular is so highly classified that its modelling in DCS is very basic (the keypad isn't even clickable), and I suspect most of the functionality for the UHF is in the same category. I'm hesitant to suggest that you just make something up for guard monitoring, but I also kind of doubt that there's any documentation to be found unless someone commits a crime for you. Should the volume knob and the power switch issues be reported to Polychop or do they already know?

Some Gazelle glitches... VHF/AM volume knob is backward. Radios turned off still hold their last frequency and can still transmit (according to the overlay at least, haven't tried it with another client). They don't update frequency changes until the radio is turned back on, however. Note that I tried this with a hot-started Gazelle. By the way, is there a guard-monitor mode for any of the Gazelle radios either current or planned? The manual says that they're all very very classified, but I'd expect the Ch. OTAN selection on the FM and maybe the G selection on the UHF to have some significance there. Also, the R-828 knob on the KA50 isn't changing the frequency for some reason. According to the overlay it's stuck on 21.5.

Done for both. Will you need the tacview or anything?

I knew what was in my inventory, I just thought it was larger than it was :o I'd been thinking I could carry five passengers instead of three.

I didn't get the speed part, so that's a good thing to add. What I was actually getting at, though, was that the "you are full" message should probably be higher priority than the "hover low enough" message, in order to avoid a frustrating situation where a pilot goes to a lot of trouble to hover properly and then still can't do the pickup.

So I was trying to do a hillside pickup and didn't realize my Huey was full. I kept getting messages that I wasn't hovering low enough even though my skids were dragging in the dirt. It makes me think that it's playing the wrong message there ("hover moar!" instead of "u r full!"), could you doublecheck?

To expand on this a bit, the lineup card and all the briefing materials ID the player as Ford 4, and Wags' voiceovers also always refer to the player as Ford 4, but if you (for example) call Nellis ATC, you'll self-ID as Ford 3. For extra confusion, there's an AI Ford 4 flight making position reports as they go through their flight plan. Also, the lineup card and briefing said vul time was 0855-0935 (40 minutes), but the map says it's +20 and Wags released me to RTB at 0917 (22 minutes).