Weegie

Can you tell me what half a + length means in terms of percent or something? I don't understand what "half a + length" means I'd like to get a replacement washer, as I'm currently using the stick without one. I doubt there will be any wear to the stick, despite warnings otherwise as without the washer there will be a gap. However I think the purpose of the ring/washer is to help seal the mechanism against contamination so its better if one is installed

Ok Ok its Off Topic but that's great to hear When I mentioned the lack of axes for the Hawk VEAO stated it would be in the next update, I think that was about 2 updates ago With the Main Controls screen I've not had any problem up until now EXCEPT if trying to do changes to more than one aircraft at a time. Doing multiple changes to different modules and its almost a guarantee crash for me This problem was solely trying to change one axis in the Viggen. It may well be generic to all the Viggen axes since the last update and not to this mod. I haven't tested that hypothesis, it was just by coincidence that it happened to be an axis added in by Franky & not one of the very limited set provided in the Beta for the Viggen I tried it in both Beta and Alpha and it crashed both times

Hi Franky I don't know if anybody else is getting this or not I love the mod as it enables me to map so much more, but I came across a peculiarity with it in the latest game updates All the existing mapped controls were/are running fine When trying to map a new axis to the instrument lights in the controls on the main screen (the gear cog symbol at the top) it takes the axis and its recognized when I check in Axis Tune but the minute I exit the controls screen DCS crashes. It does this for any new mapped axis to any device. However if I go into the controls when in a mission using the escape then choosing the Adjust Controls option, it works fine If I then go back to the controls on the main screen the updated axis is there and all is good Just thought I'd post up in case anybody else was encountering the same thing Fantastic work by the way, many, many thanks for the mod......................You don't happen to own the Hawk module by any chance? :music_whistling:

There was a thread on Autothrottle somewhere in here already and the consensus was YES!! It will kill or try to kill you unless performing a perfect by the book landing in VFR. Personally (and I'm a crap pilot) I found the lag too long and it is reacting to the physical orientation of the aircraft. So it's always better for the pilot to control the throttle as he knows what he is about to do, or has done and can place move the throttle accordingly to account for it. The autothrottle has to wait to receive the input before reacting. I do find it handy for loitering or holding aircraft speed when busy with other things eating doughnuts, drinking coffee etc: Regarding the slave I'm still waiting to understand that, I think you place the HUD to SLAV but I'm not really sure what that does

I've not tried using either of these greases on a throttle yet as I've not encountered a problem, but I have used both of these on a stick First is Tamiya Cera Grease, Boron Nitride grease for model electrical motors, plastic friendly. A lighter grease, it worked well on a Hog stick but won't last so long. If you're not wanting a heavier pull and want to make the movement light. Second that many recommend here and works great in my Hog stick at the moment is Nyogel 767a Damping Grease, a sticky heavy viscous grease. Works great on the Hog stick giving a heavy almost Hydraulic feel Dunno if that helps or not

The minute I posted that image up I thought GOD!! is that my key. So I checked and its not, it's probably some encrypted variation on it that enable Starforce to determine the key but it's defo not my key Thank's a lot though for the advice and concern, it's appreciated

So I updated to the latest Alpha 2.0.5.3140.194 I'm getting this So I'm guessing here that the next Apha update will include the patch, as it states that once the deactivation/reactivation is completed in the Beta it is not necessary to do it for the Alpha. Looks like there won't be MiG-21's over Nevada for a week or so

Should add that I did deactivate/reactivate for the Beta & I'll probably not fly in NTTR at all until I can get an answer It all seems a little confusing to me......................but I'm not the sharpest tool in the box

Hi I haven't went into Alpha for a while but when I did today I've got an updated alert to go from 2.0.5.3140.194 to 2.0.5.3521.198 Now I'm confused about what I should do with the MiG-21 Deactivation/Activation. For the moment I'm not going to install the patch until somebody on here can tell me if this patch is the one that requires to me to deactivate/reactivate or if the relevant patch that requires this action is still to come for the Alpha

No apologies necessary mafuasu Many thanks for the tip, I'll go back to the manual and check it then try to engage TILS earlier and see how I get on Many thanks for the reply

Thanks for the reply, I should have been clearer I have the master selector in Landing Mode, with the sub mode Nav selected, i.e. the first of the 2 available Landing modes Sometimes I get a TILS lock but most often I do not, so it does work but it's intermittent

I've been flying Sgt Cyanide's simple bad weather TILS mission into Senaki, I have tried both auto TILS selection and also setting the TILS for channel 12 (Senaki) and I do have the 11-20 selection switch in the right place. I usually go to Nav on master selector on turning to the landing waypoint at around 1000m and about 20-25kms out. I always see the radar screen indicating the airfield but quite often I don't get a TILS lock, or receive any HUD guidance. Am I missing something or am I executing (or not executing) some procedure I need to get TILS to function reliably?

I'll be interested on the HUD slave answer too as it has me foxed Nav is for TILS (ILS) P/O is for visual approach TILS light is on the RHS panel quite far back as I recall. It flashes when selected but you do not have a TILS lock & is solid when you get a lock I asked about this before and another member, Sgt_Cyanide, gave me a link to good video Apologies if you have seen this before, he also has link to the mission which is a TILS approach and quite fun. Link to mission is here https://forums.eagle.ru/showpost.php?p=3039643&postcount=14

Mea Culpa, using an old version upgraded 7 zip and I got it to extract no problem Many Thanks for the mod and for assisting my dumb old ass :thumbup:

Could be me, tried twice same thing I tried to download & got 1.9Gb file (it states 2 in your drive) but when I extract the 1.9Gb file using 7zip it tells me it's not a valid archive Any clues???

This looks very nice So I have the FBM Mk III with an extension which I think is great Am I correct in thinking if I ordered the stick and 3 pin to 5 pin convertor it would work with my existing set up including the analog axis on the hat/hats A second question can both hats function as axes or is it one or the other?

Looking great & a very neat job What is the brake? a motorcycle or bicycle lever? Hat's off to your skill Goblin

SWEET!! Thank You Jack

Thanks for the hard work It's a really nice skin

Thanks for the advice Dirk I use OVGME and disable any mods before an update so the wiping is not an issue for me I never knew that the liveries would only show for module owners if the liveries are placed in the mods folder, useful. Yeah the reason they were placed in there was initially when the Mirage came out you could not use the Bazar folder. Now that's changed I'll transfer over in OVGME

Well I'm not going to argue with the skins creator, just glad you shared it The path comment was just to ensure people checked it and didn't just place it straight into JSGME. With JSGME I suppose it depends how you have it installed, but I agree it could be either way Could not agree more on the storing of livery files there are several places to store them and it can vary. Example I have my mirage liveries in the path Mods\aircraft\M-2000C\Liveries\M-2000C A bit crazy Thanks again for this wonderful skin DirkLarien

Ok I got a PM from Pawel, a new member who cannot yet post on the forum and he informed me of how he got the skin to work I also tested his solution and it also works for me. It would appear that the description.lua file has somehow got corrupted, perhaps by hidden characters, as the content of the file itself is correct. So the work-around is to open the description.lua file in Notepad++, I recommend using this free editor as it will not introduce hidden characters, or corrupt anything Copy all the script from the description.lua and then paste the script into a new blank file. Rename the new file description.lua and replace the existing in the folder with the the other 3 .dds files and it should now work The folder file path is also not quite correct. If using the skin with JSGME or OVGME. The folders Eagle Dynamics and DCS World should be omitted. Lightning2000C by DirkLarien\Bazar\Liveries\M-2000C\Lightning2000C by DirkLarien\ Easiest place to put the skin is to simply take the the folder immediately above where the files are and place it into the Username\Saved Games\DCS*\Liveries\M-2000C folder** * or DCS.openbeta or DCS.openalpha as appropriate ** If the folder is not in the Liveries section just create it

No I think its something to do with the description file I tried just taking the final aircraft skin folder and placing it into the Saved Games/Open Beta/Liveries/M-2000 The skin title shows up but when you select it, nothing happens Likewise if you go run the Mission File then you see another skin Again thanks for trying, gotta be something small only I'm not educated enough to see it

Please no apology is necessary, I'm indebted to you for producing this wonderful skin & who knows what the problem is could be me, could be the update, or just a simple error I'm no expert but I'll take a look at the description.lua and see if I can see anything. Anyway what's a few more days, once again thanks for taking the time