Maulkin

Nevermind I forgot that the mission does not calibrate to the joystick until after I have touched something on it. Despite my throttle being all the way back, the sim didn't know that until after I wiggled it a bit. Then I could start the engines. :) I forgot how much fun it is to fly this plane :)

I am trying to do the single mission "Ramp Start and Navigation" and the first thing it gets me to do is turn on electrical power which I am able to do. It then gets me to start the left engines with LALT+HOME and I can see the engine start light breifly light up but then nothing happens. Same with the right engine. Anyone know what I am doing wrong here?

Oh I like the second idea! Thanks!

Hey guys I am fairly new to the mission editor (last time I touched it was when Flaming Cliffs 1 was released) and things seem very very different and yet the same so I get confused easily. I thought a good place to start was to edit the P-51 vs P-51 quick mission and set it to P-51 vs Fw190 but when I set the Fw-190 to Germany it flips it to blue and I cannot seem to change it. I can see the definition for which countries are Red and which are Blue in the briefing but it does not seem to let me change it there. So where can I put Germany on the Red team?

They have a strange name but I have attached them to this post.

Now we need some with the P-51 facing the Fw-190!! :)

Sorry for the delayed response. I have been very busy at work. I will email them to you as soon as I get home from the office and I will try to make a video demonstrating it.

Yup and I tested the axis to make sure there wasn't any crosstalk And there is a value of 5 for the deadzone of the rudder input. That being said it would not explain why this issue disappears when the aircraft stops moving.

This is only visible when the P-51D is moving down the runway. If the aircraft is stopped you cannot see it. With some forward movement down the runway, if I press on either one wheel brake or the other, but carefully maintaining a neutral position of my rudder pedals, I will see the rudder snap to the side on which I have applied the brake. The faster the aircraft is moving on the ground, the more obvious this becomes. If the aircraft is still (with engine running) then pressing on the left or right wheel brake will not cause this.

OMG thank you thank you thank you!!!!! I have been at this since Friday every spare moment and I had just given up all hope and the next step was going to be a full OS re-install (which I guess would have solved it but that would have been so painful. Thanks so much!!! And so fast as well. :)

I have raised a ticket but I am hoping someone here might have also encountered this problem and found a way to fix it so I am going to post the details here: After performing a motherboard and CPU upgrade I reactivated the three DCS modules I own: P-51D, BS2 (upgrade), and A-10C. It is important to note that I was unable to reactivate using the a10_protect.exe for the A-10C module but instead I was forced to use the protect.exe in the standalone A-10C that I still have installed. The other two modules appeared to activate properly. After enter DCS World, any time I attempt to run one of the modules I get a window pop up with the title "Warthog 64 bit - Error" asking me to reactivate the A-10C module: "The Activation Key is not valid any more due to significant changes of the computer hardware configuration. Press "Retry" to reactivate the application. If the error recurs, press "Error report" and send the report to product technical support." If I try "Retry" immediately get a crash: Problem signature: Problem Event Name: APPCRASH Application Name: dcs.exe Application Version: 1.2.3.9871 Application Timestamp: 512bd49f Fault Module Name: ntdll.dll Fault Module Version: 6.0.6002.18541 Fault Module Timestamp: 4ec3e855 Exception Code: c0000005 Exception Offset: 0000000000048e2e OS Version: 6.0.6002.2.2.0.768.3 Locale ID: 1033 Additional Information 1: 5928 Additional Information 2: c68df113c525a12234b64bed5060258a Additional Information 3: 5c5c Additional Information 4: 6069216743c77aad98b0021af2404cd2 Read our privacy statement: http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409 If I select "Error report" then it generates a report which I have attached. If I select "Exit" I will be prompted two more times and then it will open the module, however if the module is either P-51D or BS2 then I am able to fly the aircraft, but if it is the A-10C then it does not let me fly the aircraft. If I attempt to open the standalone version of A-10C then it opens with no problems and I am able to fly the aircraft. I have uninstalled and reinstalled DCS-World and all of the modules but this did not change the situation.

Yup all three of mine just activated!! Yay!!!

Has anyone else raised a support ticket for this besides me? The first post to this thread was Feb 22nd and I am surprised this has gone on for so long.

I just bought a new motherboard and CPU so before installing I deactivated all three DCS products I currently own (Ka-50, A-10C, and P-51) which worked fine about 4 days ago. Now I am finished with the installation and now I am also unable to activate any of my three licenses. The website is also unreachable. And plain star-force.com just displays a blank page. This really needs to be looked into.

Game Avionics is disabled. As you suggested, I opened the training mission in the mission editor, then I set the ammo down to zero, saved the file, then set the ammo back up to max and also put on external fuel tanks, and saved the file. I put on the fuel tanks just so I would have a visual indication that the file had been modified. Ran the mission through the 'single mission' and it now works! Thanks folks!! :)

Here are two track files zipped together. One shows an example of where the guns are working fine in the instant-action mission "Intercept". The other should show the training mission where the guns do not work.

Yup, I flicked the switch to the bottom one (Camera & Sight) then back up to the 'up' position just to be sure, and still the guns would not fire. Then I went to a quick mission and performed the same test and it worked just fine.

While the training session does start in active pause, I did not notice the guns firing to depletion during the initial introduction to the gyro gunsight. The version I am using is v1.2.2 and I have confirmed that the HOTAS is mapped correctly by going in a quick mission and confirming that pulling the trigger will cause the guns to fire, but to be certain I used the space bar as well which is the default 'trigger' for the P-51D guns, to no effect. I will see if I can figure out how to post a track. So based on your replies, you guys did not have this problem with that particular training session? Because I have never gotten it to work, not even in the beta.

A while back I had tried this training and ran into the same problem but then moved on to something else, but now I am back and I am determined to figure out what I am doing wrong! The training sessions I am talking about is the one under 'Combat Employment : Aerial Gunnery - Gyro Sight'. After following the instructions there are two P-51D targets spawned to practise on but when I pull the trigger I get nothing at all! I check to make sure the switch is set to guns/sight/camera and pull the trigger again and I get nothing. I set the switch to off then back to guns and still nothing. I opened the mission itself thinking that perhaps the aircraft was not given ammo but it was. Then I loaded up a quick mission just to make sure the keybinding is working and the gun fire with no problems. Has anyone else encountered this or figured out how to fix it?

Thanks Tailgate this has been driving me nuts. Last night I was trying to do the "Red Rover" single mission and the first time I loaded the mission the engine seized instantly within seconds of the mission start. I hit the refly button and this time it didnt seize up right away. I am flying along and the gauges appear to show nominal reading for a good 30 minutes of flying and then it happens again! Then I try the free fly quick mission and it was all I could do to keep the RPM out of the redline. I had to drop MP down to half normal cruise. Reflying the mission and this time it didn't happen.

Now that I know where to look I found it using this handy shockwave-flash cockpit trainer I found:

Ah thanks Melcar.... I was flipping through the BlackShark user manual and could not find that.

It has been a long time since I have tried a night mission but today I got an assignment to perform a mission at the dead of night and was given NVG's to help see stuff. When I turn them on I am almost blinded and cannot see anything at all! At first I thought perhaps it is not late enough at night but then my wingman complains that it is so dark he cant see a thing, but I am finding it easier to see around with them turned off then it is with them turned on! It is almost like the gain is up too high. Can anyone suggest what I might be doing wrong? I could not see a gain knob anywhere... just the toggle switch to turn them on or off.

Did anyone else notice that when you close or open the canopy it appears to be a bit more choppy now? I dont recall it being like that in the previous version.....

I think only the full install of Black Shark 2 will currently work, not the Black Shark 2 upgrade and not Black Shark 1.