|
Post by flappers on Feb 10, 2012 17:09:55 GMT
my good friends at HJG, 1st of all let me say how much I appreciate your website, it is such an asset to the flightsim community, can't thank you enough! now, as to my problem that I had. I noticed this with both the red and white PG panels. When I 1st start my fs9 it is in windowed mode and that window is not maximized, rather it is the same size as the opening splash screen. Now, whenever I would go from full screen back to windowed, or if I maximized the window and then "restored down", fs9 would crash. After some investigating I found this identical entry in both those panel.cfg files:
gauge70=GEARTLK3, 0,0,1,10764795 ;EE/PG
I'm sure that 10764795 must have been a typo, I changed it to 10 and all seems well, but I am not sure if 10 is a good value or not as I am not sure what this gauge is for, although I think it is not visible and therefore 10 would be ok, just wondering if you could confirm what an acceptable value would be. thx again for this great website and great aircraft!
P.S. I believe this typo was probably from when this panel was originally made as I think I had this panel years ago before it was on HJG and had the same problem, but back then I didn't have time to check why so I just deleted the panel.
|
|
|
Post by aerofoto - HJG Admin on Feb 10, 2012 18:09:49 GMT
We/HJG have never, yet, messed with either these 2 panels .... therefore what we currently offer, in terms of these, remains precisely as was supplied to the community by the 2 authors concerned .... albeit in their last updated form. The PG white and PG red panels are essentially "identical" .... save for the predominently red backgrounded (as opposed to black) digital data displays associated with the "RED" version of these panels .... hence there should be little difference between either of their CFG files. I don´t know anything about any supposed invalidity/reduindancy) of the said "GAUGE70" .... or its associated code (i.e in regard to its possibly being a typo or not), so, I wouldn´t be inclined toward changing it .... or anything else for that matter. I personally have both panels installed on 2 different WINDOWS XP PRO based PC´s .... and in FS2004 .... and I´ve not encountered any issues such as you describe Additionally, my HJG colleague, here in Colombia, also has both of these panels installed too (since we first started testing theam early last year), on a WINDOWS 7 based PC .... and in FS2004 as well .... and he, so far as I´m aware, doesn´t appear to be experiencing any issues either .... SO .... on the strength of this information I´d be inclined toward thinking that any such issue you´re experiencing "might" be common to your own system or its settings. Mark C BOG/CO
|
|
|
Post by flappers on Feb 10, 2012 22:05:35 GMT
thx for the quick reply Mark, it could well be unique to my system as I fully expected if others were having this issue it would have been raised in the forums earlier, I was so busy last few months and periodically would check here to see if the issue had been raised and if there was a fix. Today I finally had some free time and decided to look into it. I am running windows 7 64 bit, intel I5 2.3 Ghz dual core with 8Gb ram and radeon graphics adapter. If it is unique to my system I would really like to know why, what do I have set wrong or whatever that is causing it, but that will have to be another day, for now it seems to work with the edit I did, I just don't know if that edit will affect something else that may give me other problems. thx again.
|
|
|
Post by aerofoto - HJG Admin on Feb 10, 2012 22:58:13 GMT
That´s the 90 million dollar question "FLAPPERS" .... and the one we/I, unfortunately, can´t necessarily answer for you. Files/programming can react differently on different systems .... of course .... even to the extent of causing a CTD. Unfortunately not everything can be guaranteed to work faultlessly on everyone system due to huge and complex variety of systems available today .... BUT CERTAINLY ..... I can assure you/everyone .... that each of the systems upon which we/I tested these panels(and that´s 3 seperate/individual/different PC´s and 2 different operating systems too) prior to releasing these panels here, each demonstrated no problems whatsoever .... or we simply wouldn´t have released these panels here. As you´ve correctly observed .... nobody else has, as yet, reported anything similar. I regret I can´t provide an answer regarding this for you .... BUT .... anyone else is at liberty of offer intelligent suggestion/oppinion .... if they wish. HOWEVER .... I "certainly would not" recommend editing out anything that´s currently represented within the said 2 PANEL.CFG files as, again, prior testing, and experience, over the past 12 months, has revealed no reason, whatever, to scrutinize these or consider doing such. Mark C BOG/CO
|
|
|
Post by aerofoto - HJG Admin on Feb 11, 2012 3:59:55 GMT
"FLAPPERS" .... I´ve been thinking (trying to at least ;D) about your particular issue with these 2 panel versions.
I, too, run these panels in FULL SCREEN mode .... but .... without any issues.
What I´m about to say is "a long shot in the dark" and may not help at all .... BUT .... have you tried to adjust your screen/monitor resolution .... just to see if that might help ?
Some panels can be "SENSITIVE" to particular screen/monitor resolutions.
Of course whatever resolution you have set within your FS DISPLAY settings should, generally, agree/be identical to that set within WINDOWS .... but .... have a play around these these settings anyway by experimenting in order to see what might happen using both lower (preferrably) and higher resolutions .... and whilst also still using FULL SCREEN mode for each test too. You certainly can´t do any harm by trying this.
Mark C BOG/COL
|
|
|
Post by flappers on Feb 11, 2012 5:20:01 GMT
Mark, ok, i will try that tomorrow and see what happens. I just re-read my original post on this, and I don't think I was real clear on what is happening. I can run this panel in full screen with no issues at all, and I can run it in windowed mode with no issues at all, the crash occurs only when I try to switch from full screen or a "maximized" window to a "downsized" window. I can switch from a full screen to a "maximized" window no problem. I can start off in a downsized window no problem, but if I maximize or go full screen and then try to go back to that downsized window it will crash. Now, that is going to a different size resolution, so perhaps you are onto something, I will give it a try and see and will let you know. thx again, and thanks again to all of you at HJG for these fine aircraft.
|
|
|
Post by aerofoto - HJG Admin on Feb 11, 2012 19:08:13 GMT
"TRY IT AND SEE" .... but .... failing that I´d stick with both the screen mode and resolution at which you already know these panels perform well and without any issues.
FYI ....
On my old 19 inch CRT monitor, back at home, and in FS2004 running within WINDOWS XP PRO, I run these panels in Full Screen, or other mode, and at a resolution of 1280X1024X32 .... without any problems.
On our more modern wide/flat screen monitor, here in Colombia, and in FS2004 running within WINDOWS XP PRO, I run these panels in Full Screen, or other mode, and at a resolution of 1440X900X32 .... again without any problems.
Camilo´s using these same panels in FS2004 running within WINDOWS 7, and in Full Screen, or other mode .... but .... I´m not sure at what resolution .... only that he´s not experiencing any problems at all either.
An odd resolution "may" be the cause of your problems.
It can happen .... with some panels.
Mark C BOG/CO
|
|
|
Post by aerofoto - HJG Admin on Feb 19, 2012 19:13:05 GMT
"FLAPPERS" .... "IF" you´re still having problems .... of the nature you recently commented regarding (above) .... then please refer to the following thread posted only last evening .... tonymadgehjg.proboards.com/index.cgi?board=questionsonfsxandhjg&action=display&thread=5229The author of this particular thread, if I´m not entirely mistaken, "seems" to be desiring to minimize his screen also .... (using a completely different aircraft and pane combination though).... but .... "apparently" .... experiencing what "might" be a similar issue. Although this other poster is using FSX .... what Dan comments (in regard to this problem, possibly, being a graphics card related issue, "MAY" have merits .... and "MAY" also apply (although I don´t imply the 2 issues are indeed related) to your situation as well. Give it a look anyway .... "IF" you care to ! In the meantime .... I can only, once again, comment that these sorts of issue have, hitherto, been "UNKNOWN" here .... at HJG. Mark C BOG/CO
|
|
|
Post by Alejandro on Feb 19, 2012 22:36:23 GMT
I'm just curious... have ypu tried to reduce the window size with another panels? Maybe the default ones?
This way we can know if it is the panel or the Flight Simulator.
Another curiosity: why do you need to reduce the program window?
|
|
|
Post by aerofoto - HJG Admin on Feb 20, 2012 2:27:56 GMT
I´m quite satisfied that whatever this issue might be .... it´s "not" being caused by the panels themselves. These panels .... in their updated form .... have been around/available since 2004 (and longer in non-updated form) .... and have been proven very stable (which is one of the reasons why I selected these 2 particular versions) .... and we/HJG, have done "ABSOLUTELY NOTHING", as yet, to any of them in terms of further upgrading/re-programming. As I keep saying ;D .... I´m inclined to think this issue is, possibly, being caused by odd FS resolutions or window resizing which some panels can be "sensitive" to .... OR POSSIBLY .... something along the lines of what Dan suggested (on the FSX SUPPORT forum) .... in regard to "graphics card" capabilities .... and in relation to what appears to be a similar issue with the B707 panels, but, which represent entirely different programming by a completely different author. This B707 issue may be related to the MD80 one too .... since, "IF" I understand correctly, running these B707 panels in a reduced window is precisely what this other user is also, apparently, trying to do. I agree that these panels, perhaps, shouldn´t be run reduced windows Mark C BOG/CO
|
|