NakedSquirrel

If you hold the primer (and starter) up after the engine starts to cough, it will catch

Well I know the engine breaks if it gets hit by flak or shot. That is kind of given. I've read ED plans on improving the DM of their aircraft, especially the visual side of things sometime after EDGE (ETA 2 weeks of coarse) I'm just asking if the internal wear and tear is modeled with these recent patches? I tested using my own mission in the mission editor, then decided maybe it was my mission settings and went to the "landing" final approach" instant action mission. I was able to do whatever I wanted with my throttle and pitch settings, the engine continued to run until it ran out of fuel. Same happened when I tried a MP server. I remember being able to break it before if I ran at 61mp 3000rpm for 10-15 minutes. Using WEP, The engine would quickly break, but I never timed it. I always assumed it was 5 minutes (per page 30 in the AC manual) I used to be able to keep the engine going for about 1/2 an hour if I ran at 60 manifold and 3000RPM, but now those precautions don't matter? I can run full 67 MP and 30rpm without any worries at the moment. Is there something in progress with the Mustang? I didn't see anything about the P51 in any patch notes, I didn't know the engine values were being tweaked?

Thanks for the replies! I didn't see the "Raw Documentation" Part 1 and 2 at the top of the page. :doh: At least I have something to stare at blankly while I try to figure this out! :book: (Witchcraft is sticky in the editor scripts post: http://forums.eagle.ru/showthread.php?t=118935 , but I think it deserves it's own sticky post like MIST)

I've been trying to find the engine limits of the P51 to include in a tutorial, but when I finally sat down to test the limits, I can't find any? I wanted to test the engine at different throttle and RPM settings, but even on the deck through the gate (WEP) the engine lasted over half an hour (I ran out of fuel before the engine would break). I didn't think to take drop tanks or fill the fuselage tanks for these tests since I was going for "combat power". I thought it might have been something to do with the mission settings, so I went on a MP server and I found the same thing... I had my engine seize once during the MP session after 20 minutes of flying 67 manifold and 30 rpm. Then I thought perhaps it was because I was constantly over 300mph so I tried doing stalls and dropping flaps... my temperature went up, but my engine kept running. The second time, while stalling and flying at 100mph, the engine finally slowly quit after about 5 minutes of slow aerobatics. Surprisingly, it didn't seize up right away, it slowly died after sitting at 150+ degrees for 2 minutes. Am I missing something? Did Spinaltap tweak my P51?

I am just beginning to dabble with lua scripting for DCS. I am wondering if there is a list of variables for in game functions, trigger actions, conditions, ect. I have some experience scripting with ARMA, but DCS is new to me. Lua seems fairly simple, but I am trying to figure out how to reference and interact with the mission. Scripting for ARMA was rather easy to pick up since they have a rather comprehensive dictionary for in game scripts: https://community.bistudio.com/wiki/Category:Scripting_Commands Is there something similar to this for DCS? I know the game has quite a few of them. From playing training missions, I know that the game can tell when you've pressed a button, and trigger actions can even tell if an aircraft is at a certain altitude, velocity, heading, ect. I have read through the "Introduction to Lua" post in the forum, but I couldn't find any reference to it on the post or any of the provided links.

Aim-7 doesn't go pitbull and accidently hit friendly aircraft. I always carry at least one Sparrow in my loadout just in case I have friendly aircraft around the enemy I'm trying to kill

First 2 dogfights First two dogfights in the K4

I was able to reproduce this bug. Game crashes when you dive from high altitude with idle throttle and full prop pitch.

Gav, it may be because the starter overheats since it takes the engine a lot longer to catch now. A trick to starting the engine with the latest build is to hold down up primer switch after the engine starts to ignite. This seems to be enough to get the engine to catch every time for me.

=P Done sir, Been spending a bit more time on the P51, because the 109 slots are always taken in MP! (I'll get more time in the Hun planes when the Spit comes out, for sure :pilotfly:) This is a pretty sloppy dogfight but maybe it shows some of the strengths/weaknesses of the planes. The main/only thing the P51 has going for it is speed. You can pull pretty decent turns at 200mph, but below that the plane becomes a dog. Most of the turns I made weren't really to get on his six. They were mainly to make him cut into my turn and lose airspeed so I could get distance and recover energy. I'm not very good at 1v1 though, I prefer flying with a wingman.

Thanks for the help!

Is there a way to view/edit .lua scripts saved in a .mis file? I noticed that .lua scripts are saved internally in the .mis file when you save a mission, but is there a way to view the .lua scripts saved in a mission, or do you need the original .lua file to edit the scripts?

Diving Oval Check out Dart's Tutorials An old game, but the concepts are the same. Enjoy! :smartass: Additional videos on the subject:

I want a Hawk :)

Go to create new mission and you should be able to change which countries are 'blue' or 'red'

Fighting the 109K Difficult but not impossible. I really had to micro manage my flaps and trim to keep my E. I don't think I would fight like this against a human opponent, but also I don't think human opponents will be hanging at 50-100kph stalls for extended periods of time like the AI does, because their engine would probably overheat. The mustang isn't very competitive against the 109 below 7000ft, because your only advantage (speed) is gone at low altitudes.

Same trouble I have tried running the .reg file, but it does not seem to help. Is there a way I can manually look up the registry entry, or is there another step besides just running that file that I need to do? The one thing that is different for me that I dont see others having on these posts is that my number of activations does not go down (but also my mig21 hasn't been able to run after "Activating"). Obviously it ran fine before, but now I'm having the same error that others seem to be getting.

:harhar: Made this as a gag, since most of the PVP missions we play have empty fuel loads for FC3 aircraft and refueling takes... forever!

FM still needs some work. I didn't expect it to go out of beta so soon. Control surfaces are extremely efficient at extreme speeds, plane does not over-stress in high G maneuvers, pilot blacks out instantly at negative G force, and doesn't black out with high positive G maneuvers like in the video.

Doh! Thanks for your help! I looked at the dcs.log and figured it out. Apparently I am a moron when it comes to github and my witchcraft was corrupt (When I opened up the witchcraft.lua I found out it had extra html code plopped in). :doh: I doubt anyone will have the same silly problem as me, but something to note is that DCS caches .lua scripts in the mission file. Even after I fixed the lua file I kept seeing messages like this: 00043.084 ERROR DCS: Mission script error: : [string "C:\Users\...\AppData\Local\Temp\DCS\/~mis00003D88"]:5: unexpected symbol near '<' So it took me a bit before I realized they were cached in the mission. After I got everything updated, it all worked smooth. Thanks for your help! I don't think I would have figured it out if you hadn't replied. :thumbup:

I am wondering if anyone can help me out. I've been trying to get DCS Witchcraft to work, and I have followed the tutorial to the T, but I keep getting this error message when I start a mission using the script: [string "witchcraft.start(_G):1: attempt to call field 'start' (a nil value) stack traceback: [C]:in function 'start' [string "witchcraft.start(_G):1: in main chunk I've followed the readme and copied what the video did to the T. I've tried running it on mist 3.3, 3.4 and 3.5, but I keep getting this error message. and the witchcraft.cmd (npm) shows "npm info loaded ok" but program only shows "Waiting for DCS to connect..." Has anyone else had this error, or maybe have an idea of what I am messing up? I am hoping it is something simple I have missed. I've gone through the tutorial and readme over a dozen times just to make sure I have every element implemented properly. I dont know if I am missing a game or windows setting or what I am missing. Any suggestions or help would be appreciated.

Some simple KA-50 tutorial videos that go over the cockpit and how to use the weapons. I don't think I posted these on the DCS forums, so here they are, enjoy! ${1} ${1}

I nominate drsgfire I nominate Drsgfire May he crash the plane on landing as much as I have Muwhahaha!

How do I get rid of the red crosshair in the center of the screen? It only appears when flying the MIG-21. ---- EDITED + ANSWER ---- DISABLE PADLOCK -> This can be disabled in your game options Question 2: Why does this only affect the MIG-21? Answer 2: I don't know just disable padlock and quit asking questions!!!!