January 11, 200323 yr Author ....I have Direct x 8.1I wondered if it might be the panel too. Although I use the default 777 panel, I remember adding a second EICAS ages ago using an add-on from flightsim.com, and then I added a fuel gauge and repositioned the radios using downloads for this for the default panel from Flightsim.com as well. The panel works fabulously with default MSFS 777 but could it be interfering with the MJ 777 in some way?Or is this a texture issue?Appreciate posts from all of you so much, thanks! It's great to be on this forum doing this with such support. JS Jonathan Sacks Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO, 12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals, CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96 FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.
January 11, 200323 yr Hmmm.... What does your Meljet Panel.cfg file say? By default it should say something like:(fltsim) :)Cpudan80 :) :+
January 11, 200323 yr Author Well, well, well, guess what?I switched back to the full unmodified MSFS 777 panel and the MJ bird is flying to FL300 without freezing!I am very pleased, but what could have caused the modified 777 panel to make things freeze up the way they did? Is there something I might be able to find in the modified panel that upsets the Meljet 777 a/c? I use the modified 777 panel with POSKY 777s fine and also with the default 777s no problems at all.Anyway, passing FL140 to FL300 now, above Hawaii (!), and all looks well. But if anybody can help me figure out what to look for in the modified panel or the MJ 777 files, post away.Thanks!JS Jonathan Sacks Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO, 12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals, CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96 FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.
January 11, 200323 yr Author Cpudan80:Yeah, the MJ 777 panel.cfg says:[fltsim]alias=b777_300 panelI modified that panel with the downloads from flightsim.com.JS Jonathan Sacks Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO, 12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals, CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96 FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.
January 11, 200323 yr JS,Glad to see my suggestions worked and you were able to find the problem. I use the FS Panel Studio program to add, modify, or delete gauges. I have had some successes and a lot of failures using this program. In some cases, when I add a gauge, the sim will freeze when I select the aircraft. When I add the same gauge to other aircraft, the sim works perfectly. Somehow, I think the panel.cfg file gets corrupted. So you have to be extremely careful when making modifications. A period or comma in the wrong place can be devastating. To debug your default 777_300 panel config, I'm posting a copy of mine which you can use to compare against yours.// Panel Configuration File// Boeing 777-300// Copyright © 1999-2001 Microsoft Corporation. All rights reserved.[Window Titles]Window00=Main Panelwindow01=Radio StackWindow02=GPSwindow03=Throttle Quadrantwindow04=Compass[Window00]file=Forward_640.bmpfile_1024=Forward_1024.bmpsize_mm=640window_size_ratio=1.0position=7visible=1ident=MAIN_PANELgauge00=Boeing777-300!Anti_Ice_Switch,406,15gauge01=Boeing777-300!Ignition_Left,459,15gauge02=Boeing777-300!Ignition_Right,537,15gauge03=Boeing777-300!Fuel_Selector,588,15gauge04=Boeing777-300!Autobrake,554,404gauge05=Boeing777-300!Gear_Lever,602,380gauge06=Boeing777-300!Pitch_Trim_Ind,554,248gauge07=Boeing777-300!Pitch_Trim_Knob,558,345gauge08=Boeing777-300!Rudder_Trim_Ind,584,308gauge09=Boeing777-300!Rudder_Trim_Knob,597,339gauge10=Boeing777-300!Aileron_Trim_Ind,583,247gauge11=Boeing777-300!Aileron_Trim_Switch,595,276gauge13=Boeing777-300!Beacon_Nav_Light_Switch,9,380gauge14=Boeing777-300!Nose_Light_Switch,1,431gauge15=Boeing777-300!Strobe_Light_Switch,29,431gauge16=Boeing777-300!Taxi_Light_Switch,49,431gauge17=Boeing777-300!Clock,0,282gauge18=Boeing777-300!Autopilot,255,182gauge19=Boeing777-300!Backup_Attitude,476,246gauge20=Boeing777-300!Backup_Altimeter,476,323gauge21=Boeing777-300!Backup_Airspeed,476,400gauge22=Boeing777-300!PFD,75,255gauge23=Boeing777-300!MFD,274,255gauge24=Boeing777-300!Avionics_Switch,21,244gauge25=Boeing777-300!Master_Caution,225,186gauge26=Boeing777-300!Autostart,500,17gauge31=SimIcons!Kneeboard Icon, 156, 457gauge32=SimIcons!ATC Icon, 169, 457gauge33=SimIcons!Map Icon, 182, 457gauge34=SimIcons!Avionics Icon, 195, 457gauge35=SimIcons!GPS Icon, 208, 457gauge36=SimIcons!ECU Icon, 221, 457gauge37=SimIcons!Compass Icon, 234, 457[Window01]size_mm=127,347position=8visible=0BACKGROUND_COLOR=2,2,2ident=RADIO_STACK_PANELgauge00=Boeing777-300!Comm 1, 0, 0gauge01=Boeing777-300!Comm 2, 0, 54gauge02=Boeing777-300!Nav 1, 0, 108gauge03=Boeing777-300!Nav 2, 0, 162gauge04=Boeing777-300!Transponder, 0, 216gauge05=Boeing777-300!ADF, 0, 265gauge06=Boeing777-300!Audio, 0, 319[Window02]size_mm=150,250position=8BACKGROUND_COLOR=16,16,16VISIBLE=0ident=GPS_PANELgauge00=gps!gps,0,0,150,250[Window03]size_mm=201window_size_ratio=1.0position=0BACKGROUND_COLOR=16,16,16visible=0ident=THROTTLE_PANELgauge00=Boeing777-300!Throttle Quadrant, 0, 0[Window04]background_color=138,118,106size_mm=70position=2visible=0ident=COMPASS_PANELgauge00=Magnetic_Compass!Magnetic-Compass,0,0[VCockpit01]size_mm=512,512pixel_size=512,512texture=$777_1background_color=0,0,0visible=0gauge00=Boeing777-300!PFD, 0, 222, 255, 288gauge01=Boeing777-300!MFD, 256, 222, 255, 288gauge02=Magnetic_Compass!Magnetic-Compass, 1, 1, 95, 94gauge03=Boeing777-300!Clock, 1, 96, 122, 125gauge04=Boeing777-300!Backup_Attitude, 256, 94, 125, 125gauge05=Boeing777-300!Backup_Airspeed, 128, 94, 125, 125gauge06=Boeing777-300!Backup_Altimeter, 384, 94, 125, 125[Default View]X=0Y=0SIZE_X=8192SIZE_Y=3100Day=255,255,255Night=159,92,124Luminous=181,64,64Jim
January 11, 200323 yr Author Jim:Thanks again.What I've done now is this:Assigned the default 777 panel, unmodified in any way, to the MJ 777. That seems to work fine now; andassigned the modified default 777 panel to the default MSFS 777 fleet. That works the way it has been doing for the past year or so.It's this latter modified panel which is much enhanced and that does not seem to like the MJ 777 (or the other way around), so the question is whether there is a way for me to get the MJ 777 a/c to get to like that modified panel?Thanks for your post of the default 777 panel cfg file. Mine looks OK on the PC here.Appreciate any further advice. Thanks!JS Jonathan Sacks Dell XPS Gen 4, Pentium IV Northwood extreme 3.8Ghz, 3Ghz RAM, eVGA 7900 GTO, 12 GoFlight modules plus MCP-PRO AP and EFIS, GF pedestal, CH rudder pedals, CH throttle quadrant, 42" LG LED, 24" DELL LCD, Windows XP, FS2004, FSUIPC 3.96 FS Autostart 1.1 (Build 11), FS Navigator 4.6, UT, FE, GE, REX, PMDG, Level-D, PSS, etc.
Create an account or sign in to comment