Gierasimov

Thanks @Backy 51 , also it makes me think it was fully intentional, as even the radio is calling SPX and not CW. That's a bummer, especially for those who would like to build a mission with that airbase.

Hi @OnReTech - I want to bring to your attention, what I think is a bug. Cairo West AB in DCS is where Sphinx International Airport is in real life, therefore AI takes long minutes to taxi from actual AB to runway at SPX and returns to the wrong runway as well. Since we don't have the civilian traffic in DCS and it is D COMBAT S, I think Cairo West should sit where it is in real life and not replace SPX as it was implemented. null

Nice one, let's hope the team effort can make your project even better! All the best!

Seems that AI E7 coming with Aussie map

I purchased for myself and for a friend. So the equilibrium prevails yet again

EA 072023 The image posted and Combat Aircraft calendar seem to suggest July

Brings back memories for sure ! Thank you !

I was away from Discord recently. If they are working on a fix then that's that. I fixed my skins, I get to take nice screenshots. Cool.

Well, this is not a bug. Just saying. Quick look at the Hornet as an example. ALL default skins that were included in the module work fine. So, ED changed the way how liveries work (by changing description.lua and under the hood code) AND they ensured that default liveries work as well, which means it is not 'by mistake'. Word 'acknowledged' tagged to this thread simply means that ED is aware of what was posted, which might as well as might not mean that they are going to 'fix' it. In the past we had several examples of ED backing out or partially reverting changes that were not that good, but this one, well, it makes controlling the liveries much easier with much less lines to write in Lua to have the livery working exactly as needed, so to me this is welcomed change and I like it, just don't really liked the way how it was introduced out of the sudden without anything being said, commented or explained... However this style is also known.

I honestly don't expect this to be "fixed" by ED. Looking and description.lua files it seems it is not a mistake, but rather a new method. I mean, the change in the file structure must have been accompanied by the code side of things. It does not look like a "let's fix a typo in the line of code". Changing the lua files for skins is actually not that hard. It might prove time consuming to some, but its something that we can fix ourselves. I posted my "solution" here is anyone's interested:

I knew it would turn out like this. Case closed I guess.

Normandy 2.0 bought you some time and boosted my patience

Sniper pod not good then?

Concur. Mine just came in today, just in time for Ah-64D over London in excellent Normandy 2.0! I am super happy with the build quality, no need to get software, firmware, calibrate, assign, nothing. True plug and play! Delivered to my door (EU) from China in three weeks from placing the order and paid flat 295 USD (including delivery / no extra taxes / fees). null

Should work if you copy mapping from one saved games to other, I do that between OS installations so it should work the same between DCS versions.

I do 100% single player and 100% open beta. There is no issue, if there is a bug that affects my fav module, I use another module for the time being or if let's say Hornet A2A was bugged, I focused on traps and A2G .... That way: 1. I am "not affected" by bugs, 2. Benefit from latest changes, 3. Have a chance to find and report bugs to make the product better when those get resolved.

Normandy D-Day? Then it would be celebrating D-Day+1, would it not? Or was I in the dark most of my life?

One Friday afternoon: "The DCS: Su-22 is a new aircraft coming to DCS that is being developed by Sniper Studio. This module will be an accurate representation of the Sukhoi Su-22M4..." I HOPE

@GazAce I sent you 75th SQN file and posted explanation here:

@iQyThradz3137i This is what I did: In Livery description.lua you need to remove lines that start with "F18C_BORT_NUMBER_ and replace them with the new format: {"f18c1_number_nose_right", 0 ,"F18C_1_DIFF_323L",false}; {"f18c1_number_nose_right", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_nose_right", DECAL ,"empty",false}; {"f18c1_number_nose_left", 0 ,"F18C_1_DIFF_323L",false}; {"f18c1_number_nose_left", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_nose_left", DECAL ,"empty",false}; {"f18c2_kil_right", 0 ,"F18C_2_DIFF_323L",false}; {"f18c2_kil_right", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c2_kil_right", DECAL ,"empty",true}; {"f18c2_kil_left", 0 ,"F18C_2_DIFF_323L",false}; {"f18c2_kil_left", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c2_kil_left", DECAL ,"empty",true}; {"f18c1_number_F", 0 ,"F18C_1_DIFF_323L",false}; {"f18c1_number_F", ROUGHNESS_METALLIC ,"F18C_1_DIF_RoughMet",true}; {"f18c1_number_F", DECAL ,"empty",true}; {"f18c2_number_X", 0 ,"F18C_2_DIFF_323L",false}; {"f18c2_number_X", ROUGHNESS_METALLIC ,"F18C_2_DIF_RoughMet",true}; {"f18c2_number_X", DECAL ,"empty",true}; Then, at the end of file you need to include the custom arguments: custom_args = { [27] = 1, -- Tail change of type of board number (0.0 -default USA, 0.1- ) [1000] = 1, -- Flaps [1001] = 1, -- Nose [1002] = 1, -- Kuwait Squadron [1003] = 1, -- Australian Squadron [1004] = 1, -- Finland Squadron [1005] = 1, -- Switzerland Squadron [1006] = 1, -- Blue Angels Jet Team } If you want to show bort numbers, the line would be similar to this: {"f18c1_number_nose_right", DECAL ,"F18C_bort_number_PL",false}; and then custom args must be changed from 1 to 0.0 for example: [1000] = 0.0, -- Flaps [1001] = 0.0, -- Nose

In description.lua you need to remove all lines that specify bort numbers and add the new lines (copied from default livery), then at the end of the file you need to include custom arguments. Have a look at one of the default liveries and compare to the custom one you have. Let me know if you need help with that, not by my PC now so I can't post example.

Hi GazAce, This is the effect of the new way how bort numbers are created via description.lua. I can send you amended files to replace, need to test on Aussie pack first.

Yeah it takes a little getting used to after years of previous speed.

OK, it went from 'way to slow' (which was OK for me) to the 'OMG where is my TDC??!?' Question - are you going to tone it down a bit? Not saying that it should be as before, but I am thinking if the slew axis on VirPil and VKB (tried both) are not following this change nicely, then folks who use keyboard or other axis controls may struggle even more...