Jump to content
The simFlight Network Forums

arnonmoscona

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

0 Neutral

About arnonmoscona

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  • Location
    California
  1. Thanks! I do own the pro version. Looks like this should let me do it. I will have to learn how to hook it up, but I'm sure I can find this via the docs somewhere. Arnon
  2. Hi! I'm trying to find a way to map controller buttons to increment and decrement the desired IAS in the Majestic Q400. Reading through forum posts in various places I managed to find the ...\SimObjects\Airplanes\mjc8q400\doc\scripts\VariableMaps.xlsx spreadsheet. This seems to have a wealth of useful information - if you know how to use it. In the AFCS sheet there I could find the lines below: This appears to indicate that there are input variables (LVARS? offsets?) B812 and B813 that appear to control IAS (if you're in IAS mode). If there is some way to get FSUIPC to c
  3. OK. I have to wrap this up for the weekend. I will only be able to get back to this on June 17th or later.
  4. I take it back somewhat. It worked until I rebooted. Then crashed on start again. It seems that every time I reboot, I have to reinstall fsuipc, replace the DLL. and then I am stable again. I can get in and out of FSX as much as I want and stays stable. As soon as I reboot, back to square one. delete dll, reinstall, replace dll. Here is the dll.xml in this semi-stable setup: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</
  5. So since it's morning, and the things I tinkered with were FSRecorder and a GPS related entry in dll.xml, I wend ahead and reinstalled FSRecorder and both my working GPS products (Flight1 GNS750 and Flight1 GTN 530). Now the crash on exit seems to be gone. Haven't had the chance yet to check the fsuipc functionality. I am being interrupted, so it may take an hour before I can go back into it. But things seem better right now. Another question: what exactly gets cleared by reinstalling fsuipc? Is it something I can do manually? Thanks Arnon
  6. Oh, another thing that changed was the removal of the RXP dll from dll.xml I can try to reverse that to see if it makes a difference.
  7. Thanks Pete - for your patience and knowledge. So I have reinstalled fsuipc, replaced the DLL, restarted the machine, and thankfully it did not crash on start. The crash on exiting a flight is still there. Following is the log. Note that the machine is brand new and functions pretty much perfectly other than these problems. So I wouldn't attribute this to the machine. As for changes - in the last couple of days - aside from only tinkering with fsuipc, the only change was that at some point I uninstalled FSRecorder. Nothing else besides that. As for the time it takes to reinstall
  8. Well, unfortunately version p crashes FSX on start without leaving a log or creating an ini (tried with existing ini or without one - same results). Does not leave a crash report on the system logs either. I am getting pretty close to start the installation process of this machine from scratch. If I go that route it will take several weeks to get to the point I am now, and I only have a couple of hours a week that I can work on it. This long weekend was completely burned on trying to resolve the problems and I am now in a worse condition than I started with and I don't even know how to get it
  9. Thanks I will try this. Before downloading, I can tell you that it still fails when exiting a flight even with all gaming devices disconnected> I'll download it, reconnect the dcevices and send you results.
  10. And now it started to crash on load again :-( Went back to version c - does not crash on load, but continues to crash on getting out of a flight situation (eithe pressing "esc" or Ctrl-c - either way it now crashes consistently. So no more stable config. And the only things being changed is around FSUIPC. Very frustrated. Now the sim is next to useless.
  11. Another point to note is that switching flights does matter. Tried the following: start FSX load a flight after loading the flight - used the flights/load to load the same flight again. Result: crash See fsuipc4.log with manually added comments around the flight loading events From the system event log: Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.6.615, time stamp: 0x59103e64 Exception code: 0xc000041d Fault offset: 0x000c2a60 F
  12. Just to be as minimal as I can, here's a log listing with the crash. The sequence of operations was: start FSX Load a flight (just parked cold and dark) Try to exit FSX (this tyime via the menu Flights/exit (equivalent to Ctrl-C) The wait mouse cursor shows up, the shutdown sequence starts, and eventually it crashes. This did not happen with version C. The most directly relevant lines of the log seem to be: 115094 === Closing session: waiting for DLLStop to be called ... 142297 === DLLStop called ... 142297 === Closing external processes we started
  13. OK. We have some progress. I did what you said and also tinkered a lot with the dll.xml file, and got some better - but not perfect results. Here's where it is right now: Found that there is one entry in dll.xml that was related to the crash on start. It is the one named Reality XP GNS WAAS Hardware If I comment it out ( <!-- ... -->) then I no longer get the CTD on start. That DLL was actually no longer in the modules directory, as I uninstalled RXP GNS when I found out it was not compatible with FSX-SE. The uninstaller did not remove the entry from dll.xml. Clearly it w
  14. Pleased clarify. Do you want me to start with dll.xml completely absent?
×
×
  • 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.