bell_rj

https://discord.com/channels/536389125276827660/544224332709232660 Razbam server, #sa-chat

Took me a while to find it because it's cunningly titled without mentioning the Luftwaffe... but this is it: https://www.ww2.dk/Airfields - France.pdf Enjoy!

The text doesn't help by using 'position' inconsistently. a 'battery position' has multiple guns, each in its own 'gun position'. A light flak position is one gun IMHO. So I think you are correct in your thought that 1 position == 1 gun unless we are talking about a battery instead of a gun. Your example of 168 20mm guns serves to back that up, as you are right, there is no way that number of guns would be available for a single airfield. So I agree, and in my mission file that's how I have set the number of guns. http://www.missing-lynx.com/library/german/flak_dmourtizsen.html On this page they describe a light flak battery, with 3 guns, arranged in 3 separate positions. The unit had a battery commander - so a battery had 3 guns. So at Abbeville I'd suggest there were 7 batteries of 3 guns each, giving the 21 guns in 21 gun positions arranged in 7 battery positions.

Spotting has long been a bug bear of mine. It's probably one of the reasons why I found MP play so frustrating - I was finding it very hard to see the enemy before they saw me. Of course, practice helps - but it was clear to me that the graphics weren't helping at all. Now with this mod I can actually spot aircraft in what feels like a realistic manner. It still requires work, which is good, but it is now possible to do. And most importantly, ED, the spotting help makes me want to play the game more. This mod has improved the experience and made MP combat fun again. Not overly easy, which no-one wants, just fun. Please do not let the devs ban this mod with the integrity check. It's been a major factor in making MP flying fun for me.

The detail looks lovely but I am a bit concerned that the obvious flaw of the 'cartoon green' grass is still there. Maybe not so pronounced as Normandy 1 but still too saturated.

Just imagine the bulge was a bit bigger. Sorted.

Great work, but please please please fix the bright green colouring of the fields.

I'm very disappointed that the most iconic area in the new map, the area around Dover including the famous white cliffs, Dover port, Dover Castle, Chain Home radar station, etc isn't included in the high detail area. This was a golden opportunity to include that area in this map properly. Might that area be included in high detail at some point?

In the Razbam discord on 3rd October it is mentioned as being in the change log for the next patch: New - Santa Cruz Airfield.

This is fantastic, thanks! Can't wait to use this with the A4.

In the Razbam Discord today https://discord.com/channels/536389125276827660/544224332709232660 there was a partial list of airfields that will be added. If you are interested in the development of this map then I recommend joining that server/channel because there's quite a few tidbits about future intentions and current development that gets shared by the team.

Well I've just skimmed through my collection of Airforces Monthly since Oct 2020 and all I found was: June 2021 - purchase of second hand 737-700 Sept 2021 - their only airworthy S-2T retired. Another being refurbished. Oct 2021 - C-12B Huron delivered- first of 10 Nov 2021 - $664m designated for fighter purchase - 12 CAC JF-17 (10 single seat and 2 dual) (although no decision made at that time) I may have missed some articles but compared to the Brazilian Air Force about which there was a lot of news, there was very little to find.

I see this issue too. Turn off your mirrors. I bet that will fix it. It's not an SA specific issue - it happens in other maps. ED are aware but haven't been able to fix it yet.

You can buy here and download it now - I'm downloading right now. DCS patch is also released. Don't forget to download the terrain module separately, after you loaded the game. https://www.digitalcombatsimulator.com/en/shop/terrains/south_atlantic_terrain/

@Chapelmaggot I'm really pleased to see that you like those missions I created as it's great to know that others find them useful. And I'm glad you seem to have found a solution to your problem.

So I might be barking up the wrong tree but how about using ASCII char : (decimal 58) and string.char? https://www.tutorialspoint.com/string-char-function-in-lua-programming Thanks @Bailey for the restart tip!

My LUA experience totals about 3 days so this may not work but my guesses are: ExportScript.Tools.SendData(2010, string.format("%s%s%s%s", lDigitalClock.txtHours .. ":", lDigitalClock.txtMinutes, "\n" .. lDigitalClock.txtSeconds, "\n" .. lCET)) OR, what about adding another %s to get: ExportScript.Tools.SendData(2010, string.format("%s%s%s%s%s", lDigitalClock.txtHours, ":", lDigitalClock.txtMinutes, "\n" .. lDigitalClock.txtSeconds, "\n" .. lCET)) (I'm assuming adding another %s argument is valid).

So, good news. I re-saved the original LUA from Github and now it works. That's not the first time I've tried that so I don't know what's going on. I did see some odd behaviour with the non-CW Spit where I had to save the LUA twice before it would work. No idea why. I suspected file corruption but didn't see any differences when doing a compare in Notepad++. Another quick question if I may, is there a way to force DCS to re-read the LUA file without restarting the game? If you plan on doing any further development to DCS interface then I have a suggestion. I am trying to make a tile that shows low, normal and high oil pressure. I have used text for now, but it would be great to have a version of Momentary Button with Lamp that allows 3 image states, so I could use both > and < conditions in the same DCS Interface element. One bug (I think) I noticed with Momentary Button/Display (UFC) is that though it allows setting a condition to show a second state image, it doesn't seem to allow setting what that image is, unlike Momentary Button with Lamp. And finally, thanks for all this. I'm really enjoying using Stream Deck with all these elements that you have created. It's brought an extra level of enjoyment to DCS world. I'm even enjoying the coding and tracking down issues when I mess it up.

Thank you @Bailey! So I've made good progress getting to grips with the SpitfireLFMkIX LUA code (made a lot of mistakes haha) but I have created a new tile that returns oil pressure, temp, and rad temp and also highlights if they are low or high (I'd be pleased to share this if interested). I need a pointer though on the SpitfireLFMkIXCW LUA please. The DCS Comms function doesn't seem to be able to 'see' the CW variant. So I see the error 'DCS module not detected.' and obvioucly no IDs are therefore visible. The module name in the LUA looks ok. Is this to be expected? From looking at the DCS folder structure in \DCS World\CoreMods\WWII Units\SpitfireLFMkIX there isn't even a separate folder for the CW variant, so I wonder if DCS even thinks of this as a separate module. Have you ever seen DCS Comms connect to the CW variant? Thanks!

@Bailey Good news, I got the Spitfire (non-CW) and Mossie working. Thanks for your help! There was a slight hiccup where most of the Spitfire 3xxx IDs weren't getting to DCS for some reason, but resaving the LUA and a DCS restart fixed that. Just wanted to ask about the Spitfire CW. I noticed the LUA is missing most of the code that the non-CW script has in it. Just wondered if there was a reason for it before I tried copying across the functions and probably making a mess of it, haha.

@Bailey Ahhhh so that's what I missed. Thank you very much! I can't wait to get this working.

Hi, I hope someone can help me with this issue. I've got Stream Deck, have installed the DCS-ExportScript and the DCS Interface plugin, and have successfully established comms between DCS and the deck. For example I can see the altitude readout using DCS ID "28", so that's all good. I read the wiki and saw a list of tiles including an altimeter tile (ID "3004"). (https://github.com/asherao/DCS-ExportScripts/wiki/Spitfire-LF-MkIX) but I can't work out how to get the tiles to display. I've tried referencing the ID with no joy, unsurprisingly because when I check ID Lookup there is no such thing. I suspect I'm misunderstanding how the tiles are meant to work. Can someone help please?

Ohhh. The newsletter could have been clearer on that matter. When it listed out all the jets that would get the new FLIR, I didn't pick up that those were only ED jets. I doubt I'll be the only one to miss that. It would be better to spell things out in the newsletter rather than miss important points. (edit: I get that it'll come to third party jets eventually but the timing sounds like it may be quite different).

This is a very good point. And if ED can make the cow 'moo' whilst being flown along I'm just gonna be in stitches and repeatedly pressing F3 for the slingloaded cow fly-by view. "moooooooooooooooooooooooooo!"

Well obviously it's flying cows. Why do you even need to ask?