nosaMtrevoC

I've been giving some thought to creating something like this as I also want it. I do most of my casual work on my laptop on the couch rather than in my office and do not want to install the full DCS client. Considered this as a hobby project (after finishing the handfull of others for DCS I have on the go), but it's a much larger undergoing than it may be worth. I'm unsure if the effort is worth the return.

single player, just a regular instant action

Not sure when this started for me, but on the spitfire tonight (just bought it) i figured I'd do a quick curcuit and check out my first landing... not too bad in cockpit, but I like to see how smooth she is external. Can't change views whatsover on replay for some reason. Did a quick flight in the L-39 to see if it was module specific. Same thing. No other views on replay. I can only watch as if I was flying it again from inside.

Thanks Abril, This is awesome will have a look tomorrow. Hope to have a full working ACM soon with some surprises for you guys.

Hmmmm, I'd say p-51 is easier to fly. I find it easy to trim out and fly waypoints, p-47 much finikier.

Need testing for: Panel A6a ACM (Air Combat Maneuver Panel - (Ideally i need a track replay file that shows the station status flags in the 3 different configurations which are solid white, black and checkerboard as well along with the MASTER CAUTION light and L and R FIRE lights, SEAM LOCK lights, COLLISION light and HOT TRIG light lights in their ON status) these are found on pg. 55 of the F-14 manual for reference. Using the numbers on the ACM panel found on pg.55 of this manual I need number 11 in three postions (only one of them, not all), white/black/checkerboard along with 12, 13, 3, 4, 5. This will allow me to finish a complete ACM panel w/ graphical slip stream indicator and status flags. teaser approach indicator vid:

Need testing for: Panel A6a ACM (Air Combat Maneuver Panel - (Ideally i need a track replay file that shows the station status flags in the 3 different configurations which are solid white, black and checkerboard as well along with the MASTER CAUTION light and L and R FIRE lights, SEAM LOCK lights, COLLISION light and HOT TRIG light lights in their ON status) these are found on pg. 55 of the F-14 manual for reference. Using the numbers on the ACM panel found on pg.55 of this manual I need number 11 in three postions (only one of them, not all), white/black/checkerboard along with 12, 13, 3, 4, 5.

Approach Indexer working, will include icons in next release:

Worked a charm, thanks Arbil, got exactly what I needed from that.

working on a full Air Combat Man. Panel A6a, so few releases until that is complete. This involves using the F-14 textures to create buttons for the stream deck, creating custom ID's for the stream deck and providing a stream deck profile for the ACM on an SD XL. After this I'll be creating Installation instructions for this script and how to use it.

Phoenix FR, many more ID's added. I'm guessing many of your buttons will start working again. (not necessarily all, as there are still many ID's to add, all the ones with [0] are not added yet.)

awesome, I'll add it to my workflow of testing, I appreciate this.

Not dumb at all, I have reached out in a certain capacity that I'd rather not discuss here to the appropriate people, as I'd rather any decisions they make not be discussed on this forum. That being said, even with the right ID's for things like the approach indexer (top left of windshield), it really needs to be tested so that I can see how the numbers react to different scenarios so that I can duplicate them on the stream deck in a nice way. To do this, I would have to load up an F-14 scenario, set it up for a carrier landing and fly towards the carrier ensuring at one point during the approach i was above on ball and below the approach (to have each light up) and view the output. if for whatever reason I needed to see it again (to test my output), keep in mind I may load this dozens of times in testing, I'd have to repeat the above. I do this already with the gauges and other instruments, but I have 0 experience with the F-14, so to do the above I would have to learn how to do a carrier approach and all the systems involved etc... A way to help would be to provide a replay file for me (as the export data works just like I was flying) and then I could just replay that portion of the flight for testing.

thanks arbil, testing would be fantastic.

very nice

I will expect a scotch and some haggis ;), instructions coming soon.

let me get v0.09 uploaded on tuesday and then test, and we'll see if it corrects it (it should)

The attached script is a complete re-write, so it will not be as inclusive as the script I had you edit at the beginning (hope that makes sense) Your profile will start working again as soon as I upload version 0.09 probably, as most of the ID's are included. The reason I did a repwrite is because the script you had before that I edited to include fuel (at first) has a number of conflicts.

Thanks for the report, I'm guessing you were using a different F-14B script prior, I haven't added those ID's (landing gear) yet. probably just hadn't tried landing gear since switching to my script, but unfortunately there are hundreds of ID's not working until I can get to them. That's the problem with using something in development. :( Landing gear is part of panel A2, which hasn't been in any version yet. That bein said, it will in the next. last night I finished every placeholder and description for the Pilot Cockpit, just cross-referencing the ID's for them now and testing them. May have at least all the ID's available by Tuesday or so, even if they aren't tested so that at veyr least they can be used and/or reported as wrong.

<sigh> that's too bad. Could do some pretty neat things with custom fonts. I have used this trick in the past to pass custom symbols through to software that didn't have other methods.

Could actually use the above method for a number of other things also. - 3 way switches (font A is vector of up, B is middle, C is down) - could control three way switch with press is up to off and hold down is down etc.. like you described. - better tape guages by creating fonts that are 1 pixel tall by 10 wide and another that is 2 pixels tall by 10 wide etc... all the way to 288 tall by 10 wide (maybe a few pixels tall at a time), but I could then create very accurate gauges. I know I could dream up a bunch of uses if the font can be easily distributed with your plugin.

@ctytler: Had an idea last night about a lot of the "flags" in the F-14. For example, the Landing gear flag can show something like 5 different symbols in the form of squares with lines or cirlce with two lines etc... the standard approach would be to think of these as images, but along the lines of how I've bypassed the images, what if I created a font with each of these symbols corresponding to A or B etc... like wingdings. Would it be easy for you to include this font (e.g. F-14.ttf) in your plugin so that I can just pass A/B/C/D/E to your plugin and it will show the appropriate flag? In fact with all the extended charachters available on a keyboard, 1 font may be enough for all the aircraft in DCS, or at least a good sub set of the most popular ones. Then I could essentially bypass the image limitation for images that look best as vector art anyways.

I will threaten them with a Human Rights rally at their head office if they don't comply to this request immediaetly.

Awesome, I'll take a look and at least start familiarizing myself with the code. Story of my life.... code it so it works.... then go back and re-code it so that I'm not repeating my code and it's scalable. (I also panic when another developer wants to see it :) as many times coding so it works is very different than coding for public consumption... no judgements here.. it works. Never thought of this, but this would be great for switch covers or reset and wind on same button. This is what I originally wanted because I was being lazy, but I agree, it's better handled in the exportscript than confusing 99% of the casual users in the Stream Deck plugin. 3 button states would take care of a majority of the switches that are hard to acomplish now. I envisioned being able to "add" button states in a listbox type of system to allow any number, but I see that might not be possible with stream deck as you have explained below. I thought you were just calling the image state change boxes on the stream deck in your plugin. (I havn't used the stream deck for anything other than DCS, so little experience here.) Yeah, definately a work around, but not a nice one. Would confuse more people I think. This is what I envisioned. Making a set of gauges cirlce with markers for example that you define min and max values so gauge might show 20 psi to 65 psi from left to right, and then feeding the DCS id to that gauge as a needle position percentage (like DCS does already) Mostly because I wanted 288 pixels of freedom for my tape guages instead of 10 to make them more accurate. Yes, more far-fetched. Maybe a future look at this if there's enough interest, but although it would be cool as hell, it's a lot of work for little return. Thanks for your reply, want to try to finish the F-14 script first and provide it complete, but it sounds like diving into the above with you might be my next hobby project.

Yes, all of those gauges (tape gauges) have seperate inputs for Left and Right. Some of them move together only because both Left and Right engines are acting similar. I can't do this on the stream deck side, so there are custom functions that calculate the seperate inputs and draw them in the .lua script side before sending the complete "picture" (it's actually just formatted text) to the stream deck as a single ID, so I can be much more versatile than the stream deck plugin allows by formatting the output before it gets to the stream deck. And it's simple to setup because you just have to monitor the appropriate ID for the gauge which might show 5 different values for instance, or two tapes for left and right.