AH_Sid

+1

The rudder issue has already been reported here HERE And the tail number issue HERE

Was there pressure in the hydraulics system when you tried this? It's working ok for me, pull the handle out, put the brakes on, release the brake, release the parking brake handle, It then remain out until you put the brakes on again which releases it, but there must be hydraulic pressure available.

I see this exact same bug has crept back in with 1.5.3.51171 Again having a space between BORT and NUMBER cures the problem until they fix it again.

In both the TF-51D and the P-51D the key bindings for the Horizon Cage aren't working correctly. "Horizon Cage" - ('LShift + V' by default) should just momentarily cage the Horizon while the key bind is held (like mouse clicking it does), instead it toggles the Horizon between Caged and Uncaged without turning the cage knob to lock it. "Horizon cage knob ON" - ('LCtrl + V' by default) should put the Horizon in the caged condition (held with the caging knob turned), but doesn't do anything at all.

I've been mapping out my key bindings for both the P-51D and TF-51D today. I notice the both aircraft use exactly the same key binds (not surprisingly), except the TF-51D doesn't have the binds associated with the weapons (guns, bombs, rockets, etc). That is they are exactly the same bar one, "Position lights wing DIM" in the TF-51D is different from the one for the P-51D. I assume this is an error and the binding should be "RCtl + RShift + U" and not just "RCtrl + U".

The default key binding in both the TF-51D and P-51D for "Rear warning radar Test" is "LShift + R". This works ok in the while in the "Adjust Controls" section, but if you try to use it while flying, it conflicts with the "Restart Mission" key binding in the "General" section. Not a big problem, I can reassign the key binding myself, just thought I'd point out the error.

Yes I've been getting this in both 1.5 & 2.0. Random amount of time into a mission, most of the internal cockpit sounds disappear, external sound is still fine though.

Have you tried turning the new option off on the 'Special' options page for the F-86F? I'm not sure why this option was introduced, but I turned it straight off and have just been using the 'nose wheel steering button' as normal, just like I've always done.

Thanks Denny, it's not like any equipment I've used before then. I'm still having trouble picturing what you’re describing though, does it have a constant pitch as you tune, that only drops in pitch as you pass a frequency with a transmission?

Many thanks for adding the working "CW-VOICE" switch along with the 900 Hz tone. It's not quite working correctly yet though; placing the switch to the "CW" position makes the 900 Hz tone audible regardless of current tuning state, which it shouldn’t. The 900 Hz tone should only be audible when a station is tuned. i.e. it's just like the signal strength meter. If no station is tuned you would just hear static (the same as in the VOICE position), and the signal strength meter would be fully to the left. With the station tuned in perfectly you would hear a nice strong clear 900 Hz tone, and the signal strength meter would be fully to the right. With the station almost tuned but not quite, you would hear a weak 900 Hz tone, and the signal strength meter would be around the middle of the dial. It's just like tuning in any old style AM radio where you adjust a tuning knob to change the frequency, you adjust it until you can hear the station you want the clearest (or in this case the tone). It’s an audible way of tuning it where as the meter is a visual way (and you have to be heads down looking at it). The VOICE position then lets you correctly identify it, but there are pauses between the Morse transmissions so it would be difficult to tune in while listening to the Morse alone.

In the latest public build (V2.0.1.49921), the canopy switch is now spring loaded back to the centre OFF position from the 'Close' position (many thanks for fixing that), but it's also broken again the fact that when the switch is held in the 'Close' position the aircraft shouldn't pressurize, or it should depressurize if already pressurized.

Credit goes to Belsimtek for doing the hard work fixing it, I just pointed out it wasn’t working ;)

Many thanks again, I see the 'cockpit pressure schedule' is now correctly following the pressure schedule from the manual in the latest public build (V2.0.1.49921) Just one small nitpick, if you’re at altitude and you move the 'cockpit pressure schedule switch selector' from 5 to 2.75 psi the cabin alt now jumps instantaneously from 22,000ft ish to 30,000ft ish, the rate of change should be limited a bit more, the same applies if you change to ram. In other words, if you change from a high pressurisation setting to a lower one, the pressure would slowly dissipate (between ¼ and 1 psi a second), not dump instantly.

I see this is all functioning correctly now in the latest public build (V2.0.1.49921), many thanks, I can now do a meaningful 'Flight Controls Hydraulic System Check' from the real manual as part of my pre-taxi checks now.

... and now functioning correctly in the latest public build (V2.0.1.49921), many thanks

Also working fine for me in 2.0.1.49921. Sorry NightRush, I know that doesn't help you much, hope you find an answer.

Hi Reflected <S>, good to see you here. Like jcomm, DCS has become my only sim now after moving on from WB/AH/ROF/BOS. If you’re still into skinning, you're going to love it here due the sheer size of the skin files; you can do your skins in amazing detail that would have been lost in the smaller size skins of other sims (see here for an example). You can even personalise your own pilot if you so desire or add your own details and notes the cockpit Personally I'm having a lot of fun with the F-86F, very different style of flying to the ROF Sopwith Camel, but still a simple aircraft to start and fly. Are any of the other HQ boys here?

Here's an idea of what I mean by 'fuzziness', this was taken by just holding an iPhone camera up to the lens in the Rift. I think I've found the reason. Looking at the F86F file containing the instruments, 'F-86F_Cockpit_Texture1.dds', (4096x4096). Looking at the similar file for the MiG-15bis, 'mig15bis_prib_org.dds' (2048x2048 ) but it's only doing the instruments. The area given to each instrument face is about same, so the same resolution, same number of pixels, etc. But if you open the file including the 'MIP maps', you can see a big difference. The F86F file just has the base file and one half sized version. Whereas the MiG-15bis has the base version and eleven versions, each half the size of the previous. In the F86F the lowest resolution one I'll see at any distance is the half sized one, which is still quite readable. In the MiG on the other hand, the further I am away, the lower the resolution will be. Even in the normal seating position I recon I'm viewing MIP level 4 or 5, which simply doesn't have enough information to make numbers out clearly (in the Rift anyway). Playing around with the file today, re-saving it with various levels of MIP, three seems to work the best (for me) and make the instruments in the MiG-15bis as readable as the F86F (if not better), in the Rift anyway.

The trouble is a screen shot takes a snap of the repeater screen on the monitor, not what I'm seeing in the Rift, so it doesn’t really show the 'fuzziness' I’m seeing in the MiG using the Rift.

Anyone else using the DK2 with the MiG-15bis? I've only just started flying the MiG-15bis after spending months flying the F86F. It's immediately noticeable how fuzzy the instruments are in the MiG-15 are compared to the F86F. The Rift's resolution means things are never going to be crystal clear, but in the F86F I can at least read the instruments ok, and if I lean in to look at an instrument in particular, it has an amazing level of detail and is very clear. With the MiG-15bis, the instruments look very fuzzy using the Rift, even if I lean in to look at them. Anyone else see this difference? I'm wondering if it's just my settings or install, or is there a difference in build standard between the two?

I the 1959 copy of the F86 Flight Manual I have, it has a slightly clearer image of the variable sight selector unit than the 1971 copy that I usually work from. There's also a fairly good picture in the Maintenance Handbook. I would have to say in both of these, it doesn't look like the text 'TR' is hiding behind the switch (although it can be clearly seen on the Fixed Sight version). The text in the Maintenance Handbook still mentions the 'TR.' position though, the same as the Flight Manual. So now I'm inclined to think it was a three position switch, but the 'TR.' position wasn't always marked for some reason (although it does look like there is something written to the left of 'HI.' in your photo above).

The variable sight selector unit's 'Target Speed Switch' only has two positions, 'HI.' and 'LO.'. It should be a three position switch with 'HI.', 'LO.' and 'TR.' positions. It's described in the F86F Flight Manual on pages 4-28 and 4-32. The picture in the manual is not particularly clear, but it shows the switch selected to the 'TR.' position (although the switch obscures the writing).