Oh, sorry about that! Who could tell, anyway...


...WOW!.. ... you're 50?!...well I guess I wasn't expecting you guys at EECH forum to be that old!.. :rolleyes:

Gosh.. This makes me feel like, that I'm 24 and I got a lot yet to learn!...

Yer a youngin (so am I I guess ), and I'm 31

Damn Kimchoc! They make it sound like us geezers need to use a walker, to get to ours helos?

My sons are 31 and 26. I have 2 grandsons and a 3rd on the way, too. (So it's not just KC.)
Now you damn kids pipe down!...I can't hear Muder She Wrote!

Retro - Nice work. (And fast!)
I don't fly red side and I can't afford a motion pit so I'm guessing indicator light status is about all I'll be able to extract for a Comanche pit, right? (No analog guages there!)

Could this evolve into a means to recreate the MFDs, or is that too much data (or beyond this app's scope)?

Is your EECH up to date? My exe is supposed to go on top of arneh's latest..

Yes if you want to use the eechCommServer.exe program. UDPSpeed download .

1) Start EECH
2) Start the eechCommServer
3) Start UDPSpeed

Well you can extract the pitch/yaw/roll/etc data just the same (so you can fake some gauges), it just won't be "real" (as the real comanche does not have them)

I guess, in theory, one could export some mfd data (for example range/azimuth/type for all radar targets) and use that to recreate a similar (or identical) looking MFD in the external program, but that approach will obviously not work for the FLIR (and similar) displays. Exporting the MFD textures as a whole is a deadend, as we already talked about.

On that "CTD" PC I have currently 1.6.2W3 so shall I install firstly 1.6.2W3T2:
http://www.eechcentral.com/files/Game%20...etup162W3T2.exe

and then just copy over your cohokum.exe?
Thanks

btw. I got reply from one french diy motion platform kit designer (gonna be cheap sub 1.5K EUR!!!) as to whether what exactly is our g-force parameter doing.

I guess it is the g-force on the up#down axis only?
Is the EECH engine also able to provide g-force for left#right and forward#backward?

(The x,y,z, airspeed, slip values we have are enough but he is asking just for better fidelity)

Or by latest Arneh's you mean 1.6.2W4T3?
http://arneh.at.ifi.uio.no/eech/eechsetup162W4T3.exe

lateral and longitudinal g-forces are not stored anywhere in EECH at the moment, but it's quite easy to calculate. I've been doing it lately for making head movements with G-forces

G-forces is just acceleration, so for lateral g-force take lateral acceleration and divide by G (9.80665). (It is slightly more complicated as depending on roll/pitch gravity might add to it as well).

Retro, I think we need the UDP program to export the data out to another computer correct? I beleive that is what you are telling me. As I didnt use it yesterday. Sorry, I'm about 10 years behind you guys in learning this stuff.

Griz, if we can get warning lights and landing gear I'd be happy. Throw them on something like this
with another PCI card and interesting.. this also looks interesting for a GPS on FS, never thought of these little LCD's

OK so I made a fresh EECH install incl. the latest Arnech's version and VarDisplay works like a charm no CTDs, thanks Retro!


For your viewing pleasures "campfires in the ME" on autopilot with VarDisplay engaged:

Sadly, the UDPspeed gauges are still not spining for me and yes I had the proper IP address and port set in .ini and eechcommserver..

Thanks for any suggestions..
Please can anybody else test the UDPspeed gauges?

--

Kim my understanding is that UDP is another protocol like TCP/IP and UDPspeed program is natively able to communicate via network that's why we have to set IP address and port for both UDPspeed (.ini) and Retro's "fake Il2-DeviceLink server" EECHcommserver (port typed as simple line argument in console)..