Post by: EHM-2097 Andrei on December 08, 2013, 06:36:17 pm
As a reminder, I created that gauge long before the latest FL4 version was out, and at that time it had been tested by myself and other MT members - successfully. Later, I included it in the FL4 release, and from that point on it appears that no one was able to use it any more. Neither could I, actually, but that was on a new FS9 installation on a new windows Version (7 as opposed to XP when I did the first tests).
Now I am trying to remake it from scratch, and the first tests are encouraging (it loads OK on my PC). I cannot tell the difference, but there are many possible causes (for instance, I built the code on a different PC running a different Windows version).
Thus I would like to get some feed-back from pilots using various configurations.
For now it is a VERY PARTIAL version; basically it always shows INOP, but the color changes depending on the parking brake (set/not set) and the on/off push button on the gauge itself. If that works... success!
The opposite scenario is one where you get an error when FS attempts to load the gauge, OR it only shows as a black rectangle.
Anything in-between is less likely, but interesting to know so please report it in as many details as possible.
This partial version of the gauge is attached to this post. Usage (including PANEL.CFG changes) is the same as published within the latest FL4 release. Whatever the results, when reporting these please specify the Windows and FS version (which reminds me to remind you, no X-Plane version of the gauge... yet).
Thanks for your feed-back
Andrei
See below - ZIP attached to a newer post
Post by: EHM-2758 Peter on December 09, 2013, 09:23:53 am
I love to be of any help, but since the zip-file only contains the gauge and mentioned documentation cannot be found, I would like some further instructions how to handle!
Peter
Post by: EHM-2387 Eric-Jan on December 09, 2013, 02:27:45 pm
Post by: EHM-2097 Andrei on December 09, 2013, 03:58:12 pm
Andrei
[EDIT] A few more instructions, for whoever is not familiarized at all with the FS aircraft configuration files.
1) Choose an aircraft to test the gauge with. The simpler the better, so I (kind of obviously) choosed a C172. Pay attention to the fact that there may be several variations of the same aircraft!
2) Locate that particular aircraft subfolder in <FS Root>/Aircraft (in this case it's the "C172" subfolder) and open the AIRCRAFT.CFG file within using NOTEPAD or equivalent for viewing (no need to change this file)
3) Within the AIRCRAFT.CFG file, locate the [flightsim.something] section that refers to the EXACT AIRCRAFT VARIATION you plan to use for testing. Within that section, check the corresponding panel folder (blank means the "Panel" subfolder, while any suffix like "ehm" means "Panel.ehm" subfolder)
4) Copy the gauge file EHMGAUGE.GAU into the proper panel subfolder, overwriting any older versions of the file
5) Within the same folder, change the PANEL.CFG file as shown in the attached example. Making a backup copy beforehand is recommended...
6) Ensure there is no other conflicting EHMGAUGE.GAU anywhere else within the FS installation, and particularly in the <FS Root/Gauges> folder.
7) Start FS and hope for the best :)
Notes:
- The above mentioned folders match a FS9 installation, and may be slightly different in FSX
- ANY change to a PANEL.CFG file is ignored until that particular aircraft is "loaded" into the simulation. If it is already loaded, you can select another aircraft (using a different panel!) and then select back the test aircraft whose PANEL.CFG file you just modified
Post by: EHM-2387 Eric-Jan on December 09, 2013, 06:24:36 pm
Post by: EHM-2387 Eric-Jan on December 09, 2013, 06:59:14 pm
I tested with the Aerosoft Twin Otter, under FSX Acelleration, running Windows 7 Home Premium, 64 bit (but FSX is still 32 bit app, of course)
I did not see a colour changing gauge, just a transparent window top left (or so I thought, the first time I pressed SHIFT-5, which is that window designation in the Twotter) with a status line at times when FL4's status would change. The "Recording started" status line is slightly confusing, because at that time, FL4 still has a not-recording state (Parked / Not ready in magenta)
Post by: EHM-2097 Andrei on December 09, 2013, 08:30:16 pm
Now the question is who else can, who can not, and why ?
Andrei
Post by: EHM-2387 Eric-Jan on December 10, 2013, 06:32:45 am
Post by: EHM-2097 Andrei on December 10, 2013, 08:40:46 am
For testing I use one of the default Cessnas.
Also note that I edited my earlier post with the sample PANEL.CFG attachment, adding more instructions on adding the gauge; hope this helps.
Andrei
Post by: EHM-2758 Peter on December 10, 2013, 12:34:12 pm
As you've instructed, I installed the EHMgauge in a default C172. From the screenshot below you can read that the window does show on in the menu and on the screen and is sizeable! I gather that's what you wanted to know and see.
config. info:
I5 CP 750 @ 2.67GHz 64it
Windows 7 Home Edition
FSX Acceleration
Hope this will help you to develop the gauge!
Peter
Post by: EHM-2589 David on December 10, 2013, 05:29:16 pm
Sorry Andrei :-[
Post by: EHM-2097 Andrei on December 10, 2013, 09:15:00 pm
For the moment I am stuck, as I don't believe that by some dark magic this piece of software only works for me. Neither is there anything like "the master's voice" in this business. So I think there may be something wrong in my instructions!?
The dark rectangle you got, Peter, is basically the same result as David got, namely FS NOT loading this gauge (it's just the window, without its content).
I hope that with more people in the lopp someone will eventually produce the breakthrough I need to sort this out.
Andrei
Post by: EHM-2387 Eric-Jan on December 10, 2013, 10:18:59 pm
Will try with the C172 shortly, but prob not before thursday...
Post by: EHM-1465 Dominic on December 10, 2013, 10:47:02 pm
EDIT - I went back to the original thread (http://www.fly-euroharmony.com/forum/index.php/topic,7000.0.html) on this from the MT Forum and used the gauge you attached on March 10th 2012 Andrei - that version works fine in FS2004, loads ok and appears as expected on the panel. I hope that may help you to trace the current issue?
Post by: EHM-2097 Andrei on December 15, 2013, 08:53:56 am
Anyone who tried on FS9+C172, please zip and send me the WHOLE Aircraft\C172 folder, so that I can try the same setup on my PC and FS. Hopefully it will NOT work, allowing me to find out why.
@Dom: that first version gauge working only makes the mystery deeper. I started afresh in the first place because THAT gauge didn't seem to be working anymore ???
Thanks
Andrei
Post by: EHM-1465 Dominic on December 16, 2013, 05:39:31 am
Good luck :)
Post by: EHM-2097 Andrei on December 16, 2013, 10:47:14 am
Andrei
Post by: EHM-1465 Dominic on December 16, 2013, 08:03:09 pm
Let me know if it works ok?
Post by: EHM-2097 Andrei on December 17, 2013, 06:44:04 pm
Just as I supposed, the devil is in the details... in my detailed instructions to be more precise. One little underscore makes the difference between my original gauge and the new one, and the same underscore makes the new gauge incompatible with the original instructions.
So, just to make sure there is no misunderstanding, you have to make a small correction to the PANEL.CFG file:
THIS IS WRONG: gauge00=ehmgauge!ehm_status,0,0
THIS IS RIGHT: gauge00=ehmgauge!ehmstatus,0,0
That explains of course why using the original gauge with the now deprecated instructions worked for you Dom.
Expecting some good news from you now guys 8)
Andrei
Post by: EHM-1465 Dominic on December 18, 2013, 03:04:15 am
I then redownloaded the gauge and renamed it "ehmgauge1", reinstalled this after deleting the first version and amended the panel.cfg accordingly - all in case there was an entry in the FS9.cfg file identifying the old version as a BAD gauge forever - but when i tried to load the plane I still got the same dialog box that it would be disabled with the new gauge name (ehmgauge1) referred to...
Sorry :(
Post by: EHM-2097 Andrei on December 18, 2013, 05:33:53 am
- Feedback from more people
- Everyone trying the gauge, please say 32 or 64 bit Windows
- To avoid the same thing happening again, please write or post the EXACT error message you get, do not try to interpret / translate it as information invariably gets lost in this process.
Unfortunately when unable to load a gauge, it seems that MSFS doesn't provide any clue about WHY it is unable to do so. Also, there seem to be differences between installations, because even with the wrong PANEL.CFG file I only got a blank gauge but no error message. That's why I need it tested on as many setups as possible.
Thanks
Andrei
Post by: EHM-2387 Eric-Jan on December 18, 2013, 07:56:30 am
Haven't found the time yet to get around to testing, yet. Despite me putting it on my ToDo list twice already. Hope to speak to you on Mumble this evening.
Post by: EHM-1465 Dominic on December 18, 2013, 01:15:32 pm
"ERROR - FS9
Flight Simulator was unable to load some aircraft or software. You can continue to use Flight Simulator but this aircraft or software will be disabled.
File - AIRCRAFT\c182\panel\ehmgauge1.GAU" (as per my last post with the gauge renamed)
I've also just checked the FS9.CFG file and there is no entry in there about the C182 or the gauge being disabled in the [FrameCallNoWarn] section or elsewhere.
Post by: EHM-2097 Andrei on December 23, 2013, 04:43:53 pm
My best guess is that the remaining problem is a 32/64 bit issue in my code. Actually that makes even more important to see whether anyone on 64 bit windows manages to make it work (after correcting the PANEL.CFG file as of my preceeding post).
Andrei
Post by: EHM-1328 Willem on December 26, 2013, 01:32:47 pm
System:
I5-2,6-upgraded to 3g/16GB
2x 128GB SSD
AT HM5670 Video
OS Win 8.1 /64
FSX
After installating in C172 and BAE146-300 it get both registerd in fsx.cfg but nothing else happens.
also not a dialog/window
Remark:
After step from win7 to win8 fsx was a disaster, with the latets update to win 8.1 and 3 days ago
a video driver update FSX (not ehmgauge) works oke in dx11 mode and in dx9 mode (before driver update only in dx11 mode).
Regards
Willem EHM1328
Post by: EHM-2097 Andrei on December 27, 2013, 07:03:30 am
Just one question to be sure: did you correct the PANEL.CFG entry as shown in my post above (the one with red+green colors)? I think that the "nothing happens" behaviour was related to THAT problem.
Andrei
Post by: EHM-2387 Eric-Jan on December 27, 2013, 07:47:01 am
Sorry for keeping you waiting for so long; now sitting indoors at the camping with storm and rain outside. Good opportunity to catch up with this kind of "I should have done long ago" stuff ;D
Post by: EHM-2387 Eric-Jan on December 27, 2013, 10:01:00 am
Attached a zip file of the current c172 folder, excluding the sound folder (11 MB), and two of the Texture folders (Texture.1 and Texture.2), to make the attachment smaller than 4.5 MB
Error message was the same as Dom's: "could not load ...".
I included a screenshot of the error message inside the zip file.
Post by: EHM-2097 Andrei on December 28, 2013, 08:38:47 am
MS doesn't make things easier: I inquired on FsDeveloper forum and there is no way (log, debug mode etc.) to get any precise information from FS itself (why it cannot load the gauge). The only way is to use a C++ debugger, which I could do if I had the problem, but this doesn't help as long as the problem is elsewhere (everywhere else, actually).
Maybe I should switch and develop the gauge for X-Plane!?
Andrei
Post by: EHM-2387 Eric-Jan on December 28, 2013, 02:05:28 pm
On the other hand, if it is all about C++, then I suspect I have more libraries installed over the years on my laptop than would be considered healthy ;D (see attachment)
/ Maybe the different versions could be interfering with each other?
Post by: EHM-2097 Andrei on January 02, 2014, 08:46:55 pm
The new version to test is attached here (and I will delete the previous version just in case)
Andrei
P.S. Just saw your post E-J and if I am right... you were too ;)
Post by: EHM-2387 Eric-Jan on January 03, 2014, 09:08:09 am
I see the gauge (it is not default on; have to press <SHIFT>-6) with a red INOP field in it. If I press the button, it changed to blue INOP. Works in outside view just the same.
C172 parked at the active at GOOY, for "that other test" ;)
See attachments.
FS9; W7-64
Post by: EHM-2097 Andrei on January 03, 2014, 12:58:17 pm
Now I can proceed to writing the actual gauge function :)
Andrei