Jump to content
The simFlight Network Forums

katoema

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About katoema

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Scotland
  1. John, Alex is working on MSFS, yes it connects through LittleNavConnect,with my FSX scenery, but we're waiting for the facility to have full connection to the MSFS scenery, etc. Thanks for clarifying about client programs. Again, with Plan G, it will be the FSX scenery for present. Martin
  2. OK, now for the funny part: I am running LittleNavMap which will only run FSX at the moment, Alex currently updating for a MSFS connection, etc. On another PC I have Plan G and should not be able to connect to MSFS... It is showing the MSFS planes with the Asobo reg numbers! Both connected by WideClient. Martin
  3. Giving an update: MSFS: WideClient connected, no log file produced and the ini file only shows the initial Config of Port, Window and Visible=Yes. FSX: WideClient waiting for a connection, no ini information or log produced. FSUIPC folder for MSFS is place on the same Disc as MSFS itself. FSUIPC for FSX is in the Modules folder of FSX. Should a connection be possible with both MSFS and FSX on the same computer? Martin I found beneath the desktop items that were open there was an Administrator request to accept WideClient. This had not happened on any of the other computers. It is now functioning for FSX.
  4. Yes WideClient. Gee, I have the user guide on 6 machines, get verifocals out again! Thanks Martin
  5. I have a new PC for MSFS and have now FSX on it as well. I have two other computers which act as clients, both of these I placed WideFS. Wide FS will not connect for FSX and neither for MSFS. The .ini file on one says it has picked up FSUIPC7 when I was running FSX, hence no connection! Any ideas to on what to do? Thanks Martin
  6. John, to be sure all is OK so far, I attach the 3 FSUIPC7 files. Interestingly my WideFS details are there, but the log states that it is not user recognised or expired! I also attach FSUIPC4.ini file. I'd like to have those assignments; then when FSUIPC7 is back to normal operation I can add further assignments to it. Thanks Martin FSUIPC7.log FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC4.ini
  7. Hi Pete, Yes it was working on the old computer. I now see where my error cam about with copying what I thought was the previous log. Earlier John was communication with me about the runtime error. When the new computer was updated to W10 v2004 I saved the files again and, of course it was the same one! Attached is the file log from FSUIPC4, What should I do to have the .ini file working? I have brought all the controllers in MSFS back to default, as it was in the old computer when I used FSUIPC to make changes to my controllers. Thanks Martin FSUIPC4.log
  8. As a follow on: Yes the FSUIPC7.exe launched, but after extensive work on my new computer with profiles, etc the informat in my FSUIPC7 log and the FSUIPC7 ini both show what I was using on the old computer, but doesn't seem to be working on the new computer! Also, the WideFS is now not working, it's not connecting. What have I missed? The FSUIPC7_prev.log is taken from the old computer. Thanks Martin FSUIPC7_prev.log FSUIPC7.ini FSUIPC7.log
  9. I did and that is why I posted. The new PC had to be updated to W10 V2004, and it showed all C++ installations. However, I have just reinstalled again and it has launched FSUIPC7! Thank you Martin
  10. Hi Pete and John, I have installed MSFS on to a new computer and, yes, have copied FSUIPC7 over I am getting this error, see image! Your thoughts, please Thanks Martin
  11. As a WideFS user - it's working:)
  12. Thank you for redirecting me to the source. Martin
  13. Hi Pete, I have ordered the Premium Deluxe boxed version of MSF from Aerosoft. I posed the question of using FSUIPC and WideClient with MFS to them and, of course, I was directed to ask you directly! Are you currently working on a version of FSUIPC and WideClient for MFS and, if so, when do you see it being released? Thank You Martin
  14. Thank you, I had only registered as a member of the forum after the event of the FSUIPC update. I now appreciate the necessity for a log directly after an event. Point noted. Thank you for your time indeed/ Martin
  15. Thank You: The first is timed at 15:19:51 (20/072020): Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: atc.dll, version: 10.0.61637.0, time stamp: 0x46fadb59 Exception code: 0xc0000005 Fault offset: 0x000566f9 Faulting process ID: 0x75c Faulting application start time: 0x01d65e9fbc230dcc Faulting application path: C:\Fsx\fsx.exe Faulting module path: C:\Fsx\atc.dll Report ID: f5237a75-c212-4639-a754-a7871db8967c Faulting package full name: Faulting package-relative application ID: The second is timed at 15:48:37 (20/07/2020): Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57 Exception code: 0xc0000005 Fault offset: 0x00037399 Faulting process ID: 0x39c Faulting application start time: 0x01d65ea3e1987b88 Faulting application path: C:\Fsx\fsx.exe Faulting module path: C:\Fsx\ai_player.dll Report ID: 9bf81c8a-7dc2-4850-929e-907c7e41984d Faulting package full name: Faulting package-relative application ID: I had deleted the wxstationlist.bin and all of the .wx files after first reading your text in FAQ. However, I also saw that there was a slight FSUIPC4 version increase from v. 4.974 to v. 4.975a and therefore updated my version. The outcome, yesterday, is that FSX loaded with no error message. Today, everything seems to be functioning correctly! Can you indicate what the issue may have been? Thank You Martin FSUIPC4.log
×
×
  • 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.