BaronVonVaderham

Not seeing the point of a throttle that does not reflect the real one. Seems a bit of tech for the sake of tech. I’m totally appreciative of concessions on simulated controls for pragmatic reasons, but a linear quadrant is actually less pragmatic than a rotation quadrant when it comes to development of the simulated control.

Just “EHSI” didn’t work for me. I used Helios and that got it working. Helios used a slightly different make. I actually copied that name into my own monitor setup for, and ran that, and it worked. But probably because Helios patched some other files. So just “EHSI “ was not correct for my configuration for whatever reason.

Yeah, I ran the wrong profile in the Center. Go figure…

Actual, my profile is based on the Capt Zeen f-16 profile. However, I found out that I was trying to run the wrong profile in the control Center. i managed to get things working. note I’m struggling with performance of the gauges. 1) the Mach meter is inaccurate above 1.0 (it might be below that, I didn’t measure accurately), but when I fly m1.2 the Helios gauge indicates 1.0. 2) the altimeter stutters. The stuttering seems to reduce at a certain pitch angle. In the video I posted here ( ) you see it’s around +20 degrees of pitch that the stuttering stops. I have another video that shows the stuttering stops at about 12 degrees pitch. The difference between the videos is a pitch ladder image calibration in Helios, as the pitch ladder was not aligned with the in game gauge. regarding point 2: vsync in DCS is enabled, and I manually set max frame rates to 60 in the graphics lua, in line with my monitor refresh rate.

Hi, I’m trying to save a Helios profile under a different name, but Helios control Center doesn’t like the change of name and reports a monitor setup failure. I performed reset monitors every step and I pressed reconfigure and removed old configuration references and reconfigured and reset monitors. nothing works

Hi I’m using Helios to show instruments that are not viewports. Eg aoa, vvi, backup adi, back-up airspeed and backup altitude. After seeing things up in Helios and running dcs, I can see the viewports, but not the simulated gauges. First question: do the simulated indicators set up in Helios actually respond to dcs outputs? Second question: why are the simulated gauges not showing up on my displays? The displays are working.

I’m contemplating this one over the WW version. Mostly because I saw YT reviews of the WW version that was negative about the deadzone and how that affects the fssb functionality. I have a non fssb WW stick which is great, but I do have issues with the deadzone. I’m contemplating which stick to go for though. Should I go for the basic stick, or the ce/as version at twice the expense? I have no need for direct memory slots to be honest. also, none of them are in stock. Any clue when they will be available again?

Preordered… phantom is coming…

Hey guys, thought I shared some of my own work so far. i started with a front panel and cheek panels, which I drew out on fusion, and then cut from all purpose boards (no idea what it’s made of, wood and plastic I been told, very hard stuff and reminds me of Bakelite). I stuck a pair of cougars on the front and a pair of 8” displays on the back. i got a bunch of panels from PSM that I mounted on it. i also made a pedestal out of 5mm MDF. On that I screwed a pair of (I think 7”) displays, which I intend to populate with Helios. both were made just with a jigsaw, drill and sandpaper I’m still getting things installed and am waiting for suitable caches (I need some of those flat pcb ribbon cables to get hdmi age usb cables to fit), which should come in today. then it becomes time to set things up in Helios and dcs. I also got an icp and DED as well as right hand panels from PSM. They will live on my desk for the time being, as I don’t really have space to make a full cockpit just yet. the front panel can be removed from the pedestal for storage purposes. Not sure how to mount the cheeks yet (I would welcome suggestions), but the pedestal has a protruding board that I can clamp to my desk. It’ll be a bit high, but it’s workable. The entire exercise has been really good, as it allowed me to find out what works and what doesn’t. I’m now refining my drawings, so that I can get panels laser cut. Still thinking through some of that design, as I need to make the pedestal more stable, and I need to figure out how I will connect the stiffeners to the side and front panels of the pedestal once I start using pre-cut panels. I could bolt them, but that’ll take space I don’t really have. I could rivet them (you know with the simple hand rivet tool), which isn’t very strong but might work, or maybe a combination of glueing and screwing. I’ll post some more when I get things set up.

Same here. don’t know what my ping was before or after, but tonight I lost the screen a couple of times and then got kicked out. Nothing intensive either. Just me alone on a multiplayer server, running Caucasus and flying some canyons. Used to be no problem before 2.9. The only charge to my setup is DCS, which changed to 2.9.

Question on the preorder: ED has a 25% off preorder offer. Hearblur gives all kinds options with extra goodies. If I order via heatblur, how does ED add it to my module list when it comes it?

Gemacht! Ich glaube, es ist eine vielzweck Kompaktplatte: https://www.obi.de/arbeitsplatten/vielzweck-kompaktplatte-holz-139-cm-x-62-cm-x-0-3-cm-weiss/p/8069007

Ich wollte damit sagen, dass ich nach einem Dienst suchte, der Cockpitverkleidungen auf Basis von DXF-Dateien schneiden kann. Ich ging davon aus, dass das Laserschneiden die erwartete Methode ist, aber CNY würde für mich genauso gut funktionieren. Was die Frage zur Allzweckplatte betrifft, ist dies eine separate Frage. Ich habe das Material bei OBI gesehen und war neugierig, aus welchen Materialien es besteht. OBI gibt dazu keine Auskunft.

Ich bin neu in Deutschland und mein Deutsch ist nicht so gut. Deshalb versuche ich immer noch herauszufinden, was die richtigen Suchbegriffe auf Deutsch sind. Ich werde die von Dir vorgeschlagenen ausprobieren. Noch eine Frage: Ich habe bei OBI einige Boards mit Allzweckplatte gefunden. Irgendeine Idee, aus welchem Material das besteht?

Weiß jemand, wo ich in Deutschland online Plexiglas laserschneiden lassen kann?

Thanks. i was not able to export the EHSI using the device name “EHSI”. i ended up using Helios, and they use a slightly different name. This seemed to work fine. I just had to manually turn the location and size of the EHSI. a bit annoying that I had to use Helios for this, but then again, I’m planning to use an lcd for the other center pedestal gauges as well, so I’d end up having to use it regardless. as a note, I didn’t use the Helios lua, but instead used my own lua definition. This works, probably because Helios patched a number of files.

Any suggestions for how to draw fixed indications, how to draw indications based on dcs bios input, and how to have the dcs bios input drive those indications?

Same question for me really

So it took an plunge and installed Helios. Somehow I managed to get the EHSI to show up. Unfortunately I don’t know if this is because I used the right name for the EHSI, or because Helios patched some DCS files. In case of the latter I hope that doesn’t violate the Integrity Checks, or I’ll be back at square one.

Attached are images showing my monitor setup, as well as my monitor setup lua. 1= center 3840x2160 4= LEFT_MFCD 1280x800 3= RIGHT_MFCD 1280x800 2= EHSI 800x480 you can ignore the MFDL/R entries. Those are meant for the T-45, and is a different topic (also issues). I tried drawing it out on paper to make sure I didn’t make a calculation mistake, but the x and y values are correct. as mentioned the display of the EHSI works fine in windows. Someone told me I also have to edit the EHSI_init.lua , but from this thread I got the impression that was not necessary. I’m going to attempt Helios add my next step.

Hi, i received my CMDS panel, which is Arduino based. It looks like it can show the text without a problem using dcs bios, I didn’t have to modify any lua’s for that, soo I aan assuming it didn’t break integrity checks. i do have an issue with the EHSI. I received an EHSI as well, and I thought I currently added it to my display config file in the saved games folder. However, it shows up blank. i added it as a fourth monitor in windows, at the bottom edge of all the other monitors (ie all monitors are bottom edge aligned). I named the viewport “EHSI”, but I’m not sure that is correct, nor do I know how to find out. I’m fairly certain the location is correct and the monitor does work. Also I have the correct resolution in dcs. Note, my MDFs both work fine. maybe someone can share their display config content for the EHSI, and confirm that no display init files were modified for that export?

My question is very similar. I found an older thread that indicated that the EHSI can be exported the same way as the MFDs, but what is the right name for the EHSI. Likewise I’m curious about the RWR, can I export that the same way, and if yes, by what name?

Hi, I’m trying to export my EHSI as well, without any luck. i have my MFDs on separate 800x480 8” displays, and my EHSI on a much smaller (2.5”?) display also 800x480. My MFDs work fine, but my EHSI doesn’t show up. I edited my display config file in the saved games folder to state “EHSI”, followed by position and size. I assumed an EHSI size of 480, and recalculated the x position accordingly. It shows complete black. Do I need to name it “EHSI” or “F_16_EHSI” as indicated by @idenwen? How can I find out if it’s location is within visual range? (Other than trial and error)

I’ve not yet tried to modify the init file, which I assume is in the mod folder in the saved games directory? Is the init charge necessary? At the moment the fonts are all screwed up. I tried resizing, first with a ratio of approx 95% ( in line with your hornet comparison), and then I tried resizing to 75% off my original mfd sizes for the f-16. Unfortunately that didn’t change anything other than the size (at 75% they do line up with the Cougar keys). Soo the fonts are still garbled.

You understood correctly, thanks.