Sarah

what sorta cost did that whole setup run Raisuli? its gotta be up there... What about upgrades / features additions like JHMCS contrast controls etc...how do you cater for those?

Ihave found the shipboard Tors (SA15) on the rooskie DD and frigate fire very consistantly at 14.8 miles at anything below (at least) 14000'....buggers don't miss either when they fire 4 at once

btw.... I looked at the description.lua in the Core Modules folder as a reference, expecting that to kinda have every part and face specified but that didn't help me one little bit

I am having significant problems applying my skins to the F5 due to the dynamic numbers still being overlaid on my skins. The skins are visible for nose, tail, rude, and wing files, so that's working fine, however the dunamic numbering, specifically on the nose and rude are being splattered all over my lovely paint. Can someone provide a list of the part and face numbers I need to specify in the lua to control what is, and isn't, displayed on this plane please? Yes, everything, including skins layers and part names :) Right now, the skins are displayed using : {"F-5E3_nose", 0 , "<user file name for nose skin>", false}; etc for nose, tail, rude, and wing whats the trick for these positional parameters and part names for this specific aircraft to prevent "corruption" by dynamic overlays? if anyone wants to see my description.lua and dds files so they can try and emulate the problem, just let me know and I will zip em up here.

oh..yes….the country is USA...yet the plane loaded in game, has Russian markings..go figure.

here is a picture of the skin as it appears in mission editor screen http://prntscr.com/k8mh5b and here is what I get when I actually run that mission, in that plane... http://prntscr.com/k8mi5a pic showing drive path, folder contents, and description.lua on the one screen http://prntscr.com/k8mj5n

the problem is getting the mark point ON the target.... it just moves far too erratically / far with a merest touch on the hat....especially targets in semi obscured positions

The aiming reticle in the A10 for mavs etc I have set to a HAT switch...is there any way to decrease the sensitivity on those HATs, because if trying to lock onto a tank at say....7 miles, I find it jumping past and locking on the ground...or similar....and the closer you get, you have to rush...and its dang near impossible to get a lock on or launch more than one Mav in a pass.

This may be caused by my own skin and lua file inadequacies, but thre IS a bug that it highlights where, in the mission editor loadout screen, when I select my skin, it shows in the small window with the rotating L-39C in it. If I then load the mission, the skin ON the plane is completely different (camouflage, no country markings) and I Cant switch it to the one I want (it keeps just showing the no markings camo). Can provide lua and dds files if required.

yes, one machine.... if I load the mission from inside the mission editor, in the same session even, the plane that appears in world, and the one that appears in the mission editor small window on the loadout screen, are different. Let me go back to basics here.... Current situation : Skin installed in my user/Saved Games/DCS/Liveries/L-39C folder. Description.LUA is a direct copy of the one used for the Black Shark skin. My skin name is the same name as the Black Shark one, and in the same directory as the description.lua. If I go into mission editor loadout screen, the skin appears in the drop down box, and when selected, the small picture of the plane, shows the correct skin. I save the mission, "play mission" from the editor directly...or play it from the DCS main page, the plane that appears in world is completely different (yes, its not eve the black shark skin, but a plain one with no markings).

ok..I have the liveries for the L-39C in my user/saved games/dcs/liveries/L-39C folder. If I Am in the mission editor and assign that skin to a unit through the loadout screen, I see it perfect. If I then load the mission, the plane is actually a completely different skin.

I installed those and they work fine...BUT.....if I simply replace the DIFF file with my own...guess what? the texture doesn't change....even with the old texture gone, DCS keeps using it.

oh..that could be tricksy...whats with that DCS.openbeta folder name..is that because you have dual installation, or an automatic name...I am running the updater that flips stable and openbeta… should be irrelevant though, since I put all my mods directly into my DCS World/Bazar/Liveries/L-39C folder. Its still being flakey though...frustrating

Thanks....and that guys gone and done a dirty dog hack..using the original LUA file from the black diamonds, and just swapped the textures...lol....doesn't really explain how it works, but maybe that's how it has to work.....

It would seem there is some undocumented difference between the L-39 and, say, the F-15C, in regards to applying new skins. I CANNOT get my skin to appear, no matter what I try. There was no "L-39C" folder in Bazar/Liveries...which made alarm bells ring for me.... Can someone who has actually successfully changed a L39 skin give me some tips here on the idiosyncracies of this plane. (description.lua and file path info would be nice)

when I fire this up..... the edm extractor wondow opens up fine...no problem running it..my problem is, I cant find the actual files its looking for. I assumed it to mean you would point it at your dds file directories with description.lua and it would pull it all apart etc and generate an LUA based on what you had. Where are these "edm" files...ie, what directory should I be pointing it at to pull, say, L-39 data to generate my own skin for it?

but how do we know what those are pertaining to an aircraft? ED should be providing this information because its quite half_ssed the way it is right now.

I believe it uses a hierarchical structure where it looks for all its "new" stuff in the user saved game library, then the Bazar/Liveries then the CoreMods library...if it finds a file for that specific "face" it tries to apply it...if it doesn't find it, or application fails, it moves to the next level in the hierarchy.