klem

Excuse me adding to this very old thread but will it also be possible to adjust the Settings (Graphics) on the fly instead of unloading, changing and re-loading test missions?

"I can enter the profiles into helios just fine" Profiles are to be kept in "C:\Users\[username]\Documents\Helios\Profiles\. Open "Helios Profiles Editor" and go to Profile.. Open.. to ensure Helios sees the profiles held in that folder. Open the P-51D profile "P51_v1.01b_eng.hpf" and check the Install Path which on mine is in the box named "Flaming Cliffs 2.0 Setup" (?!) I think this is where your point about not having Flaming Cliffs comes from. Check that the install path points to your DCS WORLD INSTALLATION, usually "C:\Program Files\Eagle Dynamics\DCS World". If it doesn't, fix it and Save it. Close the Editor and run the "Helios Control Center" to activate Helios and select a Profile to run. The Control Center automatically interfaces to DCS due to the Install Path you pointed to.

As we're all throwing in our own techniques..... Align precisely on the runway - you'll have enough directional concerns without pointing at an angle. Pick a point, cloud, runway edges for directional visual reference. Stick fully back to lock tail wheel. Hold that stick as though you were leading a baby by the hand. Apply a little right rudder and a little right aileron. Nail your visual reference before moving. Throttle up smoothly (hold on brakes to at least 50% to establish airflow over the tail). Detect directional shift and counter immediately with a dab of brakes and a touch more rudder and aileron if it's a large swing. Be positive but no more than is essential. Don't add to your troubles. Move stick to centre at 100+kph and be ready for any swing. Anticipate roll on lift off and remember that baby's hand, don't over-control. Better a wing-low lift off than over-correcting it into the deck Anticipate. Stay right on top of it. Fractions of a second count. Tip! If you find you have put on too much rudder on ease it off, don't kick in opposite rudder.

As Capt Zeen says, you don't need FC. In fact the P-51D is a DCS a/c not FC. I have it running with mine just fine.

Thanks Stonehouse. I've a Korea mission and I think for now I'll stick with GCICAP because it's simple and is nearer to the radar systems of the time (no AWACS). EDIT: CRACKED IT! GCICAP is working now. I just had that problem with the message timings. The mist messages timings were mostly set at a fixed value of 1. In particular around line 4270 was if #clientDisplay > 0 then trigger.action.outTextForGroup(clientData.groupId, table.concat(clientDisplay),1) now reads if #clientDisplay > 0 then trigger.action.outTextForGroup(clientData.groupId, table.concat(clientDisplay), displayTime) I changed all the likely cockpit messages to displayTime. Thanks for all your help.

ENGINE MODELLING Many pages here but I didn't find a post on this aspect of the Merlin. For the P-51D we have the Packard Merlin who's failure characteristics can be summed up as "BANG!" Can we please have a slightly more sophisticated failure model for the Spitfire Merlin introducing degradation/loss of power with overheating before eventual failure. Can this code also be retro-fitted to the P-51D Packard Merlin?

Many thanks Stonehouse. I did follow the manual but it looks like a lot of finger trouble on my part! I have it working now. One thing surprised me, the enemy GCI a/c spawn and take off as soon as I leave the ground but before I enter their Radar coverage. Same with my GCIs when their GCIs leave the ground outside my radar coverage. Is that correct? Also, do you know of a way to get the GCI messages to have pauses in them to let other messages come through? At the moment they are continuous and hog the message box. Thanks again.

Hi Stonehouse. Thanks for your script. I am having a little trouble getting things working. I have tracked it down to the following Debug message: C:\Users\...\Appdata\Local\Temp\DCS\/~mis00003088:295 attempts to access global 'mist' (a nil value) here's the line 295 if mist.DBs.zonesByName[redAFids:getName()] then I have used the Mission Start trigger to call up MIST.lua (I renamed the version title to generic MIST in case the version changes). Can you tell me what may be wrong? I'm attaching the .miz, file and lua's in case they help. Korea_Late_51_GCICAP.miz Korea_Late_51_GCICAP.lua MIST.lua

What actually goes wrong?

Thanks Capt Zeen, works fine now. One minor observation, the slip ball sits slightly to the left, just touching the line, no big problem. Nice to have the Compass and Horizon-Cage knobs working. I assume the other switches etc aren't meant to be animated? Thanks again.

Aha! dcs.log tells me: 00059.828 ERROR Lua::Config: Call error LuaExportActivityNextEvent:[string "C:\Users\Dad\Saved Games\DCS\Scripts\Export.lua"]:1460: attempt to index local 'myInfo' (a nil value) stack traceback: [C]: ? [string "C:\Users\Dad\Saved Games\DCS\Scripts\Export.lua"]:1460: in function <[string "C:\Users\Dad\Saved Games\DCS\Scripts\Export.lua"]:1452>. and line 1460 in Export.lua says: if myInfo.Name == "P-51D" or myInfo.Name == "TF-51D" then Which seems to hang together..... but I don't know what it all means :( EDIT: I forgot to say I do have other export.lua's, the one referenced above plus the one in Program Files\Eagle Dynamics\DCSWorld\Scripts\ which I believe isn't used when there's a 'Saved Games' one available and the one in Program Files\Eagle Dynamics\DCS World\Config\export\ folder.

Thanks CaptZeen, looks beautiful,it releases my instruments monitor from DCS graphics and gives me 20% increase in fps. One problem though. It works fine off-line (Instant Action) but I can't get it to work on-line. I have tried starting the Profile before and after starting DCSWorld before then selecting MP. I have tried starting the Profile, then going directly to starting DCS Multiplayer. I have tried starting it off-line (works ok), then Escaping back to main menu and then going to MP where it doesn't work. I also tried two different servers. In all MP cases the instruments stay frozen at their 'Start' positions. Is there something I should be doing for MP use? Sorry for the questions.

Come visit. http://www.tangmere-museum.org.uk/

and the Canberra..... https://www.facebook.com/TangmereMAM/app_190322544333196

I hope it's acceptable to post this here:- https://www.facebook.com/TangmereMAM?ref=br_rs See the aerial drone video of the museum and the remaining half of the old airfield plus the Canberra B2 and the English Electric Lightning F53 / F6 cockpit panoramas.

I can only tell you that I put the mod package in the DCS World subfolder I made called _MODS per the instructions at step 4. When I opened JSGME I didn't get the welcome window shown in step 5, just an empty JSGME window. I had to "Tasks...Import" the mod pack by pointing to the DCS World _MODS folder. I can see what has happened. On importing it has transferred the mod pack to the JSGME MODS folder leaving the DCS World _MODS folder empty, so I suppose I should have placed the mod pack in the JSGME MODS folder in the first instance and not in a DCS World _MODS subfolder.

I don't know if this has already been said in the huge number of posts here but I followed the OP's instructions in post one and found one discrepancy. Having installed JSGME and made a _MODS folder I made a snapshot. I unzipped a mod package to _MODS and opened JSGME expecting to see it. In fact I had to go to Tasks... Import mod.... and browse to the /_MODS/[ModPack]/ folder before JSGME would see it. Perhaps the OP needs amending?

Or this. JSGME not required. http://forums.eagle.ru/showpost.php?p=2344534&postcount=10

This is precisely the question I wanted to ask. Notice in the video how the camera is focussed at the instrument panel which is about the same distance as the canopy. In fact we focus beyond the window pane, or canopy in an aircraft - you can do this in your car. I wonder if the graphics are somehow interpreting this issue incorrectly. The Mustang is bad enough but the Sabre is not only covered in reflections, it is mottled and streaked too. Hard to believe you'd send a man into combat with that disadvantage. Anyone here flying that can look into this in a pragmatic way? EDIT: I meant to attach examples. The Sabre problem is obvious. The Rapide view - although different lighting circumstances and a flat glass - has the camera focussed beyond the window. The reflections are no-where near as intrusive against the landscape and as someone pointed out, our brain seems to be able to filter the problem out in RL. EDIT2: Over the weekend I sat in a Hunter cockpit. Although the light sources are only large fluourescent lights there is a definite difference between looking AT the reflection on the canopy and looking through it.

Brilliant! That's five different views with the original. Will we hot key between them?

Excellent. Thank you.

Thanks Capt_Zeen, can't wait. :thumbup: I have Helios installed but I'm really a Helios virgin. Will it just be a case of unzipping files to locations or will we have to do something in Helios to 'install' it?

Hi Capt Zeen, well I've decided to move away from four screens due to the fps hit and am now just using the three surround screens. So like many others I am really looking forward to your P51-D panel for instruments instead. Many thanks for this. A couple of questions, although I wouldn't want to delay things. Are the startup switches active and, if so, is it possible to add the Generator and Battery switches (for the start-up routine)? Anyway, looking forward very much to this. I saw your recent web news that it's very advanced. Any idea how long it will be now? Thanks again

Don't want to drag this OT but look under Options.... General. The keys are RCtrl + Pause. I find LCtrl+Pause also works.

Current patch. Mission 7 no problem. Don't get fussy. 46" MAP, 2700rpm, Auto Rads. Just remember to maintain 46" MAP as it drops off in the climb to 20,000ft or you may end up low and on a go-around. Oil temp approached red line during the early stages but spent most time in the green as did engine coolant. Fly easy, steady climb, keep speed >= 170. Was 200+ much of the time.