MemphisBelle

yep, that is the solution I´m using at the moment and it works as very well. This thread is looking for alternate solutions and of course asking ED to add new features to the ME. Generally, I´m like you and try to maximize the ME possibilities.

awesome Pikey, Your suggestion may not be a no-script solution but it is nonetheless exactly what I was looking for, I still hope that ED will consider adding features to the Editor so that more randomized Mission can be created. But with you suggestion, I´m having something good to work with, thank you.

Yeah I know, but not everyone has the knowledge to write own scripts Imagine the following scenario. A Huey is supposed to pick up Casualties from an Area. You don't want to spawn the casualties every mission at the same spot, that simply doesn't make any sense...it is fun the first time, but with the 2nd or 3rd run it gets boring. I´m using flags to make it happen to randomly spawn Infantry on 7 different spots and each time we fly the Mission the Inf spawns at another spot...or not at all. This is what I mean with dynamic ...not linear. It would be so much easier with an (OR) Option in the Action rule to make the game spawn the Infantry (to stick with my example) randomly. If you know how to make this possible by using a script, I´d be more than happy to use it :)

awesome, thanks...I´ll do that

exactly that´s what I´m referring to.

Whenever I try to create my missions dynamically to not have the same Targets spawn on the same position whenever the Mission is starting, I´m wondering why we do not have an [OR] Option in the Actions Section of the rules. It is, of course, possible to create dynamic spawn points by using Flags, but this will also create hundreds of unnecessary Trigger rules. It would be awesome to see if ED could bring this in.

sorry to hear about your issue, but this is the wrong forum for technical issues. From what I understand is that you haven´t set the axis properly, Try that again before climb into the cockpit.

Any updates on this Nineline? I was testing the Infantry at night (2.5.5 branch), and they are still blind like bats even when I hover right next to them with Nav lights and beacon lights on (Huey).

Ehhh, yes I have, we always fly with a blind map. I thought that the Gamemaster is able to see all units whether or not this option is activated or not. So the way as you ask me sounds like that the Gamemaster can see units only if they are not hidden. I was searching for Gamemaster in the manual and it is mentioning it with this: that's why I thought that he can always see the units no matter whether they are hidden or not...that´s an option that should definitely be added.

Hello, wasn´t it possible to see hidden units on the map when I´m in Gamemaster Slot? i´m sure I forgot to set an option or is it some sort of a bug. Last time I tried that position I was able to see every single unit, but now the map is blind as for the Pilots. Anything I can do about it?

Holy shit, I could kiss you hahaha only thing I had to figure out was now how to get the Weaponracks textured properly to make it look like this now: you wont believe it, but I had to use the tex_3 texture line twice within the description.lua and the file even twice within Textures AND Liveries [b]{"mi-8_tex_3", 0 ,"159th-HOOKERS-Mmi_8_tex_3",true}; {"mi_8_tex3", 2 ,"Mmi_8_tex_3_spec",true}; {"mi_8_tex3", 0 ,"159th-HOOKERS-Mmi_8_tex_3",false};[/b] Anyways, finally I got it to be working!!!!! I´d never have found this issue without your assistance...thanks a lot :) Do you know by any chance which files I have to editi to change the Cockpit color? The zip file in Bazar/World/textures does not contain any Cockpit Textures apart from the Night Cockpit Textures

Hello Grajo and thanks for your help. The problem is, that my description already looks like you said already. Did you checked the spoiler in my upper post? description.lua ivery = { {"mi_8_tex1", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_tex1", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_tex2", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_tex2", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_tex3", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_3",false}; {"mi_8_tex3", 2 ,"Mmi_8_tex_3_spec",false}; {"mi_8_tex4", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_4",false}; {"mi_8_tex4", 2 ,"Mmi_8_tex_4_spec",false}; {"pilot_MI8_body", 0 ,"159th-EAGLE-LIFT-Mpilot_MI8_PL_601_13",false}; {"ZSH-7", 0, "159th-EAGLE-LIFT-ZSH7", false}; {"pilot_MI8_patch", 0 ,"159th-EAGLE-LIFT-Mpilot_MI8_patch",false}; {"EVU", 0 , "159th-EAGLE-LIFT-Mevu_texture", false}; {"rotors_opacity", 0, "mi_8_rotors_opa", false}; -- Numbers Large On Engine {"mi_8_ENGINE_NUMBER_001", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_ENGINE_NUMBER_001", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_ENGINE_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_ENGINE_NUMBER_010", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_ENGINE_NUMBER_010", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_ENGINE_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_ENGINE_NUMBER_100", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_ENGINE_NUMBER_100", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_ENGINE_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Small Below Engine {"mi_8_SMALL_NUMBER_001", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_SMALL_NUMBER_001", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_SMALL_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_SMALL_NUMBER_010", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_SMALL_NUMBER_010", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_SMALL_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_SMALL_NUMBER_100", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_SMALL_NUMBER_100", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_SMALL_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Large Below Exhaust / Middle {"mi_8_BORT_NUMBER_001", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_BORT_NUMBER_001", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_BORT_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_BORT_NUMBER_010", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_BORT_NUMBER_010", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_BORT_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_BORT_NUMBER_100", 0 ,"159th-EAGLE-LIFT-main",false}; {"mi_8_BORT_NUMBER_100", 2 ,"Mmi_8_tex_1_spec",false}; {"mi_8_BORT_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Medium Forward Section of Tailboom {"mi_8_BALKA_2_1_NUMBER_001", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_2_1_NUMBER_001", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_2_1_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_BALKA_2_1_NUMBER_010", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_2_1_NUMBER_010", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_2_1_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_BALKA_2_1_NUMBER_100", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_2_1_NUMBER_100", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_2_1_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Medium Rightside Above Doppler Radar {"mi_8_BALKA_1_1_NUMBER_001", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_1_NUMBER_001", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_1_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_BALKA_1_1_NUMBER_010", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_1_NUMBER_010", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_1_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_BALKA_1_1_NUMBER_100", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_1_NUMBER_100", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_1_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Medium Leftside Above Doppler Radar {"mi_8_BALKA_1_2_NUMBER_001", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_2_NUMBER_001", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_2_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_BALKA_1_2_NUMBER_010", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_2_NUMBER_010", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_2_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_BALKA_1_2_NUMBER_100", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_2_NUMBER_100", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_2_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Medium Leftside of Tailboom ( before Stabilizer) {"mi_8_BALKA_1_3_NUMBER_001", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_3_NUMBER_001", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_3_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_BALKA_1_3_NUMBER_010", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_3_NUMBER_010", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_3_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_BALKA_1_3_NUMBER_100", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_BALKA_1_3_NUMBER_100", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_BALKA_1_3_NUMBER_100", DECAL ,"Mempty",false}; -- Numbers Small ( before Stabilizer) {"mi_8_SMALL_BALKA_NUMBER_001", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_SMALL_BALKA_NUMBER_001", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_SMALL_BALKA_NUMBER_001", DECAL ,"Mempty",false}; {"mi_8_SMALL_BALKA_NUMBER_010", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_SMALL_BALKA_NUMBER_010", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_SMALL_BALKA_NUMBER_010", DECAL ,"Mempty",false}; {"mi_8_SMALL_BALKA_NUMBER_100", 0 ,"159th-EAGLE-LIFT-Mmi_8_tex_2",false}; {"mi_8_SMALL_BALKA_NUMBER_100", 2 ,"Mmi_8_tex_2_spec",false}; {"mi_8_SMALL_BALKA_NUMBER_100", DECAL ,"Mempty",false}; } name = "159th EAGLE LIFT TESTSKIN" countries = {"USA", "FRA", "SPN", "NETH", "TUR", "GER", "NOR", "CAN", "UK", "ISR", "ITA", "INS", "AUS"} --custom_args = --{ -- [457] = 0.1, -- EVU off --} thats my overall problem. I´ve downloaded your SAR Skin and did as same as you did in that one and I still have no colored rotorblades. But maybe there´s yet an issue within my description which I simply not see.

Is it possible to solve this issue with this Rough/Metal Patch? I´m not yet able to test this?

hmmm, does noone know the reason why the rotorblades wont change its color? I´m adding a few more information here. description.lua 159th-EAGLE-LIFT-Mmi_8_tex_3

no, if you clear all bindings ingame then you wont be able to control anythings. Have you watched the Video in the first post? This explains it all actually. This program has absolutely nothings to do with DCS except that it simulates Keyboard inputs. Thats why its important to NOT delete all key bindings ingame. Lets take the key Combination for opening the Cockpit Canopy as an example here. Ingame Key-combination is right Ctrl + C. So if you just want to use one switch on your Joystick for executing this command, so you have to assign this combination in a profile. Make sure that RS Mapper will read out all connected hardware, then assign key combinations for certain functions according to the ingame controll settings and save this for this particular Module and voila...you´ve got your first profile. It´s then possible to use more devices in this Profile.

I´m here since LOMAC, but had flown the Flanker 2.0 before already. When LOMAC was released I had a crabby PC that could not run it which caused me upgrading my PC the very first time essentially. It´s been a great experience back in that time considering that I´m flying Simulators since the good old Commodore C-64 days. I joined a MP Group quite quickly and since then flew MP only. The Huey UN Pilot Campaign is the first one I ever touched actually

how did you make the Rotorblades wont fall back to the default color? I can do what I want, my Rotorblades wont change (cold Helicopter), even though the Rest of the Texture does.

Thank you Dingo_Bob, I found the Skinset that you´ve mentioned and downloaded it. I did everything as he did but the result is still the same...except for this...what are these yellow black areas? They look like streched missing Texture parts, but they belong to Texture files that are actually loaded...I dont get this System of Texturing in DCS...

Hello Everyone I wonder why parts of the texture are getting recognized while others are not...the yellow cover of the Weapon Pylon was just for testing purposes...DCS is using this part of the Texture file, but completely ignoring others (like the main rotor blades) of exactly the same Texture file...that doesn't make any sense. I don´t get why that is. The Tail rotor in example is no issue, works perfectly fine. Here the image again I´m speaking about I also I tried setting status to false already, this is what happens when I do so. does anyone has an Idea, I've no more anymore. I also have extracted the rotor texture liverie description.lua from MV2 and it didnt showed my another file than the one I'm using.

Sorry if this has been asked before, but wasn´t the A-10C now supposed to (finally) receive a Pilot body? I thought it would come with the new Cockpit. Are there any Infos around about this? apart from this, I like the new Cockpit very much. So far I´ve just tested in in VR and it looks great.

Well, thank you. I'm happy you like it and hope it serves you well.

I think you misunderstand the function of profiles. Once you single click S3 to change to another Profile, so that new Profile is a blank new one. Thus you need to create a new Button (S3) on that profile page in order to change back to the first Profile. This is how I did it with 3 Profiles on my HOTAS Warthog (Boat Switch serves as Profile selector) The middle Position is the "default" Profile which I simply haven´t renamed) and I need to move the Boat Switch in the forward position to change to my Combat Profile: To change back in to the default Position, I have to move the Boat Switch back to the middle Position To change to the Start up Position I have to move the Boat Switch into the backward position

Thanks for mentioning my Website. I´m gathering the Tutorial Videos on this page of my Website, seperated by language.

I pretty much assume he´s referring to AirCraft with ac/AC.

please continue all further discussions in this Thread: https://forums.eagle.ru/showthread.php?t=255909