Gps issues in the 407...

[Krazycolin]

If you're having GPS issues with the 407, try opening up the acm (the loadout menu on your desktop) and choose and then save your settings.

[JMCorey]

After 2 long days of testing the 407 in every single possible configuration, with every single different possible REALISM settings, I have 2 issues that cannot be resolved.

Issue #1 GPS, of any kind, in ANY aircraft, under any configuration, no longer works.

Issue #2 If i have different configurations on different 407's, ( i.e. VH-ICK tail number set to cold and dark with standard avionics, and 315RR tail number set to ready to fly with GPS 530 ), there is very strange things that happen. The cockpit views in cold and dark will revert back to the standard eyepoint. If i change virtual cockpit view from pilot seat to overhead panel, it automatically goes back to pilot view. If I look down in pilot view, it auto corrects to looking straight ahead. If i go into spot view to flyby view, it auto corrects back to spot view. There is also a round white mouse cursor signalling that something is trying to load, then stops, then starts, then stops, and over and over and over.
This problem happens to ANY 407 in cold and dark state, with any different avionics configuration, on any different tail number. If i select a 407 that is " Ready to Fly ", the strange issues I just listed do not happen. I am completely BAFFLED and at a loss for words on that one.
I am running the Milviz Menu Manager under "Run as Administrator", and I have tried literally every single configuration possible. I have clicked each different setting, 1 at a time, and save 1 at a time, under each different tail number in the menu manager at least 3 times over.
Every 407 I had in the previous service pack worked just fine, cold and dark, ready to fly, and every avionics config. there is...ALL worked fine. Plus I was able to use the GPS in the 407, and every other aircraft.
This is INCREDIBLY FRUSTRATING ! ! !
I still have only been told by several posts in this forum to "choose and save my settings". SIGH . . . . If only it were that easy.
Oh and I am using the PEDALS_BELL407.AIR but i have also tried every other one supplied and the same issue happens with the others.
I have re-downloaded the SP4 and re-installed it several times. I have even gone through the hard drive and removed every single file from the 407 and tried a true fresh install.
The 407 is my all time favorite helicopter, and the only one available for FSX is from you guys at Milviz, and it frustrates me beyond words that it just cannot work, and be realistic at the same time.

[petedob]

I'm experiencing the same GPS issues as described above. I have utilized the ACM as recommended and still no GPS.

[JonathanBleeker]

The GPS entries are mistakenly commented out in the panel cfg. That's the cause of the problem.

[WarHorse47]

The GPS entries are mistakenly commented out in the panel cfg. That's the cause of the problem.

I have the FSX install, but noted the following entries in my panel.cfg

[Window01]
Background_color=0,0,0
size_mm=1280,650
window_size_ratio=1.000
position=2
visible=0
ident=GPS_PANEL
window_size= 0.710, 0.552
window_pos= 0.290, 0.480

//gauge00=MV-407-XML_P3Dv2_P3Dv2!FBS_GNS430_2, 640,0,640,268
//gauge00=MV-407-XML_P3Dv2!FBS_KR 87 ADF, 640,268,640,134
//gauge02=MV-407-XML_P3Dv2!FBS_GNS530_1, 0,0,640,468
//gauge01=MV-407-XML_P3Dv2!FBS_KAP140, 640,402,640,163
//gauge02=MV-407-XML_P3Dv2!FBS_GTX330, 0,468,640,170

Notice that the GPS gauges refer to the MV-407-XML_P3Dv2.cab. My install has the MV-407-XML.cab for FSX.

So to activate the GPS, some additional editing is necessary.

--WH

[JMCorey]

Just looked at mine. I am seeing the same thing. So have you found a way to fix this???? Please copy / paste if so. PLEASE ! ! !

[Window01]
Background_color=0,0,0
size_mm=1280,650
window_size_ratio=1.000
position=2
visible=0
ident=GPS_PANEL
window_size= 0.710, 0.552
window_pos= 0.290, 0.480

//gauge00=MV-407-XML_P3Dv2_P3Dv2!FBS_GNS430_2, 640,0,640,268
//gauge00=MV-407-XML_P3Dv2!FBS_KR 87 ADF, 640,268,640,134
//gauge02=MV-407-XML_P3Dv2!FBS_GNS530_1, 0,0,640,468
//gauge01=MV-407-XML_P3Dv2!FBS_KAP140, 640,402,640,163
//gauge02=MV-407-XML_P3Dv2!FBS_GTX330, 0,468,640,170

[N4GIX]

I am in the process of compiling new installers for the 407 that have the GPS issue fixed.

[JMCorey]

FIXED AND TESTED GREAT ! ! ! ! You need to paste the following into your panel.cfg and overwrite the old one, click save. GOOD TO GO.

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com

[Window Titles]

Window00=Configuration Manager
//Window01=GPS
//Window02=Reality XP GNS 430 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
//Window03=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
//Window04=Reality XP DropStack




[Window00]
Background_color=0,0,0
size_mm=920,440
window_size_ratio=1.000
position=0
visible=0
ident=40
window_size= 0.001, 0.001
window_pos= 0.000, 0.000




gauge00=MV407CM!cm_av1, 16,295,121,30
gauge01=MV407CM!cm_av2, 136,295,121,30
gauge02=MV407CM!cm_av3, 29,328,121,30
gauge03=MV407CM!cm_av4, 149,328,121,30
//gauge04=MV407CM!cold, 55,392,121,30
//gauge05=MV407CM!cm_rtf, 175,392,121,30
gauge06=MV407CM!cm_vis_01, 15,168,16,16
gauge07=MV407CM!cm_vis_02, 15,201,16,16
gauge08=MV407CM!cm_vis_03, 15,234,16,16
gauge09=MV407CM!cm_tan, 44,360,121,30
gauge10=MV407CM!cm_save, 164,360,121,30

//-----------------------------------------------------------------------------


[Window01]
Background_color=0,0,0
size_mm=1280,650
window_size_ratio=1.000
position=2
visible=0
ident=GPS_PANEL
window_size= 0.710, 0.552
window_pos= 0.290, 0.480

gauge00=MV-407-XML!FBS_GNS430_2, 640,0,640,268
//gauge00=MV-407-XML!FBS_KR 87 ADF, 640,268,640,134
//gauge02=MV-407-XML!FBS_GNS530_1, 0,0,640,468
//gauge01=MV-407-XML!FBS_KAP140, 640,402,640,163
//gauge02=MV-407-XML!FBS_GTX330, 0,468,640,170

[Window02]
window_pos=0.686667,0.526882
window_size=0.312500,0.210000
visible=1
ident=15431
zorder=99
//gauge00=rxpGNS!GNS430,0,0,100,100


[Window03]
window_pos=0.510000,0.000000
window_size=0.488281,0.500000
visible=1
ident=15531
zorder=99
//gauge00=rxpGNS!GNS530,0,0,100,100


[Window04]
position=0
window_size=0.050000,0.030000
visible=1
ident=15000
zorder=100
//gauge00=rxpDrop!Stack,0,0,100,100

[Vcockpit01]
file=Bell_407.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Bell_407

gauge00=Milviz_Sound!FBGS_XMLSound, 0,0,1,1,SimObjects\\Rotorcraft\\MILVIZ_Bell407\\Bell407XML_Sounds#30
gauge01=Bell407!Com22, 8,258,1010,107
gauge02=Bell407!Xpdr, 6,409,1012,112
gauge03=Bell407!Com11, 8,104,464,102
gauge04=Bell407!Nav11, 552,104,464,102
gauge05=Bell407!TRQ_LCD, 8,542,236,71
gauge06=Bell407!MGT_LCD, 8,647,236,71
gauge07=Bell407!N1_LCD, 9,749,236,71
gauge08=Bell407!FUEL_LCD, 2,851,236,71
gauge09=Bell407!boot_timer, 2,1,1,1
gauge10=Bell407!Chronometer, 270,410,630,630
gauge11=MV_B407_STF!STF, 0,0,1,1,0


//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_1

gauge00=MV_B407_LT!L1, 0,0,1024,1024, 1

//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_2

gauge00=MV_B407_LT!L2, 0,0,1024,1024, 2


//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_3

gauge00=MV_B407_LT!L3, 0,0,1024,1024, 3


//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_4

gauge00=MV_B407_LT!L4, 0,0,1024,1024, 4


//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_5

gauge00=MV_B407_LT!L5, 0,0,1024,1024, 5


//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_6

gauge00=MV_B407_LT!L6, 0,0,1024,1024, 6


//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_7

gauge00=MV_B407_LT!L7, 0,0,1024,1024, 7


//--------------------------------------------------------
[Vcockpit09]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_8

gauge00=MV_B407_LT!L8, 0,0,1024,1024, 8


//--------------------------------------------------------
[Vcockpit10]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_9

gauge00=MV_B407_LT!L9ON, 0,0,1024,1024, 10


//--------------------------------------------------------
[Vcockpit11]
Background_color=0,0,0
size_mm=128,128
visible=1
pixel_size=128,128
texture=$cl_10

gauge00=MV_B407_LT!L11, 0,0,128,128, 12


//--------------------------------------------------------
[Vcockpit12]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_11

gauge00=MV_B407_LT!L10, 0,0,1024,1024, 11


//--------------------------------------------------------
[Vcockpit13]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_12

gauge00=MV_B407_LT!L9OF, 0,0,1024,1024, 9


//--------------------------------------------------------
[Vcockpit14]
file=C310_VC_01.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01

gauge00=MV-407-XML!FBS_GNS430_2, 0,367,640,262
gauge01=MV-407-XML!KR 87 ADF, 0,630,640,134

//--------------------------------------------------------
[Vcockpit15]
Background_color=0,0,0
size_mm=512,512
visible=1
pixel_size=1024,1024
texture=$C310_VC_02
gauge00=MV-407-XML!FBS_GTX330, 0,376,512,136
//gauge00=MV-407-XML!FBS_GTX330, 0,376,512,136
//gauge01=MV-407-XML!FBS_GNS530_1, 0,0,512,374
gauge01=MV-407-XML!FBS_GNS530_1, 0,0,512,374
//--------------------------------------------------------
//--------------------------------------------------------
[Vcockpit16]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_03

gauge00=rxpGNS!GNS430, 0,10,1024,433

//--------------------------------------------------------
[Vcockpit17]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_04

//gauge00=MV-407-XML!FBS_GTX330, 0,376,512,136
gauge00=rxpGNS!GNS530, 0,8,512,384

//--------------------------------------------------------
[Vcockpit18]
file=C310_VC_01_FR.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_05

gauge00=MV-407-XML!FBS_GNS430_2d, 0,707,640,262
gauge01=MV-407-XML!BK_AudioPanel, 0,0,640,128
gauge02=MV-407-XML!FBS_GNS530_1d, 0,103,640,468
gauge03=MV-407-XML!FBS_GTX330, 0,571,640,136


//--------------------------------------------------------
[Vcockpit19]
file=C310_VC_02_FR.bmp
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_06
gauge00=MV-407-XML!FBS_KAP140, 0,106,512,131
gauge01=MV-407-XML!FBS_KR 87 ADF, 0,0,512,106

//--------------------------------------------------------

[Color]
Day=255,255,255
Night=255,255,255
Luminous=255,0,0

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6143

[JMCorey]

I believe whoever was putting the .cfg files in the installer package accidentally put the P3Dv2 panel folder into the FSX 407 package. What a long frustrating couple of days to figure it out but I AM SO HAPPY TO FIX IT. Hope this doesn't happen again and hope there is now some quality checks to make sure the 2 different 407 versions do not get intermixed files in the installers.

THANK YOU WARHORSE47 ! ! ! ! AND THANK YOU JONATHANBLEEKER! ! ! ! Your clues gave me an idea and it worked!!!!!!!!!! SO freaking happy now and i just got the new updated 407 addon pack in email, SWEET.

[JonathanBleeker]

Well..you took it a little overboard. Leave the ones in the window entries out unless your computer can handle it and/or if you want 2D popups as well as the VC.

[N4GIX]

I believe whoever was putting the .cfg files in the installer package accidentally put the P3Dv2 panel folder into the FSX 407 package.

Actually, I hadn't realized that the panel.cfg for the FSX version had been changed to use the revised .CAB file set of gauges I'd done for P3Dv2. So now the new installer build has that gauge in the ..\gauges folder.

Simply renaming the .CAB file would have accomplished the same result...

...but I'm delighted to hear that you got it working!