Lawlcat

Here lately every flight my ASP will randomly turn off as I am climbing from takeoff. It's random time that it does it, usually shortly after, and clicking switches doesnt do anything to bring it back. Eventually it'll randomly kick back on even if I do nothing. It's not just the sights that goes out, all the ASP loses power (all red lights on the rotary range things go off) I was able to capture it in a track file I have had both myself and another watch the track to confirm the ASP goes out. Right around 3700 meters or so as I am climbing. No system failures are noted in the briefing after the fact. This happens even if I use the right windows home auto start procedure and go straight to taxi. Note, this is a multiplayer server the track is from and there are 2 or 3 other people on, so just wait for me to spawn in within a few seconds :) lostASP.trk

As the title says, wondering if anyone is working on a Helios profile for the MiG-21. I'd try to make one myself but I'm not competent or artistic enough to make a decent one. Unfortunately for me the Fishbed is something I have to look down often in, to see instruments, and its starting to make my neck hurt with trackIR :)

This is a very common problem with DCS. AI do not properly manage fuel and pretty much run mil/AB the entire time. My wingman as well said bingo, then 15 seconds later ejected. I was still able to land, got the Mission Success notification and campaign continued just fine. Not a specific issue with the mission/campaign, just DCS.

I'm seeing the same thing. First mission was alright, second mission I can't go through. First time I tried it I ended up in a MiG-21, but on the redfor team. Exited, launched it again, this time I was in a MiG-29. I can't seem to get it to spawn me in a blufor MiG-21.

Has anyone had any luck deploying the 4x250 bombs yet? I am able to use the 500kg bomb easy enough, just pick a fuzing profile and hit weapon release. The same motions for me don't seem to do anything to the 4x rack however. Any tips?

This is a bug with extreme and instantaneous G-forces causing instant black out of your pilot. It happens a lot at extremely high speed and low altitude. Wiggle the stick left/right/forward/back and watch your G meter in the F2 external view. It will regularly spike between 30-40 positive Gs and -15 to -20 negative Gs, resulting in and instant blackout for your pilot. This is a problem with the flight model

I am finding multiple morse codes playing. The first station you tune to is fine, any successive tunes result in the sound playing on top of other morse sounds.

I'm seeing an issue where when I tune to a station on the radio, I hear the Morse code for that station and the compass works fine, but if I then tune to another station, the new Morse code plays on top of the old one. This makes it very difficult to hear the Morse and make sure I'm on the right station. The problem exacerbates as I continue to tune stations to the point that I am just hearing constant beeping that is indiscernible. Has anyone else ran into this issue and found a fix?

For those looking for a quick fix, switch the switch back to MISSILE and turn the volume down on the top left missile panel. Then switch back to gun. What seems to happen is that when you switch to GUN, the last sound being played with regards to the missile loops. If you have a lock on a target and switch to GUN, you hear the constant high tone.

This needs a binding because trying to look down and click the switch to go from missile to gun while dogfighting is troublesome

Seconding this. When I first started using the Sabre I wasnt even sure my engine was on with the cockpit closed. Cockpit open sounds alright, but closed nothing. Every other airplane sounds fine. Using 1.2.9 stand alone

With the kneeboard up, you can also hit RCTRL + K to put a marker on it of your current position and heading! This is super handy for finding out where you are and where you've been (the markers dont go away)

Lets say you have 3 targets bugged in TWS mode. From my understanding, the functionality is such that you can launch your first 120 and your PDT automagically moves to the second bugged target. From there you can immediately launch again. Does maintaining bug on the target count as keeping lock and providing data to the 120? Or do I have to switch back or keep the target that missile is going towards as PDT until pitbull?

I'm sorry I guess I just don't understand? My available keystrokes per the control settings are Kneeboard Next Kneeboard ON/OFF Kneeboard Previous Page Kneeboard current position mark point Kneeboard glance view I don't have a "show/hide" button option. Next/Previous do what they say on the tin, ON/OFF disables or enables seeing the tablet on my knee, current position mark point does I don't know, create a markpoint? It doesn't affect the tablet though. Which is the show/hide key/button press that I should be using to momentary view?

So I decided to grab this mod and give it a try... I'm currently using DCWorld 1.2.7 Open Beta so obviously anything broke is kind of null and void for reasons. I was just hoping maybe someone has figured this out or maybe I'm just doing something wrong. I have the mod installed and it all seems to be working fine in the virtual cockpit. I can look at it, change pages, turn it off/on, add custom pages, etc. All of that works great. I keep seeing the RCTL + K "Glance View" which I assume, and this is where I may be mistaken, that it would then pop up on the screen infront of the camera for a quick view without having to look down with TrackIR. When I do this, however, the pad just disappears in cockpit for however long I hold RCTL + K. I've added Kneeboard_TEST.lua to the config/monitorsetup and the entry for ED_A10C_KNEEBOARD is in there. (I'm using the DCS: A-10C module, for the record). The location/width/height looks good, but just nothing pops up. I have also selected KNEEBOARD_TEST.lua as my monitor option in the options page for graphics. Is my understanding of what the Glance view does incorrect, am I doing something else wrong, or does this just not function in the beta?