speckfire

@MadTommy You will not be over writing any files. On the contrary, you'll be adding new files in \bazar\temptexture. The program reads the textures first from temptextures before loading them from the zip files under \bazar\world\textures If you find a way to add them via the lua file you'll be my hero :)

This is exactly how I installed our squad skins for the SU-33 by renaming the textures and putting them in \bazar\temptexture I had to dig in \bazar\word\textures\texturebmpX.zip to find the appropriate texture that I wanted to replace in a specific slot. Be careful how you rename them and the type of texture used. It has to be in DDS format and you have to rename them with a .bmp at the end in the fliename only not type. example mytexturefile.bmp (in DDS format)

How do you add skins for the Mig-29, SU-33 and the SU-27 under FC3? The description.lua is almost empty !! Here is an example of a Mig-29S description.lua file livery = { } name = "733th guards regiment, damgarten ab (gdr)" id = 4 countries = { "RUS", }

Please HungaroJet :) :)

C) How many people are hammering the server for the update at the same time.

Yup the Jig is up. ED post the changelog :)

Thanks Mustang, I will remove my foot from my mouth :D

Why isn't the updater working?? I don't want to re install again and loose an activation :(

Nope it worked fine on the 104th. I just tested it :)

Here is what I'm talking about. BTW the skin is not mine. It's part of a CAW pack on lockonfiles by Black_Hawk

It can be done. You have to edit the db_countries.lua under \DCS world\scritps\Database Under -- ISRAEL local units = {} copyTable(units,db.default_units) *** Add the line (under the planes section) cnt_unit( units.Planes.Plane, "Su-25T"); For specific skins you would need to edit the description.lua file for the specific skin that you want under \DCS World\Bazar\Liveries\SU-25T Add "ISR", in the list of countries.

I love it and I want it :)

I experienced the same problem with runway lights during multiplayer. In my case it was the 3 airports in the Tbilisi area. I was taking off from Lochin. However using the F11 view the other airports on the map had all their lights...Very strange.

I use my 2nd monitor for the KA-50 Shkval and the A-10C TGP.

Phenomenal work !!!!

An F-4 would be awesome!!!

Yes I know the specific skin must be on the server. It is. It's not the 1st time I'm doing this amigo. You do not seem to understand what I'm saying. I'm talking in a scenario when someone does NOT have the required skin, OK? -People who join with an A-10C who dont have the required skin, they default to a game skin automatically assigned by DCSW -People who join with an SU-25T who dont have the required skin, they default to a game skin automatically assigned by DCSW. -People who join with a KA-50 who dont have the required skin, they default to an Orange skin. The Ka-50 does NOT default to a game skin. Why only the KA-50 defaults to an orange skin while the A-10C and the 25T are ok ? This is what I'm trying to fix. Which file does DCSW read to assign default skins if one is not found? KA-50 for example.

Seems to be working so far for the A-10C and the Su-25T but not the ka-50. That's what I stated. I want to know which file to modify to fix this issue ie, make the KA-50 default to a skin when one is not found in a mission.

Cliffs of Disappointment.

I'm reviving this thread again to report that DCS 1.2.1 seems to have fixed the issue where custom squad skins are appearing intermittently with all the players. However people who join missions without the custom skins installed, see other players who are using them with the game default skin (I'm assuming the 1st skin available to the type) except for the KA-50. The KA-50 appears to be orange while the A-10C and the SU-25T have a game default skin. Is there a file that was overlooked for the KA-50 in multiplayer? Can a file be edited for the KA-50 to default to a skin if not found in the mission instead of appearing orange?

Thanks a lot Peter !!! This #$%^#$ is not letting me Rep you :)

Very nice indeed :)

Hoooollly !!! That would have been a biiiig disaster. I'm glad it was averted.

What's next?? Reverse thrust? Viggen anyone??? :)

My bad