Jump to content
The simFlight Network Forums

Tom Mc

Members
  • Posts

    22
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    USA Pennsylvania

Tom Mc's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Pete, But programmed not only to repeat but to affect both COM1 and NAV1 standby and active, continually? Makes no sense. It appears that they refresh the 4 values for the Com1/Nav1 even though some may not have changed. Guess it wont hurt but the repeat must be a bug in their driver. I'll start working the forum at Reality and perhaps with the logs I have captured, open a ticket with them. Thanks for your support. Tom
  2. I believe the button (rocker) programming is imbeded in the Reality XP s/w since that software is required to handle the external h/w device. I have been unsuccessful at getting Reality XP (John Luke.-Canadian I believe) to engage in any discussion. I was looking for some way to work around the problem. Acts like a "repeat count" is embeded somewhere but just a guess! Without these logs, I would have been no idea... Tom
  3. Pete, I am in this forum looking for some suggestions as to how I can utilize FSUIPC to correct my simulator problems. I have not infered there is anything wrong with FSUIPC. Is there another forum you can suggest? I tried assigning Shft+9 to No Action in FSUIPC and the [window 8] popup stopped as reflected in the log. tnx. 170593 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 170593 .. Key not programmed -- passed on to FS 170593 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 170593 FSUIPC Control Action: Ctrl=1126, Param=0 170593 .. This key is programmed in FSUIPC4 'Keys' options The confusion is my understanding the log. ----------------------------------------------------------------------------- The second problem I characterize is the bouncing COM1 Active/Standby Windows. Here is the log which shows repeating events even though I only pushed the key once. Any ideas? 898062 JoystickValues PCnum=0, dwCount=1, data[2]={0000008d 00000000} 898172 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898172 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898172 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898172 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898172 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898172 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898172 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898172 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898297 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 9349 (0x00002485) COM_RADIO_SET 898297 *** EVENT: Cntrl= 66371 (0x00010343), Param= 6471 (0x00001947) COM_STBY_RADIO_SET 898297 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898297 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898390 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898390 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898390 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898390 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898593 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 9349 (0x00002485) COM_RADIO_SET 898593 *** EVENT: Cntrl= 66371 (0x00010343), Param= 6471 (0x00001947) COM_STBY_RADIO_SET 898593 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898593 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET 898703 *** EVENT: Cntrl= 65707 (0x000100ab), Param= 6471 (0x00001947) COM_RADIO_SET 898703 *** EVENT: Cntrl= 66371 (0x00010343), Param= 9349 (0x00002485) COM_STBY_RADIO_SET 898703 *** EVENT: Cntrl= 65708 (0x000100ac), Param= 5968 (0x00001750) NAV1_RADIO_SET 898703 *** EVENT: Cntrl= 66447 (0x0001038f), Param= 2048 (0x00000800) NAV1_STBY_SET Thank you for your patients. Tom.
  4. Pete, I don't want either the POPUP [window 8] or the KEYDOWN VK 16 & KEYDOWN VK 57. I am speculating that these two are causing the POPUP behavior and perhaps the bouncing COM1 active/standby frequencies. I see ascii 57 is a "9" & ascii 16 is a DLE.I'll look for through the FSUIPC Advanced User's Guide next. Tom
  5. Peter, "England and America are two countries separated by the same language " George Bernard Shaw From the FSUIPC Log: 3370890 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3370890 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS These are coming from the Reality XP Interface when I press a key (e.g. FLP) on the eLite h/w device. I have no idea what FS assignment to clear. ("To unassign a keypress in FS just go to the Assignments, find the one which is doing it, and clear it." Peter) Tom
  6. Peter, Not exactly sure how to reassign/clear the DOWNKEY VK=16 , VK=57 yet. I know how to address simple events like BREAKS... I'll search MS Learning Center first. Thank you for the direction. Gives me something to run down... Tom
  7. Peter, Here is a short log of the eFlite 430 interaction.. I believe the KEYDOWN: events are what are causing the FSX unwanted popup behavior. One of these appears to trigger [WINDOW 8] in the Panel.cfg for any aircraft I fly. Not sure exactly where to go to understand the VK=nn assignments? I was hoping to use FSUIPC to intercept the event and not pass it on. I was reading through the .pdf on VRInsight (I realize this is not what I want but the functionality is attractive). There is a FILTER capability defined in there. This is the functionality I was hoping to mimic somehow. (I do not want to passon the KEYDOWN VK=nn which are not Programmed!) The KEYUP: VK=nn all work as expected. ********* FSUIPC4, Version 4.90 by Pete Dowson ********* User Name="Tom McCaa" User Addr="tmccaa@csc.com" FSUIPC4 Key is provided WideFS7 Key is provided 3367031 System time = 27/06/2013 20:50:59, Simulator time = 08:53:43 (12:53Z) [Continuation log requested by user] Running inside FSX Module base=06060000 3370890 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3370890 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3370890 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=1 3370890 .. Key not programmed -- passed on to FS 3371047 KEYUP: VK=123, Waiting=0 3371047 KEYUP: VK=57, Waiting=0 3371047 KEYUP: VK=16, Waiting=0 3371484 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3371484 .. Key not programmed -- passed on to FS 3371484 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3371484 .. Key not programmed -- passed on to FS 3371484 KEYDOWN: VK=123, Waiting=0, Repeat=N, Shifts=1 3371484 .. Key not programmed -- passed on to FS 3371719 KEYUP: VK=123, Waiting=0 3371719 KEYUP: VK=57, Waiting=0 3371719 KEYUP: VK=16, Waiting=0 3371937 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3371937 .. Key not programmed -- passed on to FS 3371937 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3371937 .. Key not programmed -- passed on to FS 3372172 KEYUP: VK=124, Waiting=0 3372172 KEYUP: VK=57, Waiting=0 3372172 KEYUP: VK=16, Waiting=0 3372312 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3372312 .. Key not programmed -- passed on to FS 3372312 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3372312 .. Key not programmed -- passed on to FS 3372469 KEYUP: VK=124, Waiting=0 3372469 KEYUP: VK=57, Waiting=0 3372469 KEYUP: VK=16, Waiting=0 3373609 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3373609 .. Key not programmed -- passed on to FS 3373609 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3373609 .. Key not programmed -- passed on to FS 3373781 KEYUP: VK=122, Waiting=0 3373781 KEYUP: VK=57, Waiting=0 3373781 KEYUP: VK=16, Waiting=0 3373844 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3373844 .. Key not programmed -- passed on to FS 3373844 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3373844 .. Key not programmed -- passed on to FS 3374015 KEYUP: VK=122, Waiting=0 3374015 KEYUP: VK=57, Waiting=0 3374015 KEYUP: VK=16, Waiting=0 3374359 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3374359 .. Key not programmed -- passed on to FS 3374359 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3374359 .. Key not programmed -- passed on to FS 3374437 KEYUP: VK=121, Waiting=0 3374437 KEYUP: VK=57, Waiting=0 3374437 KEYUP: VK=16, Waiting=0 3374578 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3374578 .. Key not programmed -- passed on to FS 3374578 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3374578 .. Key not programmed -- passed on to FS 3374672 KEYUP: VK=121, Waiting=0 3374672 KEYUP: VK=57, Waiting=0 3374672 KEYUP: VK=16, Waiting=0 3375140 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3375140 .. Key not programmed -- passed on to FS 3375140 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3375140 .. Key not programmed -- passed on to FS 3375359 KEYUP: VK=120, Waiting=0 3375359 KEYUP: VK=57, Waiting=0 3375359 KEYUP: VK=16, Waiting=0 3375359 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 3375359 .. Key not programmed -- passed on to FS 3375359 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 3375359 .. Key not programmed -- passed on to FS 3375515 KEYUP: VK=120, Waiting=0 3375515 KEYUP: VK=57, Waiting=0 3375515 KEYUP: VK=16, Waiting=0 5016265 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYUP: VK=121, Waiting=0 5016265 KEYUP: VK=57, Waiting=0 5016265 KEYUP: VK=16, Waiting=0 5016265 KEYDOWN: VK=16, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYDOWN: VK=57, Waiting=0, Repeat=N, Shifts=1 5016265 .. Key not programmed -- passed on to FS 5016265 KEYUP: VK=121, Waiting=0 5016265 KEYUP: VK=57, Waiting=0 5016265 KEYUP: VK=16, Waiting=0
  8. Peter, I am using FSUIPC 4.90 as an interface for Eflite 430 GPS & Reality Xp S/w. I have been chasing a popup problem an annoying pop-up problem with the eflite 430 h/w interface buttons launch an additional fsx window. I turned on fusipc logging and capture a diagnostic . (paraphrase - function not implemented passing on to FS). question: Can I dump the ipc data in hex? Do I have any control on what to do with these diagnostice - eg do not pass them on? Basically, what capabilities do I have using fsuipc as an ipc debugger? Tom (USA, Pennsylvania)
  9. Pete, Ok.. Think I have isolated the problem to the RXP s/w which went south after the FSUIPC 4.80 upgrade. Think we just changed the load order and probably timing between the s/w modules. I now have a FSX that loads with 4.80 and does not CTD. Now I have to put it all back together. THANK YOU FOR ALL YOU SUPPORT!!! Next time someone complains about the cost of an upgrade, send them my way...You can not get this type of support from any other s/w provider that I have worked with.... Tom
  10. Yes... That is what I mean..Wasn't it one of your WWII PMs who said "we are two countries seperated by a common language!"
  11. Pete, Ok I think we are starting to converge now! I as pealing back the onion so to speak. I got to the dll.xml and removed almost everything being started manually. same CTD. Then went to the fsx.cfg and removed all of the TRUST section and selectively started each .dll. It appears that when any of the RXP (FLN, FLT, GNS) run, I CTD. But FSX sometimes displays a window informing me that FSX has a fatal error. So there is no crash because FSX is helping me out by gracefully handling the fatal error and terminating gracefully? THANK YOU FSX!!! I'll have to keep your SSD thread for later. I'll get to non SSD drive configuration that has the problem just so I can eliminate the SSD as a variable for now. Boy. Thanks for the guidance and helpful hints on where to look for snippets of information. Not sure what any of this has to do with FSUIPC upgrade other than changing load order/timings? Still think I have been chasing a race condition. Tom
  12. Pete, I did find the DLL.XML and removed the duplicate eliteFSX.DLL. That cleaned that up but still CTD. I'll keep at it. Tom 0.00000 SimConnect version 10.0.61259.0 0.06595 Server: Scope=local, Protocol=Auto, Address=127.0.0.1, Port=1030, MaxClients=64 0.12191 Server: Scope=global, Protocol=IPv4, Address=(null), Port=13300, MaxClients=64 0.17189 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.22515 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=1031, MaxClients=64 1.27885 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1" 1.50951 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1" 1.74049 Panels data export found and set to 20AF19E8 78.90816 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1" 79.12700 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>" 79.27962 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>" 80.13062 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>" 80.49370 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5" 82.96193 Panels data export found and set to 20AF19E8 86.82857 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.1.1"
  13. Pete, The SimConnect from the working FSX is similiar except it does not CTD. 0.00000 SimConnect version 10.0.61259.0 0.11085 Server: Scope=local, Protocol=Auto, Address=127.0.0.1, Port=1037, MaxClients=64 0.16999 Server: Scope=global, Protocol=IPv4, Address=(null), Port=13300, MaxClients=64 0.27953 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.37548 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=1038, MaxClients=64 1.67181 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1" 1.98385 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1" 2.32682 Panels data export found and set to 20AF19E8 83.10054 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1" 83.56004 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>" 83.81151 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>" 86.96876 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>" 87.76411 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5" 87.78331 DLL already loaded: Path="Modules\EliteFSX.dll" 87.78385 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.78506 DLL already loaded: Path="Modules\EliteFSX.dll" 87.78555 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.78752 DLL already loaded: Path="Modules\EliteFSX.dll" 87.78896 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.79083 DLL already loaded: Path="Modules\EliteFSX.dll" 87.79134 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.79253 DLL already loaded: Path="Modules\EliteFSX.dll" 87.79298 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.79500 DLL already loaded: Path="Modules\EliteFSX.dll" 87.79548 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.79835 DLL already loaded: Path="Modules\EliteFSX.dll" 87.79888 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.80011 DLL already loaded: Path="Modules\EliteFSX.dll" 87.80058 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.80262 DLL already loaded: Path="Modules\EliteFSX.dll" 87.80317 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.80521 DLL already loaded: Path="Modules\EliteFSX.dll" 87.80632 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 87.80758 DLL already loaded: Path="Modules\EliteFSX.dll" 87.80804 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 89.64034 Panels data export found and set to 20AF19E8 92.79150 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.0.0" 92.80194 DLL already loaded: Path="Modules\EliteFSX.dll" 92.80248 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" > 173.26540 [255, 1]Open: Version=0x00000002 Name="Saitek Flight Sim X Plugin" > 173.26583 [255, 2]SubscribeToSystemEvent:EventID=1, SystemEventName="SimStart" > 173.26610 [255, 3]SubscribeToSystemEvent:EventID=2, SystemEventName="SimStop" > 173.26628 [255, 4]SubscribeToSystemEvent:EventID=3, SystemEventName="Paused" > 173.26646 [255, 5]SubscribeToSystemEvent:EventID=4, SystemEventName="Unpaused" I cut if off here .. everything appears to work . Don't know why the EliteFSX.dll is multi-loading? May have to open a tickey with eflite on this one. What xml may be corrupted? Still have not idea about the fsx abort. I did a search of all files created by date FSX aborted. Did not find anything looking like an error log. I don't know if I have an abent handler disabled? Is that possible on XP? Thanks Tom
  14. Pete, Here is the simconnect log I just captured. 0.00000 SimConnect version 10.0.61259.0 0.04949 Server: Scope=local, Protocol=Auto, Address=127.0.0.1, Port=1032, MaxClients=64 0.09293 Server: Scope=global, Protocol=IPv4, Address=(null), Port=13300, MaxClients=64 0.13555 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64 0.17677 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=1033, MaxClients=64 0.99744 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1" 1.25133 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1" 1.59554 Panels data export found and set to 20AF19E8 46.47738 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1" 46.71771 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>" 46.79087 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>" 47.34921 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>" 47.58572 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5" 47.59972 DLL already loaded: Path="Modules\EliteFSX.dll" 47.60036 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.60233 DLL already loaded: Path="Modules\EliteFSX.dll" 47.60296 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.60526 DLL already loaded: Path="Modules\EliteFSX.dll" 47.60587 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.60768 DLL already loaded: Path="Modules\EliteFSX.dll" 47.60828 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.60958 DLL already loaded: Path="Modules\EliteFSX.dll" 47.61015 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.61190 DLL already loaded: Path="Modules\EliteFSX.dll" 47.61250 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.61381 DLL already loaded: Path="Modules\EliteFSX.dll" 47.61438 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.61567 DLL already loaded: Path="Modules\EliteFSX.dll" 47.61625 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.61763 DLL already loaded: Path="Modules\EliteFSX.dll" 47.61822 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.62048 DLL already loaded: Path="Modules\EliteFSX.dll" 47.62110 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.62290 DLL already loaded: Path="Modules\EliteFSX.dll" 47.62353 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 47.62486 DLL already loaded: Path="Modules\EliteFSX.dll" 47.62544 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll" 49.11832 Panels data export found and set to 20AF19E8 50.94373 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.1.1" Also, The Application Event Viewer. Type Date Time Source Category Event User Computer Information 3/21/2012 6:49:18 PM gusvc None 0 N/A IFS_ATD_PC_100 Information 3/21/2012 6:48:58 PM SecurityCenter None 1800 N/A IFS_ATD_PC_100 Information 3/21/2012 6:48:58 PM WebrootSpySweeperService None 0 N/A IFS_ATD_PC_100 Information 3/21/2012 6:48:18 PM gusvc None 0 N/A IFS_ATD_PC_100 Information 3/21/2012 6:48:18 PM gupdate None 0 N/A IFS_ATD_PC_100 Event Log System Type Date Time Source Category Event User Computer Information 3/21/2012 7:01:32 PM Windows Update Agent Installation 19 N/A IFS_ATD_PC_100 Information 3/21/2012 7:01:15 PM Microsoft Antimalware None 2000 N/A IFS_ATD_PC_100 Information 3/21/2012 7:01:15 PM Microsoft Antimalware None 2000 N/A IFS_ATD_PC_100 Information 3/21/2012 7:01:15 PM Microsoft Antimalware None 2002 N/A IFS_ATD_PC_100 Error 3/21/2012 6:56:40 PM SideBySide None 59 N/A IFS_ATD_PC_100 Error 3/21/2012 6:56:40 PM SideBySide None 59 N/A IFS_ATD_PC_100 Error 3/21/2012 6:56:40 PM SideBySide None 32 N/A IFS_ATD_PC_100 Error 3/21/2012 6:56:37 PM SideBySide None 59 N/A IFS_ATD_PC_100 Error 3/21/2012 6:56:37 PM SideBySide None 59 N/A IFS_ATD_PC_100 Error 3/21/2012 6:56:37 PM SideBySide None 32 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:19 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:18 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:18 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:17 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:14 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:14 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100 Information 3/21/2012 6:49:12 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:11 PM Service Control Manager None 7035 tmccaa IFS_ATD_PC_100 Information 3/21/2012 6:49:11 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:11 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:10 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100 Information 3/21/2012 6:49:10 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100 Information 3/21/2012 6:49:10 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:10 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100 Information 3/21/2012 6:49:05 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:49:05 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100 Information 3/21/2012 6:49:05 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100 Information 3/21/2012 6:47:28 PM b57w2k None 9 N/A IFS_ATD_PC_100 Information 3/21/2012 6:47:26 PM b57w2k None 15 N/A IFS_ATD_PC_100 Information 3/21/2012 6:48:00 PM eventlog None 6005 N/A IFS_ATD_PC_100 Information 3/21/2012 6:48:00 PM eventlog None 6009 N/A IFS_ATD_PC_100 Thanks Tom
  15. Pete, Found this on the Reality XP Forum. Looks like they believe the Event are normal. The Windows Event Viewer flags SideBySide Codes 59 and 32 referencing a Reality XP gauge? This is normal. All our Gauge XTreme gauges uses SimConnect in a dynamic fashion to permit loading the same gauge in either Flight Simulator 9 (without SimConnect) or Flight Simulator X/ESP, otherwise, a static binding between the gauge and SimConnect would prevent the gauge loading under FS9 (or at least, for customers running FS9 without having installed FSX). The system permits searching for the most updated version of SimConnect DLL, and the Windows API that permits doing this dynamically creates entries in the event log just for information. This is a Windows API/Operating system feature, not an error in the products. I did not see anything in the Application Event Log when I looked. I'll validate that again. So now off to get a SimConnect Log . See where that takes us. Thanks for the support. Not sure we're converging Tom
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.