Jump to content

Thomas Molitor

  • Posts

  • Joined

  • Last visited

Everything posted by Thomas Molitor

  1. Have to buy it to test it as I don't use any custom navdata. That's what I meant. So right now I don't know what the problem is. But I will check it out.
  2. Hi, never actually used any custom nav data. I guess I need to buy it from Navigraph to test it, right? Regards Thomas
  3. What exactly are you doing? From your post I don't understand how you start your flight. Still don't know what the difference between FSX and MSFS should be. You can pick a Gate in MSFS and start your flight from there.
  4. Nothing changed. FSX is supported as it was before.
  5. As I said my priority right now is MSFS. And to be honest as a developer I don't like the P3D versioning concept of breaking stuff with each version. I might reconsider it if there is enough demand. Regards Thomas
  6. No P3D support. I think most people will move to MSFS anyway and that's why I won't add it. But FSFK will still run, but won't fill out Airports automatically for example. Regards Thomas
  7. As promised: http://www.flightkeeper.net/Downloads/FSFKB1790.zip This beta is provided as is. FOR ADVANCED USERS ONLY! Support only here. NO EMAIL SUPPORT! Currently known MSFS limitations: MS Store and Steam versions should be detected automatically, but I didn't had the chance to fully test the Steam and DVD version ACARS Device gauge and the Core module are not supported due to technical limitations (old native C++ Gauges/DLLs not allowed to run inside MSFS) I will consider to port the ACARS Device to the new MSFS WASM framework at a later time next year (2021). FSFK requires FSCUIPC 7 to be up and running Weather data can not be read from FS directly AI Traffic appears to always be "enroute" Airports with no parkings are not included in the NAV-Database due to the large amount (this would increase FSFK loading times and memory usage) - corresponding FSFK option is ignored for MSFS FSFK messages using the MSFS tips dialog send via FSUIPC can be empty Startup time of FSFK increased due to the large NAV-Data amount of MSFS - To counter that I recommend to disable for example Aprons and other data you don't need to be displayed on the map in the FSFK scenery options section. The ACARS Device Installer will only allow you to edit the aircraft specific settings as the gauge is currently not supported in MSFS. Please take a look at the contained readme for installation, requirements and other notes. Have fun and stay healthy Thomas
  8. FYI: FSFK v3.6 Beta 1 with support for MSFS should be out soon. Hopefully tomorrow. Regards Thomas
  9. I think that apps using FSUIPC need to be running in the same user and elevated right context as the FSUIPC process. So if you use FSUIPC as admin FSFK needs it too. Otherwise the app cannot read the shared memory used to talk to FSUIPC. Thus the IPC errors.
  10. I run latest MSFS and FSUIPC 7 Beta and it works fine.
  11. Yes. But some features won't work any longer (e.g. gauge, core module). Current version will work with some limitations. So you can already use it now. No time window for release yet. Cheers Thomas
  12. Also check if your settings are correct. Maybe you changed something there? Thomas
  13. Hi, maybe you missed a waypoint of your flight plan? This tab is only updated if you reached the waypoints in your plan. Regards Thomas
  14. No. The FSMap databases are located under "C:\Users\[userName]\AppData\Local\FSMap". The ones for FSX are named *2006*.dat. But I think that the gauge might fall back to the FS2004 mode as it doesn't "know" P3D. You might try to duplicate those 2006 files and replace 2006 with 2004. Thomas
  15. I haven't tried the gauge in P3D. But I guess it should treat P3D as FSX and thus load the FSX NV DB if available. Thomas
  16. Prepar3D is not supported. It's planned but I cannot give you an exact at this time. But there should be no problem except for the NAV DB and the gauge installer. Regards Thomas
  17. It's planned, but I currently cannot tell you any release date. Regards Thomas
  18. Those values only work if the aircraft supports it. There is nothing you can modify. The aircraft designer is responsible for modifying those FS variables. Regards Thomas
  19. FSMMM is another product and has nothing do to with FSMap. In FSMap you need to modify the map priority. I think that's similar to the weight property in FSMMM. I think you'll need to register your copy in the Aerosoft online shop to get access to the latest version of FSMap. If not then send an email to the FSMap support address. Regards Thomas
  20. Ok. Then I guess that this DLL is not correctly registered on your system. Open a command/dos prompt as admin. Now enter the following commands: cd C:\Windows\System32 regsvr32 dx8vb.dll This should result in a new window telling you that this DLL has been registered. Now check if you can get into the sound profiles. Hope this helps Thomas
  21. Open the flight by double clicking on it.Then in the following dialog change the pilot and logbook entries via the combo boxes. Save the changed flight and you're done. Hope this helps Thomas
  22. Can you please check if the following file is installed: "C:\Windows\System32\DX8VB.dll". Regards Thomas
  23. This feature requires that you have installed it for all users (this is an option during the installation). So I recommend to re-install FSMap and make sure you install it for all users. After installing the CD version apply the latest update again. Hope this helps Thomas
  24. Hi, can you please run FSFK in debug mode (via the windows start menu shortcut) and pack and mail me (support address can be found in the manual) the resulting log file from "Documents\FS Flight Keeper\Logs\FSFK.log". Regards Thomas
  • Create New...