Nereid

At the moment the gadget appears out of thin air but it's only a ghost - just visible for the pilot. ;) So, why and where from appears (I should say materializes) the gadget in front of the HUD? And why can't we see it from the external view?

Of course, Leatherneck: please keep both! For the meantime and CH Products users, I have created a CMS script that uses two buttons on the stick or MFP to move the weapon selector knob left/right or resets it (short press moves left/right, long press resets it). If anybody is interested, I could post this.

Well... is there any chance for an increment/decrement key bindings on the weapon selector? Currently we need 11 keys to bind on a HOTAS. But because the knob is easily visible increments/decrements work better (most often it's the other way around).

Of course the gun cam may not be of great usage. But why is it (ore at least some strange kind of gadget) magically appearing in front of the HUD just after enabling the gun cam power switch (RV34)? Some way to emulate a manual installation of the gadget?

See topic. This happens with use of the english cockpit of course: Labels on T-10/T-4 table are russian if not lit and english otherwise. To be more precise: Not the ingame mouse-hover labels are meant, but the ones visible in the cockpit. The way it is the bulb seems to magically translate the labels. :) EDIT: This should be postet in 3D Model and Cockpit section. If any mod can move it... :) EDIT2: Thank you! :) :)

Pressing "RCTL RSHF Num/" should move the cockpit view backward. Instead the keypress "RCTL Num/" is recognized ("zoom external out"). Not a big deal. Reassigning the key works. But maybe this will affect other keys, too.

Tacview (1.6) shows no IAS in my flight recordings while in the F-86. In other modules (A-10C, P51, UH-1H) the IAS is recorded. A bug in the F-86 module? Tacview shows "Tacview 1.5" as recording device. Is there something wrong with the installation/integration in DCS?

Well maybe I was not flying long enough or flying in time acceleration differs. My VSI was working all the time. If time allows I will try this without acceleration. But the IAS was behaving as described: ascending and airspeed increase, descending and it goes down. And then it was working again. So yes: Pitot heat is ineffective at higher altitudes. I had an engine failure in my first test. Is this caused by a disabled engine anti-ice?

Yes, confirmed. But its recovering from icing when descending and pitot heat is on (don't know if pitot heat off will make any difference). And the VSI was functioning all the time.

So I was to low obviously...

Well... how did you manage to get the pitot tube freezed? I have tried to freeze the pitot tube with pitot heat off (just for testing if this is simulated) and even temps below -10 degree but the airspeed indicator still works. Is there some kind of randomness in there or do I have to fly longer then 20 minutes?

Anyway. It's only a very minor bug. If they will never fix it, it won't really matter. It just had confused me, because if it works on the ground you expect it to work in flight, too.

Ah, ok! You are right. Well, this is a bit nitpicking then ;) but then there is another bug: Why can we communicate with ATC and "\"-key on the ground if this button is only for communicating with the ground crew? It took me a while to check this in the A10: using the MIC Switch Forward will get you to communicate with ATC, the \-key will not. Because it had worked for me on the ground in the F-86, I had assumed the \-key was the correct button. This is wrong, but then it should not working on ground.

OLD: Starting airborne with the F-86 in an user created mission seems to prevent the player from accessing the communications menu. The default keyboard assignment (key \) won't work anymore. This will not happen, if you start on the ground or choose another type of airplane. EDIT: No bug. But communication with ATC should not work with the \-key. Inflight the menu won't open but on the ground the \-key opens the menu and communication with ATC works (it should only work with the correct key RALT-\ for the microphone)

Is the remaining seeker sound when switching back to guns a bug? You can't even adjust the volume anymore. After switching back to missiles the volume is adjustable again.

LOL. And I just checked the left wing (but didn't know what to look for) and took just a glance on the right. I have never noticed a hole on the right wing so far... But thank you. The manual should explicitely mention a hole not an indicator (I was looking for a red/yellow/whatever-color thingy that were somewhere on the wings) EDIT: It's not just a hole. It's an indicator but not very eye-catching. Anybody looking at the right wing would see it.

Well, I don't think so. You can't see much of the flaps in the cockpit. So I would expect some kind of "mechanical indicator". But I do not see any...

In the takeoff procedure of the manual we should check the mechanical indicator on the wing for the flaps. Is there any in the sim? Page 93 of the manual: "Takeoff: [...] 4. Set flaps to takeoff position. Push selector switch located on left side panel. 5. Verify take-off position by observing the mechanical indicator on the wing. The electrical indicator [...]"

Strange. I have done this with 40.4 Mhz AM and set channel 1 and 2 to 40.4 Mhz without any success. Does AFN-2 only work with channel 3? I will try channel 3 instead...

This is not true. Well, it depends on your definition of "frame rate". If you define fps as an average frames per second over a given interval, then a SSD could (and in most times will) improve fps. That's because any stutter will reduce the fps at this moment to 0 fps and the average fps per second (averaged over a interval greater than a second) will drop. If you define fps as an average over an interval excluding stutter or over a single large interval, then a SSD will not improve fps (or at least not much). But's thats not a definition that does make any sense for a player. The most useful definition of frame rate in a simulation would be the minimal average fps for a short given interval (a few seconds or less) measured over a couple of those intervals (several minutes or more in total). And any stutter in one of those intervals will decrease fps drastically then. I have played DCS without a SSD at first. And ever then and now there was stutter. It was quite annoying and I have noticed hard disk access at every stutter. After installing DCS on a SSD the stutter was gone COMPLETELY.

Maybe this not the correct forum, but I have noticed that in the cockpit of the AI model of the Mig 21 there is a strange orange area directly in the front of the pilot. Its visible in the external view. Is this a missing texture? The cockpit is very well done even in the AI model. You can even see the radar display from the external view. Hopefully this will go away when the real Mig 21 is released...

How exactly have you done this? I have tried it myself but the damned needles won't move. :(

Cool. :) Another Module and two days of holiday to spend...

I'm incredible bad at dogfighting in DCS. But it's true what you said: I wish there were some way (at least I do not know any) to create a mission where some AI pilots will do a barrel roll or other flight manouvers at a specific time. This may even great for aerobatics exercises as well.

Yes. And I repeat: impossible. The video wont proof it, because we can't see if you are using your brakes. If you do, you are NOT dancing the rudder but the brakes. And with an unlocked tail wheel I got a lot of problems this way. I have tried it three times just for testing. Two times the Dora wents to the right just a second after start with minimal effect on the rudder. One time it goes forward and wents right a few moments later at higher speed, so I could catch it but not really control it. I could have catched it with the brakes, but not with the rudder alone... This wont happen with a locked tail wheel (i.e. the stick aft), but you suggest to UNLOCK ("neutral stick") it just at start. I'm not quite sure if using the brakes as suggesting before will do really better. I have just tried it a few times so far. And just to avoid misunderstanding: I don't complain for an easier takeoff. But all tutorials won't work for me. With full throttle I need to have luck to "survive" the first 2 seconds of takeoff. If the Dora keeps straight for this time, I can mange it to stay on the runway (and maybe takeoff). If things went wrong the first 2 seconds, I have never managed it to get any real control so far. Without full throttle at start, I need more than 2 seconds. I knew this. But I erased all axis controls just before assigning it yesterday. I will cross check it, but I doubt I have done any mistakes. "head movement with g forces"? Interesting. I will check this, too. No, its off.