nosaMtrevoC

Not sure if SSE4.1 is required for them to move forward, but eventually a developer needs to minimize its requirements to a given instruction set to enable newer features and efficiencies. Everyone cries for better performance, but on the flip side wants 100% compatibility. Unrealistic. Not sure where you get 70% of available space in datacenters don't support sse4.1. It's an intel instruction set that goes back to 2006/07 era, and only recently has amd (2019) sold 15% of the datacenter processors. (doesn't mean that 15% of the processors are AMD, just means they sold that percentage in 2019), majority are intel, and the sse4.1 instruction set are supported on consumer processors going back to duo core 2 or something like that. If you are trying to run DCS on a duo core 2, this instruction set is not your biggest problem. AMD has had lesser support for intel instruction sets over the years (slow to adopt), but that is the price you pay for adopting a second class processor. Don't get me wrong, I have a 3900x this year, one of the first times I've moved off Intel, but I fully realize for the 50% or more savings that I have made comes with some lesser know concessions. We have dozens of on premise and hosted systems that I bet it would be hard to find one without this support. I'm guessing all but the earliest x64 processors support sse4.1 Just took a quick look at the XEON based processors, sse4 was introduced in 2007. Everything 2008 and later has this. I'd say that ED is moving slowly to ensure compatibility. If anything I'd say step it up. Any tech older than 10 years cannot be expected to be supported in industry let alone gaming which always moves faster. I know less about AMD because few datacenters that are worth their weight have ever implemented AMD anything. I get that this is changing of recent (and for good reason), but anything recent from AMD would also support this.

I realize ED is first and foremost a business model, and I'm fine with that. Not knocking a great company that provides a wonderful product IMO, but time and time again it shows that allowing communities to build around your product like this doesn't hurt sales but does the opposite. People get more excited about your product, and new people are brought to it. If there was an open source map product, I'd still buy every terrain product ED releases. I have them all now.

I doubt he was bragging about a 3700x Maybe had his post read: I have dual 3950x's with a 4 way 2080 tian system and 64 gb ddr6... ok, then maybe it would have warranted that response.

I'd guess your limit is the GPU. I have a 3900X that is barely working during gameplay. Keep in mind that although 12 cores, it's usually more important to have better single core performance than more cores. example a 4 core 4.8Ghz will perform better than a 12 core 3.4Ghz (all other things being equal, obviously architecture of the chip is important, newer being better generally) That being said, I'm running dual 1070ti's (not sli), so essentially a single 1070 ti, and the 1070 runs 50-60 fps (mid 30's to 40 fps with super carrier) and is 100% all the time clearly showing that my 1070 ti is the bottleneck for more performance. I'm waiting for the 3000 series nvidias to come out before upgrade as the 2080's aren't that much greater performance for the price from a 1070 ti. I usually skip generations between upgrades. I also have a number of 580's I used for mining eth, and the 1070 ti's are much quicker for games (not quite double but close) than the 580's, so a 2080 should be a very nice upgrade from the rx 580. Funny enough, the 580's are 20% or more faster at mining eth... <shrug> edit: for reference I'm running very high settings (not maxed out though, there are a few concessions made) at 4k

Keep in mind with all the above, I can't test it for you. I don't have the bf-109 module, nor a copy of DCS in front of me, so this is just a best guess. Make a copy of the bf-109.lua file first and name it bf-109.org so you always have the original file un-modded.

In order to get gun information, we need to first see if that information is available in the array that is passed to this function. You'll have to dump to log the "MainPanelDevice" Array in the same function as above and see what is available to you.

So in the BF-109 lua file replace: ----------------------------- -- HIGH IMPORTANCE EXPORTS -- -- done every export event -- ----------------------------- -- Pointed to by ProcessIkarusDCSHighImportance function ExportScript.ProcessIkarusDCSConfigHighImportance(mainPanelDevice) --[[ every frame export to Ikarus Example from A-10C Get Radio Frequencies get data from device local lUHFRadio = GetDevice(54) ExportScript.Tools.SendData("ExportID", "Format") ExportScript.Tools.SendData(2000, string.format("%7.3f", lUHFRadio:get_frequency()/1000000)) -- <- special function for get frequency data ExportScript.Tools.SendData(2000, ExportScript.Tools.RoundFreqeuncy((UHF_RADIO:get_frequency()/1000000))) -- ExportScript.Tools.RoundFreqeuncy(frequency (MHz|KHz), format ("7.3"), PrefixZeros (false), LeastValue (0.025)) ]] ExportScript.Tools.SendData(35, string.format("%0.4f", mainPanelDevice:get_argument_value(35))) -- Oxygen_Flow_Blinker ExportScript.Tools.SendData(42, string.format("%0.4f", mainPanelDevice:get_argument_value(42))) -- MG131_0_Klappanker ExportScript.Tools.SendData(43, string.format("%0.4f", mainPanelDevice:get_argument_value(43))) -- MG131_1_Klappanker end with ----------------------------- -- HIGH IMPORTANCE EXPORTS -- -- done every export event -- ----------------------------- -- Pointed to by ProcessIkarusDCSHighImportance function ExportScript.ProcessIkarusDCSConfigHighImportance(mainPanelDevice) local digAltitude = mainPanelDevice:get_argument_value(9) * 13000 ExportScript.Tools.SendData(2000, string.format("%d", digAltitude).." M") ExportScript.Tools.SendData(35, string.format("%0.4f", mainPanelDevice:get_argument_value(35))) -- Oxygen_Flow_Blinker ExportScript.Tools.SendData(42, string.format("%0.4f", mainPanelDevice:get_argument_value(42))) -- MG131_0_Klappanker ExportScript.Tools.SendData(43, string.format("%0.4f", mainPanelDevice:get_argument_value(43))) -- MG131_1_Klappanker end and then in DCS Plugin use the id 2000 to view your new information, not 9

I took a quick look at the bf-109 exportscript lua file and found the following [8] = "%.4f", -- Altimeter_FinePtr {0.0, 1000.0} = {0.0, 1.0} [9] = "%.4f", -- Altimeter_CoarsePtr {0.0, 13000.0} = {0.0, 1.0} Looks to me (without testing) that these are the positions of the fine needle and the coars needle on the altimiter. What we can deduce from the comments here are that Altimeter_FinePtr (thousand feet total meaning it's the hundred foot needle) Has altitude data from 0 - 1000 ' {0.0, 1000.0} or from 2,000-3,000 etc.. and the last brackets {0.0,1.0} means it will display this as raw information 0.000 - 1.000 defined by the %.4f formatting rule. so 0.5000 is 500 feet. To be more correct, it means the needle will be pointing at 500 feet when we are at 500 feet or 1,500 feet or 2,500 feet. the next needle Altimeter_CoarsePtr goes from 0 to 13000. At this very part of me writing this i realize its meters not feet, so change feet to meters in all the above (I'm lazy and busy right now) so the Altimeter_CorsePtr goes from 0 to 13000M We can probably just use this variable to give us meters so if 0 is 0 meters and 1.0 is 13000m, then 0.5000 is 0.5000 * 13000 or 6500m so you could use just that information to do this: local digAltitude = mainPanelDevice:get_argument_value(9) * 13000 ExportScript.Tools.SendData(2000, string.format("%d", digAltitude).." M") This should output your altitude in M like 6500 M

Sounds to me after reading your post again about your altitude value that you are not getting the altitude value ID, instead you are getting the altimeter needle position id which relates from .0001 to 1 the position of the altimeter needle.

I always output the raw information that I want changed (e.g. heading information) and output it to a stream deck key first and then make a table of that data compared to my guages while flying the plane to make sure i understand the output. e.g. guage in plane shows 70gal, raw output shows 0.9234, guage in plane shows 60 gal and raw output shows 0.8254 etc...

1. Gun Counter. You'll need to find the data that store the ammo info. Not sure personally, but now you have me wanting one, so I'll take a look. 2. Yes for altitude (check my video above) I have both and fuel and heading etc... this is why i originally posted my question on this thread. (I had heading information like 0.5000 which I wanted to make 180 by using 0.5000 *360 to output proper information). My code above is doing what you are asking. You'll have to interpret it for your use case, but none the less it's a perfect example. Keep in mind, if you are grabbing a needle position of the altitude it could be like the fuel guages and not linear in value. Make sure your output is linear (meaning 0.0100 is 100 feet and 0.0500 is 500 feet etc... not 0.0100 is 100 feet and 0.0325 is 500 feet) in which case it's much more complex, but still doable.

I understand the need to keep things close to the chest or proprietary, but I'm wondering if it wouldn't help improve DCS World as a whole to allow certain parts of it to be more open to the community. Terrains especially I think would be a great project to offer the tools or API to DCS World to allow people to collaborate in building certain parts of the environment. I wouldn't allow the openness to edit the current terrains necessarily, but what about opening up certain parts of the world map that wouldn't conflict with the current terrains and allow the community to build out the LOD's, terrain and textures and buildings/streets/airports etc.. I'd love to contribute to such a project, and I know many would probably jump in with their particular talents. Pick a spot on the map to test it, and allow the community to build it out. Sort of a developer supported community project, offering the community the ability to do something on their own. Thoughts?

Glad you got it sorted.

It is absolutely possible. Many of my switches show text change state and image change. image change is second set of options and can monitor the same or different ID as the third option. It cannot change states 3 times (for a three way), but you could absolutely show armed or not. (e.g. text shows actual state -1, 0 or 1, but if armed then red light on button glows.

I'm guessing you guys are joking about cargo planes, but I dream of flying a C-130 as part of the missions, and a spooky variant would be awesome.

Not sure how much help you need in getting it working. Looks like its ID 213 with a decimal number. Without testing (I'll take a look tonight if I have time), I'd guess it's a standard 0 for caged and 1 for un-caged (or vice-versa) I'd monitor ID 213 in the text change box (3'rd option of the plugin) and cage/uncage the knob to see the value change live on the stream deck. That will tell you which values it needs to cage/uncage, and then use those values to send them in the first option.

bump. Would love this as I would like to use the ME on my laptop while not having to need the full client (don't fly planes on it)

Togg, Have used your icon pack on a few profiles... just wanted to say thanks.

P-51D 3 Wheel landing

Using the principles above and stream deck, now showing live data on my stream deck. plan to first create an icon set for the p-51, currently using button icons from tons of other peoples work, then build an f/18 pit.

I'll probably turn the live data like 92 gal information into a working analog fuel guage displayed on the stream deck. That might be nicer for the p-51 than a digital display.

Next step is to create icons for the p-51d that match. Used a mix and match from many of your guys profiles for the icons for now, but just wanted to share my main page for the p-51 live data for now. Now that it's all working next step is to pull the texture files for the cockpit (anyone want to poke me in the right direction before i start?) and create plane specific icons.

Thanks chacal, Forgot to mention that the icons are a mix and match from all types of other icon stream deck projects on these forums. Would give credit where its due, but goodness knows which icons are from each person. Next step is to create an icon pack for the p-51 when i have time. will post here.

For some context, I posted a video of the live data on the stream deck so you can match the output with the above:

Also love the WWII effort. Can't wait for the Corsair. Would love to see midway map and WWII Carriers ;) Just got into DCS again after a huge break (coming from lockon ACS and lockon flaming cliffs and a-10 from I don't even know how long ago) Wow has it ever changed. Anyways, bought the p-51d module to start with a plane that will have less of an instrument learning curve as I'm already familiar with planes in genreal and have a lot of simulator and real world hours. Love it. Took a few attempts, but this was my 4'th landing attempt 3 wheel. Pretty standard stuff, a touch tail heavy IMO, but it has great flight characteristics and is easy to fly.