Geoffco
-
Posts
26 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Geoffco
-
-
Hi,
I have been getting some odd CTD related to FSUIPC 4.90 in FSX. The fault is repeatable and will occur upon view change (within FSX) after the sim has been changed from fullscreen to windowed and back again at least once - since this is the only way I've found so far to 'clean out' the available memory a little bit, I have been attempting to use this trick before approach to 'OOM risk' sceneries...
I get the standard windows 'chime' and the 'Fatal Error' message a few seconds afterwards. The only thing I can see going on in FSUIPC.log that is unusual (to my eyes) is this Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION" business - is my crash likely to be related to this? In terms of weather, this is provided by FSGlobal Real Weather, but testing with the FSX 'Clear Skies' theme gives the same error...
I have attached (as quotes below) an error log, the FSUIPC.log and my FSUIPC.ini... Any ideas as to wehat is going on / how to prevetn this error?
Cheers,
Geoff
This is an example Windows Error log...
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: FSUIPC4.dll, version: 4.9.0.0, time stamp: 0x51862b2f
Exception code: 0xc00000fd
Fault offset: 0x0009c097
Faulting process id: 0x2960
Faulting application start time: 0x01ceac9768eb6a26
Faulting application path: D:\Games\FSX\fsx.exe
Faulting module path: D:\Games\FSX\Modules\FSUIPC4.dll
Report Id: 9bf51ddb-188b-11e3-96c7-f46d0496af4eThis is the FSUIPC log after the crash...
********* FSUIPC4, Version 4.90 by Pete Dowson *********
Running inside FSX on Windows 7
Module base=5A0F0000
User Name="Geoff Cooper"
User Addr="geoffco@chem.gla.ac.uk"
FSUIPC4 Key is provided
WideFS7 Key is provided
15 System time = 08/09/2013 14:30:16
31 FLT UNC path = "\\PIHLAJA\Flight Simulator X Files\"
47 Trying to connect to SimConnect Acc/SP2 Oct07 ...
47 FS UNC path = "\\PIHLAJA\FSX\"
327 Run: "D:\Games\fs2004\aeroSOFT\FDC\FDC.exe"
468 LogOptions=00000000 00010011
468 SIM1 Frictions access gained and basic values patched
468 Wind smoothing fix is fully installed
468 G3D.DLL fix attempt installed ok
468 SimConnect_Open succeeded: waiting to check version okay
468 Trying to use SimConnect Acc/SP2 Oct07
1981 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
10717 AppKey="9YD1ZM4IWNH5"
10733 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
10733 Initialising SimConnect data requests now
10733 FSUIPC Menu entry added
10779 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
10779 \\PIHLAJA\Flight Simulator X Files\Previous Flight.FLT
10779 \\PIHLAJA\FSX\SimObjects\Airplanes\HJG_B712_VirtualBlue1\B717-200.AIR
12355 Memory in use: 929Mb, Avail=3167Mb
22386 Memory in use: 928Mb, Avail=3168Mb
32432 Memory in use: 928Mb, Avail=3168Mb
42479 Memory in use: 928Mb, Avail=3168Mb
52525 Memory in use: 928Mb, Avail=3168Mb
62587 Memory in use: 928Mb, Avail=3168Mb
72634 Memory in use: 927Mb, Avail=3169Mb
82680 Memory in use: 927Mb, Avail=3169Mb
92727 Memory in use: 927Mb, Avail=3169Mb
102789 Memory in use: 927Mb, Avail=3169Mb
112882 Memory in use: 927Mb, Avail=3169Mb
122929 Memory in use: 927Mb, Avail=3169Mb
132991 Memory in use: 926Mb, Avail=3170Mb
143084 Memory in use: 926Mb, Avail=3170Mb
153130 Memory in use: 926Mb, Avail=3170Mb
163192 Memory in use: 926Mb, Avail=3170Mb
173286 Memory in use: 926Mb, Avail=3170Mb
183332 Memory in use: 926Mb, Avail=3170Mb
193394 Memory in use: 926Mb, Avail=3170Mb
203487 Memory in use: 926Mb, Avail=3170Mb
213534 Memory in use: 926Mb, Avail=3170Mb
223596 Memory in use: 926Mb, Avail=3170Mb
235171 Memory in use: 1303Mb, Avail=2792Mb
252456 Memory in use: 1807Mb, Avail=2289Mb
253423 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
253751 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
262565 Memory in use: 2487Mb, Avail=1609Mb
262815 Adding menu entry:'&CONNECT FDC' for hotkey entry #0
272611 Memory in use: 2576Mb, Avail=1520Mb
282720 Memory in use: 2606Mb, Avail=1489Mb
288009 System time = 08/09/2013 14:35:04, Simulator time = 14:30:24 (13:30Z)
288009 Aircraft="HJG Boeing 717-200 Blue1 OH-BLQ SAS Ops"
291519 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
292533 Starting everything now ...
292548 AES Link established
292548 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
292782 Memory in use: 2760Mb, Avail=1336Mb
293718 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2526, Index param -1 on Weather request type 5
296027 Advanced Weather Interface Enabled
298367 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2530, Index param -1 on Weather request type 5
302798 Memory in use: 2889Mb, Avail=1207Mb
302860 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2534, Index param -1 on Weather request type 5
310567 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2538, Index param -1 on Weather request type 5
313874 Memory in use: 2442Mb, Avail=1654Mb
316775 AES version 2.31 active at airport EGPH (default vehicles deleted)
319942 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2545, Index param -1 on Weather request type 5
323920 Memory in use: 2951Mb, Avail=1145Mb
324310 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2549, Index param -1 on Weather request type 5
334029 Memory in use: 2116Mb, Avail=1980Mb
334029 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2554, Index param -1 on Weather request type 5
343701 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 2559, Index param -1 on Weather request type 5
344060 Memory in use: 2971Mb, Avail=1125MbMy FSUIPC.ini...
[General]
UpdatedByVersion=4900
History=VBXY41WAN4KMI2RLCNG1A
InitDelayDevicesToo=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=Yes
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=Yes
ElevatorSpikeRemoval=Yes
AileronSpikeRemoval=Yes
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
patchsim1friction=Yes
Debug=Please
LogExtras=x1000
ConsoleWindow=-32000,-32000,-31835,-31929
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
[JoyNames]
AutoAssignLetters=No
0=CH Pro Pedals USB
0.GUID={BED23F70-1A4D-11E2-8003-444553540000}
1=CH Throttle Quadrant USB
1.GUID={BED26680-1A4D-11E2-8004-444553540000}
2=CH Flight Sim Yoke USB
2.GUID={BED26680-1A4D-11E2-8005-444553540000}
3=Saitek Gamers' Keyboard Command Pad
3.GUID={2F971290-1A4D-11E2-8007-444553540000}
[buttons]
ButtonRepeat=20,10
1=P3,0,K49,8
2=P3,1,K50,8
3=P3,2,K51,8
4=P3,3,K52,8
5=P3,4,K53,8
6=P3,5,K54,8
7=P3,6,K55,8
8=P3,7,K56,8
9=P3,8,K57,8
10=P3,9,K48,8
11=P1,0,K32,10
12=R2,9,C1006,1
13=U2,9,C1006,2
14=P1,1,K87,11
[AutoSave]
Next=2
Interval=60
Files=2
SaveOnGround=No
AutoSaveEnabled=Yes
1=Fri 005112
2=Fri 005012
[GPSout]
GPSoutEnabled=No
Port=COM1
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=
[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
SimModeIndicator=No
Sentences=
[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002
[Programs]
RUNIF1=CLOSE,"D:\Games\fs2004\aeroSOFT\FDC\FDC.exe"
RUNIF2=CLOSE,"C:\Program Files (x86)\GrabClipSaveX\GrabClipSaveX.exe"
RUNIF3=CLOSE,"D:\Games\FSGRW-Network_bridge\FS Global Real Weather Network Bridge.exe"
RUNIF4=CLOSE,"D:\Games\RemoteFlightServer\RemoteFlightServer.exe"
[sounds]
Path=D:\Games\FSX\Sound\
Device1=Primary Sound Driver
Device2=Speakers (ASUS Xonar Essence STX Audio Device)
Device3=S/PDIF Pass-through Device (ASUS Xonar Essence STX Audio Device)
[Axes]
0=0X,256,D,7,0,0,0
1=0Y,256,D,8,0,0,0
2=0Z,256,D,47,0,0,0
3=1X,256,D,22,0,0,0
4=1X,B,8448,12032,66065,0
5=1X,B,768,4864,66066,0,66067,0
6=1X,B,-16384,256,65786,0
7=1Z,256,D,9,0,0,0
8=1U,256,D,23,0,0,0
9=1V,256,D,10,0,0,0
10=2X,256,D,45,0,0,0
11=2Y,256,D,46,0,0,0
12=2V,256
13=2V,BR,-4811,16383,66079,0
14=2V,BR,-16384,-4681,66080,0
15=2P,0,F,66416,0,0,0
[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Aileron=-16253,0,0,16128
Elevator=-16384,0,0,16128
Rudder=-16384,0,0,16256
LeftBrake=-16384,16256/16
RightBrake=-16384,16256/16
Throttle1=-16123,-14693,-13393,16128
Throttle2=-16384,-15213,-14303,16383
Spoilers=-16384,0,2688,16128/16
Flaps=-16384,16383/16
MapThr12to34=Yes
SlopeAileron=3
SlopeElevator=3
SlopeRudder=1
SlopeLeftBrake=3
SlopeRightBrake=3
[Keys]
1=88,11,1079,0
4=223,8,66415,0
5=88,10,1079,0
7=32,8,65875,0,65796,0
[ClientNames]
1=LAKKA
[Monitor]
Monitor0=0,024C,4,0
-
You'd need to have a small Lua plug-in in the Wideclient folder which read the log file as it was written and display it locally. There's a "wnd" library in the WideClient Lua implementation which can display scrolling texts. You'd need to share the FSX Modules folder so it vould be read, of course.
If that's all then just have a very small Lua program which reads the offset containing that memory value and displays it using the "display" library, which does formatting etc for you.
Pete
Thanks, I'll do it that way. Thought I'd check first in case there was already a method in place.
Geoff
-
Hi,
I like the debug console window, but I wonder if it is possible to show that real time log data on a second PC connected with WideClient? (Latest FSUIPC for FSX in use)
What I want to do is watch the VAS memory availability during certain procedures in FSX, but the other options for viewing it are no good in fullscreen mode (the FS display option makes the screen flash at ~1Hz). I already run my weather programs etc on the second PC, so having the VAS displayed there would be a neat debugging setup...
Cheers,
Geoff
-
The list of FSX controls which FSUIPC has installed in your FSUIPC Documents folder lists them all, and those are the same names listed in FSUIPC's drop-down assignments lists (though the latter also includes FSUIPC's own added controls and those for Lua and Macro files). The example in post #5 was "View forward right" which you will see in both places. The list document provides the numerical equivalent which is what you'd use in a Lua plug-in, and is how the FSUIPC INI file records your assignments. FSX uses the name strings instead in its XML file recording assignments.
I'm afraid I'm a bit out of my depth with FSX's panel display handling, but I would have thought the Panel ID open and Panel ID close controls would work without loading multiple copies. There's also a Panel ID toggle control.
Pete
Thanks, I have looked at a couple of tutorials earlier on Lua and that will be a good way to do it, if I can get the gauge stable...
The code I have got already does indeed use Panel ID open / Close and some custom L:Vars from a gauge by Doug Dawson that can tell me when different panel ID windows are actually open...
I guess that the memory issue comes from the fact that FSX just doesn't like big 2D panels and obviously has some trouble when several of them are open. In FS9 I could have a single 5120x1600 front view with about 100 custom XML gauges and popups without too much trouble. In FSX, that just won't open and I have had to split it into two several parts, just to get it all to display!
Geoff
-
Oh, I see! It isn't the VIEWS you want, but the cockpit walls/windows around them.
I'm rather lost again. What are "key commands" in this context? FS controls ("Key Events" or K:... in XML) are numerical values which are sent internally in WM_COMMAND messages. As such they can be assigned to key presses and to buttons and axes, of which the hat switch is actually treated as both by FSUIPC. You could actually have the hat switch send both the view changing controls it currently does AND send othere controls to switch your panel bit map, if in fact it is implemented that way.
Additionally, or maybe alternatively, the controls ("Key Events") sent to FS from any source can be received and acted upon in FSUIPC Lua plug-ins using the event.control function. Wouldn't this be a way of programming your needs?
Regards
Pete
They are key events captured using XML code like I showed in post #5. I have to admit they were new to me when starting this gauge, so my understanding of them is more than likely incorrect!
Yes, thanks - Lua plugins is where my reading and testing will probably take me next...
You may try to use "conditional buttons assignment" for the hatswitch buttons, e.g
100=W8320!1 R0,34,C65672,0 ; PAN IN VC/EXTERNAL VIEW 101=W8320=1 H0,34,K102,8 ; KEYPRESS IN 2D PANEL VIEW
so, for the above example if you press the POV-RIGHT button while in 2D panel it generates keypress (NUM-6) and operates normally as PAN button in other view modes (VC, external, top-down). Just change the keypress assignment above to your predifined key for each of HAT buttons (32-39).
If you use that FIXED-VIEW XML gauge, maybe it's also possible to assign the hatswitch buttons for PANEL ID OPEN/CLOSE/TOGGLE directly,
100=W8320!1 R0,38,C65672,0 ; PAN IN VC/EXTERNAL VIEW 101=W8320=1 H0.38,C66507,10001 ; OPEN PANEL ID 10001 (CUSTOM FIXED-VIEW) 102=W8320=1 U0.38,C66507,10001 ; CLOSE PANEL ID 10001
I hope this will be helpful,
Regards,
-xcorez-
That's great - thanks for the pointers...
I think first I will have to work out why FSX is gaining about 150-200MB to it's memory footprint with each of these views when I open them (consistently and at any airport I care to choose) and then not unloading that. It is quickly enough to get me an OOM message with heavier scenery areas, making the concept of the 2D views rapidly less appealing!
Thanks,
Geoff
-
Yes, and this is what I don't understand as I don't see a difference. Sorry.
Ah, so it isn't to do with just looking out the window in different directions? You want predefined cameras, effectively. And these can't be done with the camera options?
Have you looked at programs like EZDOK and OpusFSX? They do a good job. I use EZDOK myself.
Regards
Pete
In FSX, when there is no VC and you look right, you see only the scenery to the right. In FS9 you could easily define a bitmap image to also be displayed on that view so that when you looked right, you'd see the scenery /and/ that image, so it would look like you were looking out of the cockpit. See attached screenshot from FS9 - there is /no/ VC there, just the illusion of one using a fixed bitmap (the wingtip /is/ part of the model).
When I take the same aircraft, with no VC, in FSX there is no easy facility to get those views back, with the bitmap overlay. I can add them as panels, but then I need code to open and close them when the view is in the appropriate direction - FSX cannot do this natively anymore... I found an XML solution from Joao Muas on fsdeveloper that allows me to capture key commands to the views, and that way set up code to switch to the right bitmap / panel in my panel.cfg. Only problem being that it only works for the key presses, and not the joystick hat switch.
Here is what the FSX view looks like with no 'extras' - all you get is the wing.
Hope that makes more sense.
I have had a quick look at EZDOK, but as far as I can see, there is no provision for fixed views with bitmap overlays. Perhaps I am wrong?
(Anyway, it might all be worthless as I seem to be getting OOM errors with these view switching scripts, so perhaps they have deeper problems...)
Thanks,
Geoff
-
Yes. That was the idea, for those who wanted to disable controllers altogether in FSX.
Hmm. I'm obviously still not understanding. Here "panel view" selects specific views in 2D mode, AND returns to forward when released, whilst still panning in VC mode. So you have view selection in 2D and panning in VC. As far as I recall (and I know it has been a long time -- I gave up FS9 when fSx came out -- but I certainly had my rocker switches on my yoke programmed to do exactly that.
Sorry, but it seems I'm lost.
Pete
I am trying to emulate that FS9 behaviour in FSX, with bitmap 2d panel views as there is no VC.
As I'm sure you know, in FS9 you can set view directions, eyepoints and zoom factors for each direction in the panel.cfg. Then you set a [fixed_window.xx] entry that contains an overlay to look like a window / view from the left seat looking right etc etc. When you 'look' in that direction, the eyepoint, zoom and direction from the panel.gfg are used, and if defined, the overlay from the fixed window is used too. This is great for wing views etc.
I am trying to replicate that behaviour in FSX, but annoyingly all those nice panel.cfg commands were dumped in favour of seeing the VC or nothing... FSX cannot handle fixed windows or individual viewpoints set in the same way as FS9. There are cameradefinitions, so that helps with the wing views.
The only solution I found so far is to use some XML code to show a different 'panel' - no gauges, just a bitmap - depending on which view direction was pressed. The problem is that I am severely limited in what information I have to tell me where I am currently looking. There is no nice variable to say 'cockpit view, forward right is currently in use' - if that existed, this would be really easy. Instead, the only reliable handle I've got is the key capture in XML. That is only sent when the view direction is commanded directly. For whatever reason, the hat switch is not triggering that key to be sent for each view, but it is changing the view direction. If the hat switch individual positions are set to the view directions, then the relavent key is sent.
Actually... I have just had a thought, which is that perhaps I am being a little dense and could in fact also capture the PAN_UP / DOWN keys if they are in the SDK, along with using Doug's gauge to only do it in the 2D view... This is worth testing...
Geoff
-
Strange, because it works perfectly here. Maybe I'm misunderstanding what you actually need?
Ouch! Why? So you didn't actually try what I suggested, assigning the Hat on Axis Assignments to Pan view (not in Button assignments)?
Pete
Oops! I misread your 1st reply and assumed that I had to set it as a button (or rather, several buttons).
Anyway, setting it as an axis then does exactly the same as FSX would do by default. Is that right?
What I was looking for, was a way to send capture the view direction in use in order to use 2D panel views based on the direction - something that was removed by FSX with the clear assumption that nobody would want to fly aircraft without a VC (I disagree with this).
I have a solution that works quite well using some code from a thread on fsdeveloper... On the keyboard, if I press the '9' key on the numberpad, I get the forward right view in the 2D panel and I can 'capture' that event with XML code like this:
<Keys> <On Event="VIEW_FORWARD_RIGHT">1 (>L:FrontRightView, number)</On> </Keys>
I can then use that variable to close the panel view, and open an appropriate side view. The problem is that this only works with the keyboard view commands. In order to make it work from the hat switch, I would either need to have a way to capture the hat switch command itself (simconnect, C++ and too far from my comfort zone), or find a way to make the hat switch also send the key 'view forward right' etc when selecting that position.
If I only cared about the 2D cockpit view, the solution would be simple: set the eight positions of the hat switch to the appropriate view directions in fsuipc. This works regardless of whether the hat is set to pan in the FSX config. However, that would then mess up panning in the other views, unless I could make that assignment view specific.
The other option, would be some module or other to return the current view direction, but I have not found anything for this. I know there is a gauge from Doug Dawson that will tell me when I'm in the cockpit view or not...
Geoff
-
Try assigning the hat in FSUIPC4's Axis Assignments to the FS control called "Pan view". That pans in VC mode but selects specific view directions in 2D mode.
Pete
Thanks, but no joy there.
Tried assigning all eight positions of the hat to 'Pan View' and set the control to repeat while held. Not panning properly and not selecting any views in the 2D. Am I missing something like a parameter for each of the positions?
Also tried setting each of the hat positions to the various pan directions - now it does pan, but it is not as smooth as the FSX panning, especially in the VC view, where it seems to go in discrete steps (so I guess I did something wrong)? Views /are/ selected in the 2D cockpit, but the key is not sent so the view panels are not toggled, which was the point of the excersise... Any other ideas?
Also, although this could actually be useful, the view does not reset on release of the hat switch.
Cheers,
Geoff
-
Hi,
I have a hat switch on my yoke, which is set up to 'pan' the view in the main FS configuration. When using aricraft from FS9 that have no VC, I have made a gauge in XML (using "on key" statements) to show side view windows, since FSX no longer can do this. They work fine when I change view with the keyboard, but not when I use the hat switch...
If I program the view directions to the individual points of the hat switch with fsuipc, the view switching in the 2D panel is good. However, panning modes (VC view or spot) are then messed up... Is there a way to set button assignments in fsuipc to only work in one view? Or is there another better solution for this problem (that doesn't involve having an actual VC).
I have been advised on the fsdeveloper forum that I could capture the view direction of the hat switch with C++ and Simmconnect, but that is outside of my abilities. I am happy / reasonably competent in XML though.
Thanks,
Geoff
-
Thanks for the information. Fair enough that there's no plan to do something for FS9 if it's not a problem you've encountered and it's not the same issue as in FSX.
Interesting that you didn't get this crash in your FS9 experience - I would say it is the most common one I have seen over the years. I have always assumed it to be related to scenery loading / generation... I'll just have to see if I can identify some commonality between the crashes and see if there are add-ons that could be to blame. The problem with these seems to be that they are not very repeatable - there are certain places in my FS world where they sometimes occur but then they don't happen when I go 'testing' for them with process monitor etc running / logging!
Cheers,
Geoff
-
Hi,
I have been recently plagued with g3d.dll crashes in my FS9 setup - I have had to recover three of the last five flights from an autosave. I understand that currently there is code in the FSX version of FSUIPC to detect and prevent some instances of this crash, but if I recall there was no such implementation in (or planned for) the FS9 version.
Two questions:
1) Is there any change to the above in that is there any chance of FS9 g3d.dll prevention?
2) The details given by MS on g3d.dll errors is fairly generic. I wondered if there is any better information as to what can cause these crashes? (eg if I get an fe.dll crash I know to go hunting for bad textures) My logic here is that if you have made a fix for them in FSX, then you knew why they were happening...
PS. Sorry if this has been covered already, I tried a search but of course g3d.dll and fs9 are not very good search terms...
Cheers,
Geoff
-
Yes, it can be done in C. I doubt that it can be done in XML.
Gauges written in C are merely DLLs like FSUIPC with a different name which serves to indicate that instead of loading and staying loaded they are loaded as required according to the panel. Naturally this can present a problem when hooking into a function in FS because if the gauge then unloads the hook will cause an FS crash. I've not written gauges myself, but it would be okay to undo the hook if the gauge is guaranteed to be called before being removed. If that cannot be guaranteed then it would not be advisable to insert hooks.
Another way to implement it in C (or most other languages except XML) is to use FSUIPC. Offset 0400 contains the filename of the last flight (or situation) saved, as an ASCII string with a zero terminator and the counter at 3BD2 is incremented when this has changed. This technique is used by some, especially external programs of course, like Radar Contact, so they can also save their state.
Regards
Pete
Thanks very much for the clarification. It is certainly beyond my current ability to do any of that but hopefully Doug can see a way to implement something and has time to try it. The other possibility would be a timed function, then it would be independent of Autosave but the saved FS state and panel state should never then be more than a few minutes apart... For not my 'low tech' solution will be to make a normal ";" save at top of climb so that the panel variables are saved in an "airborne" state!
Cheers,
Geoff
-
...I call the FS API directly. I think those aircraft which save their own files at the same time must hook that too...
Is that something that can be done from a C programmed gauge? My experience is limited to writing things in XML so I really don't know what would be involved... Unfortunate though, if it is not possible to save the variables upon autosave.
Geoff
-
No, it isn't any different from pressing ";" and entering a name. AutoSave calls exactly the same routine in FS to make it happen, supplying its own generated filename. This has always worked too with other add-ons which save their own data, like the PMDG aircraft and also Wilco and PSS I think. I don't know how Doug's code differs. Maybe he only takes note of the Flight-Save dialogue command, which will of course be a different command and context. Did you check if it saved when using the ';' key?
Regards
Pete
I see. Well, there is certainly some difference as far as the gauge is concerned. I have checked and confirmed that the config ini files timestamp (and content) are updated when I exit the sim or save the situation using the ; key. The timestamp etc does not change when autosave saves a file - and I have checked, of course, that the situation is really being saved.
Oh well, I'll report this back to Doug on FSDeveloper and perhaps he can see a way around it...
Cheers,
Geoff
-
FS9.1 on XP x64
Autosave 1.501
FSUIPC 3.99
Hi,
I use Autosave to make regular saves - it works very well. Recently, after a request on the FSDeveloper forums, Doug Dawson made a modified version of his dsd_xml_config.gau for saving XML LVars which would save all the variables when the situation was saved... This appears to not work with autosave, only 'user initiated' saves and normal exit of FS. Is this expected behaviour? ie. Is the autosave operation sufficiently different to the user initiated save that the gauge would not see it??
Cheers,
Geoff
-
Thanks for the info. I actually found it a few days ago through the French language verion of the Aerosoft site - funny I could not see it in the English search!
Nice scenery by the way - shame that our airline seems to have dropped it from the timetable for next year...
Cheers,
Geoff
-
Hi,
I can't find a link to Biarritz 2005 on the Aerosoft or Simmarket shop sites - I am interested in this scenery so please tell me where to get it? I saw a link on Simmarket for Simwings France 2 package (does that contain the same version?) but that was not actually available for purchase / download - why not? Your website has some great screenshots of this scenery and judging by the titles, these are products available since 2005 so I guess it's not that they are still being finished.........
Thanks,
Geoff
-
If you want just to view the basic traffic information have you tried running the TrafficLook utility? Not sure if that shows what you are looking to see.
I'm really after finding out if changes are possible / have been made to allow either of the better ATC providers (PFE or RC) are able to work with FSHotSFX which needs to have the TCAS ID set to "Flight +" while the ATC programs seem to need "Flight" or else AI is called by aircraft type rather than callsign...
Sorry, I don't know what the incompatibility was. But a good place to ask is on the RC forum at
http://forums1.avsim.net/index.php?showforum=135
Quite honestly, I don't actually know that RC uses the facilities I mentioned, only that they were originally added to FSUIPC for RC after discussions with the RC authors. Even if RC does use the facilities, it might be that it also still depends on the TCAS mode setting for other parts of its interaction.
Regards
Pete
Thanks Pete, I've posted a question over there to see what they say...
Cheers,
Geoff
-
Hi Pete,
Thanks very much for the detailed response. I suspected that it would be more complicated than I thought - otherwise the issue in question would be resolved by now. One part of your response is particularly interesting: if Radar Contact is really now set up to read the AI data correctly, then perhaps it is now compatible with FSHotSFX..? At some stage in the past when I looked into it, it suffered from the same issue as PFE.
Cheers,
Geoff
-
Hi,
I know this is dragging up a very old thread but the question is related (unfortunately, I suspect the answer will be the same too)
With regard to running FSHotSFX and ProFlight Emulator together but on different machines, using WideFS, is there any possibility to have the local machine displaying a table with the parameter "Flight +" and the network remote machine displaying a table with "Flight"? Obviously at the expense of some performance, as the table would probably have to be written twice per program 'cycle'...? Certainly it must be possible, but perhaps it is very complicted or would cause huge perfprmance problems...
Thanks,
Geoff
FSUIPC.dll causes Fatal Error - Exception 15 ?
in FSUIPC Support Pete Dowson Modules
Posted
Hi Pete,
Thanks for the info - I'll report back if I continue to get these errors after refreshing the graphics drivers and updating FSUIPC...
Thanks,
Geoff