Martyn

So here I am a few days later. I completed mission 8 on my 3rd attempt - that was many hours of hard work! But it was enjoyable. On attempt number two, after I dropped the 3rd load safely, I gently made a small circle-to-land to pick up the slings and somehow ended up in VRS by complete surprise and crash-landed in the field. I think, as I turned away from the wind, the slight headwind became a tailwind and the VSI dropped a bit, but as I was moving along the ground at some speed I thought I was safe from VRS and didn't compensate for the tailwind. Oops! Sadly, I think that was my first Mi-8 crash (not counting a few 'experimental' flights just to 'test the physics'). I even survived the whole Spring Tension campaign without incident. I think I've just been lucky - I've had a few close calls with VRS, be sure! :lol: Attempt number 3 was successful, though I did damage the 3rd load. Either dropped it at too high a descent rate or caught it on a previous load. But after all that's happened before, I will gladly take that result! I also had considerably more fuel left compared to my first attempt, where I landed by autorotation :D On the third run of this mission, the Mi-26 never left the base. It was creeping very, very slowly along the taxiway. It has almost reached the runway by the time I returned to base. Not sure what caused that. DCS issue I imagine? There were no updates since the last two times I ran the mission (I'm on the stable branch of 2.5.0). May explain why ATC never answered my request to taxi to take off - it was waiting for Mi-26 to clear first. One minor 'bug' to report / improvement to make: After I damaged the 3rd load, the scripts/messages didn't play out about landing to pick up slings, or asking the crew chief to get to collect them once I had landed on the pad. It worked all other times, including on the next load. It only didn't work after I damaged a load instead of placing it down safely. I was concerned it might stop the script sequence from running and result in the mission not being completable, but thankfully all was well. One more weird event: I blacked out several times due to G-loading, when the load 'bounced' on the rope! :shocking: (I thought DCS had crashed for a moment!) The G-meter showed -0.6 to 2g after the 'bounce' that caused it. Lucky the rope didn't snap! I was carrying the large fuel drum at the time, doing around 150km/h. Nothing campaign-specific, I'm sure. Just a DCS thing. A few screenshots attached: 1) Last load en route 2) Final to land - note the Mi-26 which was still taxiing to the runway after more than 2 hours! (Holding up other traffic) 3) Fuel remaining once parked on the stand. More than 0 = good :thumbup: All in all, great mission. But I look forward to moving on to the next one. I'm loving this campaign so far. Aside from the slightly poorly translated English briefings which can confuse at times, it's amazing, well done! :clap_2: I hope for more civilian campaigns in DCS in future; it's a nice change.

I thoroughly enjoyed this mission ... well, kind of. I had a few slow pick-ups and drop offs with a fair amount of hovering time. I've had a few months' break from DCS so no surprise, and flew missions 6 & 7 last week. So as time went on I was sure I'd be running low. On the final, 4th run, the fuel was very low and I had doubts about making it back. I didn't want to give up and be forced to do the mission again so I pushed on (hey, it's a sim!). As quickly as I could safely manage, I dropped the 4th & final load with no damage, then headed back to base into that cursed headwind. I watched the fuel gauge like a hawk all the way back. I knew it would be close but with a few miles to go I started to have hope. I also hopped the fuel gauge might go below zero, like it sometimes does in a car. Tip: it doesn't :noexpression: Making a low powered, gradual descent to the runway, squeezing every bit out of the fumes, the fuel finally gave out at about 50ft and a few hundred yards from the runway threshold - panic!!! :joystick: I just had enough energy in the rotors to keep it off the grass and made the runway - PHEW!!! :megalol: (For reasons unknown I went full UP collective after touchdown and not full DOWN, so I had a bit of a 'bounce'!) I rolled smoothly onto the grass and promptly screamed for the ground crew, who obligingly fuelled me up a little despite my 'unusual' parking spot. I restarted the APU, then the engines, and was ready to taxi back to the stand and complete this epic mission! Piece of cake! Breathe a sigh of relief... :thumbup: But ... the story doesn't end here. Taxiing on the grass is not something the Mi-8 seems to enjoy. After it finally got moving and I made a gradual turn, it started to tip over! I cut the collective (had to lift it a little to get moving on the grass) to drop the weight back onto the wheels and used the cyclic in the opposite direction, but to no avail... my workhorse wobbled and jumped a little and then rolled right over and ripped itself apart. Noooo!!!!!!!! :doh: :cry: Oh well, I'll be a sling load champion after doing that one all over again! But I am a bit frustrated that the fuel shortage wasn't the death of me; the long grass was far more deadly. It's a bit like dodging a SAM, only to be killed by a birdstrike soon after :D Three images attached: 1) Screenshot taken about 5 seconds before the fuel ran out. 2) Ready to refuel for taxi to parking 3) All loads delivered - but spot the wreckage of the Mi-26 in the background. Feedback/questions on the mission: From the mission description it sounded like transporting all 4 sling loads was optional, as it says "from 80 minutes to 2.5 hours", but during the mission it isn't really clear if this is the case? Certainly, the crew made no major complaints as the fuel started to run low, to indicate to the player that he/she might want to re-consider finishing early. I'm not sure how it's scored or what's needed for a 'pass'. Could there be a mission bug that causes the Mi-26 to crash? I'll have to see if it happens again when I play it. At some speeds with sling loads I found that the G-meter went crazy, fluctuating rapidly from around 0-2g. (The fuel gauge also jumped around, causing audio warnings; nice feature). The Mi-8 was also pulled around quite a bit even though the load wasn't really swinging. I tried not to go too fast with any loads (generally below 150kmh for the larger ones), but at times it was very jittery. Have others seen that behaviour? I didn't notice it before in v1.5.7, only now in the 2.5 release. But maybe I didn't take such heavy loads before. Thanks! Martyn

I finished the campaign yesterday and can only agree with your comments. The lack of a 'mission completed' message is not so helpful. I flew back to Shpora where I started, as per the mission plan, but noticed that flights 101 and 102, who I followed out to the target area, actually flew back to Skala where we were based for most of the campaign. If not for this thread, I probably would have taken off again and returned there too. Overall, it was a great campaign. The biggest frustrations were the AI helicopter's inability to anticipate hills, making the formation flights hard work. But that's a core game issue.

Yes, it's the one where you have to take the worn out old Hip for maintenance. Great idea for a mission. Immediately after picking up into a hover the generators drop offline due to the engines not being able to produce enough power. You have to quickly get into translational lift to let them recover. Interesting start! Next time I run low on fuel I'll bear in mind the taxi requirements. I flew the UH-1H campaign a year or so ago and had a couple of long missions that frustrated me greatly with failure right near the end, so I hear you on that point! As I very seldom go near multiplayer servers, the campaigns are a great way to get familiar with an aircraft. I'm not good at creating my own activities, so the campaigns can keep me busy. Though in the fixed wing campaigns I tend to find that I am straight in at the deep end and struggling to stay alive. The helicopters offer a more steady 'career' :)

I also thought all was going to plan, until I shut down and the story plot was revealed to me. I think the oil leak did trigger (at least it looks OK in the mission editor and it matches with the audio message I received in flight), but I can't say as I noticed any loss in oil. Never mind the oil, I was almost out of fuel by the time I reached Mozdok! I had to go around three times due to aircraft landing, two pairs of Su-25s and then a pair of Mi-24s. When I touched down and taxied in, the fuel gauge was a fraction over the zero line at shutdown. When I opened the re-arming and re-fuelling window, it said I was at 0% :shocking: Still, we made it, so on to the next mission!

I've just completed Mission 4, taking the old Mi-8 over to Mozdok. Spoilers ahead (obviously)! As we passed Beslan on our starboard side, I got a warning about the RPM not being stable on one engine: "CREW CHIEF: Commander, engine RPM is unstable. Mozkok may be a stretch." After that nothing else happened until after I landed at Mozdok and started to shut down. As soon as I reduced the power to idle and the generators dropped off, I got another voice prompt about generator failure and choosing whether to make an immediate divert to Beslan or not. Pretty pointless seeing as I was on the ground already :D Seems that a trigger didn't work properly... else some element of randomness is included and something happened out of sequence. Looking in the .miz file and the text entries, there's talk of fire! Seems I got lucky :thumbup: This text never appeared during my flight, I expect it should have followed the earlier text: "CREW CHIEF: Commander, left engine vibration warning! No way we'll reach Mozdok the way things are going!" I had a quick look at the triggers in the mission editor and see a 100% chance of an oil leak, followed by another event 25 seconds later (listed as RPM regulator failure), but it looks like there could be a missing definition of what failure should occur? Perhaps a failure type was renamed in an update and now the mission is slightly broken. (And in the debriefing screen, I only got 60 points instead of 100, for whatever reason - not that it's important anyway). I haven't really tried to unravel it and the ME is not something I'm particularly knowledgeable about, but I have attached a screenshot showing the potential missing failure type - see right side where it's written: "!!!NEVER USED". I may be off the mark and the issue may lie elsewhere. Great campaign so far. So glad to finally be putting some decent time into the Mi-8 which has been on my waiting list for some time. Thanks, Martyn

Thanks for the reply, Bignewy. Of course, it should be a simple fix, but for whatever reason, it isn't. Or rather, wasn't: I finally found a solution as described below. This is DCS 1.5.7. Last night it was updated to the very latest version, though it didn't change anything with the behaviour since March when I last tried. I re-ran both the A-10C and Hawk "_protect.exe" files (as administrator) and deactivated both modules. I'm down to 4 deactivations left on the A-10C as I have tried many times already. I then manually deleted the whole registry entry for these two products. I could only find them under 'current user', not under 'local machine'. So, with the registry clear, I fired up DCS and looked in the Module Manager. The modules were still listed and showed a checkmark, and the serial numbers were still present if I clicked the 'serial number' sections, but I figured those were being loaded from my profile (same as if I log in on the DCS website). When I clicked the 'bin' icon to remove the modules, the DCS updater briefly ran (and requests admin rights), but after DCS reloaded the modules were still there - nothing changed. (I've tried all of this before and then reactivated them, to no avail) As mentioned, the icons were strangely missing from the modules list along the bottom of the home screen. I saw everything except the A-10C and Hawk... (I think). So I decided to focus on this aspect of the problem for a change. I went looking for log files and found this the dcs.log file under C:\Users\<username\Saved Games\DCS\Logs: 00000.644 ALERT SECURITYCONTROL: Manifest 'mods/aircraft/a-10c/dcs_manifest.x86_64': wrong manifest_token 00000.671 ALERT SECURITYCONTROL: Manifest 'mods/aircraft/hawk/dcs_manifest.x86_64': wrong manifest_token <snip> 00001.486 WARNING DCS: No update_id in manifest for ./Mods/aircraft/A-10C 00001.486 ERROR Scripting: plugin: A-10C Warthog by Eagle Dynamics unit modification A-10C not allowed 00001.486 INFO Scripting: plugin: A-10C Warthog by Eagle Dynamics skipped, not authorized 00001.489 WARNING DCS: No update_id in manifest for ./Mods/aircraft/Hawk 00001.489 ERROR Scripting: plugin: Hawk T.1A by VEAO Simulations unit modification Hawk not allowed 00001.489 INFO Scripting: plugin: Hawk T.1A by VEAO Simulations skipped, not authorized 00001.509 INFO Scripting: plugin: A-10A by Eagle Dynamics disabled by Flaming Cliffs by Eagle Dynamics 00001.509 INFO Scripting: plugin: F-15C disabled by Flaming Cliffs by Eagle Dynamics 00001.510 INFO Scripting: plugin: Su-25A by Eagle Dynamics disabled by Flaming Cliffs by Eagle Dynamics 00001.510 INFO Scripting: plugin: Su-27 Flanker by Eagle Dynamics disabled by Flaming Cliffs by Eagle DynamicsLooked like some minor modifications to the aircraft folders may have simply blocked those modules? I do recall doing something with the Hawk cockpit textures long ago, back when the menu option for Low/Medium/High quality didn't work causing High quality textures to always load (which my PC didn't like). About the A-10C I don't recall changing anything except perhaps adding a new livery, though from memory that would go in a different place. I've previously done a repair so I'm surprised the 'bad' files were not overwritten. Anyway, I simply deleted the whole aircraft directories under 'Mods'. When I ran DCS, the aircraft icons returned to the bottom of the main menu screen. Progress at last! The Module Manager has a little '2' next to it (much like a smartphone app) and when I clicked it, it told me I could now install those two modules. I clicked OK, let the installer run and reactivated the modules with my serial numbers. Now all is working! So it was never an activation problem in the first place, it was a module problem. But far from an obvious one... :huh: Thanks for the help. Thought I'd post my troubleshooting steps in case they can help someone else in future. Edit: Just saw your 'cleanup' video linked in your signature - perhaps that would have solved it too!

Hello All, Several months ago I made a fresh Windows 10 install onto an SSD, to replace the in-place upgrade to Windows 10 that I had originally. Around March, I installed a fresh copy of DCS 1.5 onto this new SSD, but to save lots of downloading I copied across much of the directory to the new drive. (Since it was some months ago, I can't remember exactly...) Most of my modules successfully activated and are working fine, but the A-10C and Hawk are being stubborn and refuse to work. I last battled with this in March and gave up; now I'm trying again. Things I've attempted, based on other threads I found back in March, are: Running the xxx_protect.exe program in the Mods\aircraft\name\bin folder as administrator, deactivating/reactivating Deleting all folders containing serial numbers information in the Registry, under HKEY_CURRENT_USER\Software\Eagle Dynamics\... Repairing DCS World Deleting an aircraft folder and then repairing All to no avail. Any other ideas? I'm completely at a loss! In the DCS main menu, under my profile it shows that all the modules are installed and active, however I do not see any icons along the bottom of the screen for the A-10C or Hawk - neither greyed out (as if I don't own them), or in colour (as if I do own them). They are completely missing. These aircraft also do not appear in the Training menu, unsurprisingly. Thanks for any pointers. It might have to be a full DCS reinstall though I'm not convinced that will solve it either.

Thanks for the input both. I've tried a few more things. I moved my DCS directory to my SSD (had only Win 10 and FSX on there till now), except for the MODS directory so I could re-download my aircraft. Then I ran the repair utility. Also deleted all keys out of the registry. After trying to get a couple of modules running, I found that the A-10C would work but not the Hawk. Since DCS wasn't really 'installed' in the new location (the path didn't match the original path), I decided to make a full reinstall anyway. I had still got a copy of my 'old' DCS directory (pre new OS installation at Christmas) which I renamed so it matched the old path, then ran the uninstalled via Control Panel. Next I made a new install onto my SSD, but to save a download I only deleted the root files and 'bin' folder contents. This was enough to allow the installer to run and re-download the missing files. Now I have an 'almost' clean install. Having signed in, in-game, I am prompted to download all my aircraft based on my account log-in. Doing one at at time, I have the A-10C and Ka-50 working, but the Hawk is still a no-go. I'll continue on with the rest now... and report back the end result. A DCS reinstall is feeling like the new FSX... more time spent tinkering/fixing and less time flying :doh: Update: All modules except for the Hawk are now working. I clicked the in-game DRM button in the Module Manager and it activated (didn't ask to re-activate), but it still doesn't work. Ultimately, putting my DCS install in a different location seemed to be enough to fix the problem for the other modules, but to avoid any possible future issues, the full reinstall was the safest option. At least a complete re-downloaded wasn't needed. For now I'll just ignore the Hawk...

I've no suggestions, but I have exactly the same problem as you. I made a fresh install of Windows 10 on to an SSD at Christmas. No other hardware changes. I don't recall deactivating my DCS modules beforehand but have 8-10 activations left on each. It's been a few months since I first installed DCS on the new OS install but I believe I copied the whole 'MODS' folder across to the new install, to save lots of re-downloading. Since then I haven't actually flown any aircraft, but today I find I can't get into the cockpit of anything except the free aircraft. So far I have tried: Deleting registry entries based on the info here: http://en.wiki.eagle.ru/wiki/Problem_with_Activation, then reactivating the modules. No joy. Running the xxx_protect.exe as administrator in the 'bin' folder of each module, and trying to re-activate there. Each module said it was already activated, but I chose to try activation again. It said it was successful, but my problem remains. Running the xxx_protect.exe file and deactivating a module, then reactivating it. Same problem. Clicking the 'DRM' button in the in-game Module Manager and making the same changes from there. Nothing. Edit: Also tried to repair DCS World several times after making various changes. No help either. Aside from deleting the whole installation and starting all over again, I'm fast running out of ideas... :( One would have thought this kind of thing would be quite simple in this day and age. I guess copying old files across isn't taken care of in the DRM applications. Next I'll try deleting (renaming) some files... Martyn

Good luck all!

Thanks for running the competition! Yet another dawn patrol...

I want Nevada. Thanks for the giveaway and congrats on 1000 subscribers!

Thought I'd still post, on the off chance you mean the full release of 1.5 instead of the Open Beta. You never know! If not this might win the title of shortest contest ever! :D EDIT: Oh wait, I only had to go back one page to see the winners announced. Congrats to all!

Apologies for digging up an old thread, but I just ran into this problem and I wondered if any solution had been found? A couple of weeks ago, I added a few MiG-21 slots into Dragon's Weapon Training mission (v4) and hosted a game without trouble. Last night I hosted the same mission and found that the frame rate dropped to 2fps as soon as DC power was applied in the MiG-21. The only thing that has changed since the first time hosting and the second time was that I increased my RAM and had to re-activate the MiG-21 (but no other modules). Singleplayer is fine as noted earlier in this thread. At that time, I ran into trouble with the re-activation and had to run the .reg fix to deactivate the module before making a fresh activation. In case this frame rate drop could be related to the reactivation, I thought it was worth adding to the thread... ?

Not sure if that was at the OP or me (guess either of us), but unfortunately I didn't get time to try changing any settings yet; haven't been near DCS all week. Interesting tip, Rider - will the server.lua affect all game modes and aircraft, do you know? It's currently set to 140 max and the wide-angle view feels more like 180 from memory. I'll try it when I can anyway. (Trying things out in DCS is never a quick affair!)

That's a good question, and now that you ask it, I realise I would like to do the same as the wide angle view is far too wide! :) I also have no view.lua in my Users folder (not even a 'View' folder in my 'Config' folder), only one in the main DCS folder. Is it safe to assume that if I copy the file (or any file) to the same location in my user directory, the game will read that version instead? Game location: D:\DCS World\config\View\View.lua Proposed user location: C:\Users\{username}\Saved Games\DCS\Config\View\View.lua That said, this file only seems to determine the external view setting, not the cockpit setting: ExternalViewAngleMin = 3.0 ExternalViewAngleMax = 170.0 ExternalViewAngleDefault = 60.0 I found some views.lua files in the aircraft directories, but not for all aircraft. I can't find one for the A-10C for example. For the Mi-8 it looks quite straightforward with the views.lua file: ViewSettings = { Cockpit = { [1] = {-- player slot 1 CockpitLocalPoint = {3.916, -0.11 , 0.0}, CameraViewAngleLimits = {20.000000,160.000000}, CameraAngleRestriction = {false,90.000000,0.400000}, CameraAngleLimits = {140.000000,-65.000000,90.000000}, EyePoint = {0.090000,0.000000,0.000000}, limits_6DOF = {x = {-0.200000,0.400000},y ={-0.200000,0.25000},z = {-0.650000,0.400000},roll = 90.000000}, Question is, can this file also be copied to the Users directory under the same folder structure? On a side note, I feel the lateral 6DOF movement on the Mi-8 is not enough, especially with the bubble side windows. I should experiment with the 6DOF setting above for the x axis and find a new setting, albeit with the risk of clipping the geometry or seeing 'holes' in the model.

I want a Hawk

Fair point Yurgon, certainly worth your €0.02 ;) From a mission designer's point of view it's sensible enough, and not every factor or eventuality can be taken into account, nor every 'max collective' requirement tested easily to ensure that troops don't board when you're still flying, so I can't complain too much. I had no trouble like this until now so it's just a factor of the high weight and stressful combat environment causing me to keep the collective halfway at the ready. On my first failed attempt I actually moved 100 yards from the smoke right up to the troops and landed again, before eventually shutting down out of frustration before quitting. They still didn't board despite zero collective, but I think that's because I was too far from the green smoke at that point, outside the trigger zone, ironically! Anyway, lesson learnt. Collective must be <20% for pick-ups in the campaign. Now I know! :smartass:

Eventually found time to refly this one. Indeed, once collective was lowered to almost zero, they boarded immediately... :doh: User error :D Given the severity of the situation, that's a slightly daft trigger check, especially when 70+% collective is needed to hover at the weight & altitude you find yourself. A lower value of 50% or less might be better. But anyway, the mission has been completed, even if my two gunners and main pilot were killed by the enemy group that spawns as you lift off, forcing me to fly home as Pedro the co-pilot - doesn't seem to have impacted on the campaign progress (thankfully! I'll forgive the small immersion loss so I don't have to fly this one for the 4th time!).

Seems that in 1.2.11 and 1.2.12 this mission is broken. I've had two attempts at it, and after all the excitement and tension of providing a little CAS, I always find that the Whiskey team won't board the Huey, so at this point all the tension turns to frustration! In 1.2.11, they retreated back towards the stream, reported having the stream in sight and said they would pop smoke shortly. Nothing further happened, even if I landed right on top of them. Now in 1.2.12, I re-ran it and the same thing happened, only they made one more radio call to say they'd popped green smoke, which they did, but landing on or near the smoke, or near the team themselves triggered precisely nothing. Won't board. I've only dabbled with the Mission Editor and learnt the very basics, but at a glance I see they have no board or embark action on their final waypoint, is that correct? See attached image. The other triggers and checks appear to make sense from what I can make of them. That said... well, I just found a check for a cockpit argument between min of 0 and max of 0.2 - I'm guessing that's the collective? See second image. I didn't fully lower it on landing, since near-full collective is needed to hover at that altitude & weight and I wanted to be ready to go as I was landing under fire. If that's the only reason I can't complete this mission, I am kicking myself!!! As fantastic as this Huey campaign is, it's taking me forever to complete it as I keep abandoning it due to missions that don't complete. The price to pay for continual DCS updates I suppose :) Thanks for any input to either fix the mission, or tick all the boxes so the conditions are met.

These odds are better than the lottery (which I would never play). Thanks for running the competition!

Yes, the nav test was an adequate challenge, especially the second part which required some close referencing of small map features. After years of flying IL-2 and FSX, I'm reasonably good at map-reading and dead-reckoning. It could be made harder with even more vaguely defined points to find, but there's a fine line between challenging and hugely frustrating :) In terms of further development, I can only think of randomising the nav test by having a few different routes, although it would be quite some work to prepare and if you were given the same one by random a couple of times in a row, you might not go back for more. Alternatively, maybe include landings in relatively small places (car park of some key building in a city, or on a bridge for example) as part of the nav test. Again, it might be difficult to do - can DCS recognise when you've touched down on a 3D object as oppose to terrain? - and the buildings are so generic that finding the right landmark could be tough. Just food for thought, anyway. It's a good mission with a nicely rounded set of tests. Some kind of landing check/test might round it out completely, or perhaps landing tests are a whole other mission to make! :D

Alright, I flew the mission and came back in one piece! Bearing in mind it's only my second flight Mi-8 flight in the last 6 months, and that I never put more than a few hours on her in the first place, I ended up like this which is satisfying enough for me: Hover: 38 / B Orbit: 26 / C Nav: 47 / A And I feel those scores are spot on, based on my self-assessment as I was flying along. The hover wasn't bad but plenty of room for improvement, the orbit was sloppy but I was confident that I was within a few tens of metres of the nav checks. I was doing more or less okay at hovering, but waiting an age (well, just over a min) for something to happen. Turns out I hadn't climbed high enough to start the test, although looking down at the guy on the runway, I felt I probably was high enough. I daren't jump to the external view as that would have ruined my hovering completely, but eventually the test began with a message after I drifted a little higher. Maybe a time-delayed message about climbing might help there for anyone else who's a bit too low? The orbit was difficult! I think I didn't come in at quite the right angle due to a slow turn to the 50° heading, so as soon as I crossed the green smoke I was too close to the centre, but that's more my problem / lack of planning. I then lost sight of the central smoke plume for much of the orbit out of the right-side window and was relying on the too close / too far guidance messages to try to keep me on track! A left-hand orbit would have been easier due to better visibility, but it wasn't designed to be easy I think :D (I suppose I could have switched to the co-pilot seat in hindsight, but where's the immersion in that?!) I noted the hover check had an option to retry by waiting around. I wonder if the orbit could have the same option? I feel it's the one area I'd want to retry a few times. The nav check was good, enjoyed that. Although trying to read the map whilst leaving the chopper in a semi-trimmed cruise is always a scary prospect! Overall, the mission ran nicely. Messages nicely timed and spaced and on screen plenty long enough to read. The scoring was well implemented. Took me 44 mins in total. My eyeballs were shaken to pieces though as I kept on overspeeding during cruise! Good work and thanks, Hobbnob! :thumbup:

I'll give it a go shortly and let you know if I end up with any points, thanks :smilewink: Perhaps add the link to your original post though (or hyperlink the image), even if it isn't at all hard to find! http://www.digitalcombatsimulator.com/en/files/1072206/