electricclay2000 Posted July 16 Report Posted July 16 Whenever I try to start aivlasoft am getting this error ( The currently selected database does not match the running simulator type ) Is any one can help,in other post someone saying adding Init3308=13 to the [General] section of your FSUIPC7.ini file, then FSUIPC will again pre-populate that offset with the value 13, which is for MSFS2020. where in the general section to add that line am using MSFS2020 thank
John Dowson Posted July 16 Report Posted July 16 4 hours ago, electricclay2000 said: where in the general section to add that line As you quoted, in the FSUIPC7.ini file (which is in your FSUIPC7 installation folder) - did you not look there? I have moved your post to the FSUIPC7 sub-forum. John
electricclay2000 Posted July 16 Author Report Posted July 16 thank for your reply ,yes i did find the fsuipc ini file but do I add the line to the top or the bottom are any where in the general section. Clayton
John Dowson Posted July 16 Report Posted July 16 Anywhere in the [General] section... order is not important in ini files.
electricclay2000 Posted July 23 Author Report Posted July 23 good day after doing some testing I notice that the Aivlasoft EFB v2 Client moving map doesn't move anymore ,after I added the Init3308=13 to the FSUIPC7 .ini file. the Aivlasoft error Database disagree fix ,but the moving map no the client don't move anymore in MSFS 2020 thank Clayton
John Dowson Posted July 23 Report Posted July 23 2 hours ago, electricclay2000 said: I notice that the Aivlasoft EFB v2 Client moving map doesn't move anymore ,after I added the Init3308=13 to the FSUIPC7 .ini file. Is FSUIPC7 actually connect to MSFS? Maybe you can show me / attach your FSUIPC7.log file (from a session when you get this error, and please exit FSUIPC7 before attaching the file). If FSUIPC7 is connecting to MSFS and there are no error in your log, you need to contact Aivlasoft about this issye - I only support FSUIPC and not third party clients. John
electricclay2000 Posted July 23 Author Report Posted July 23 here is the fsuipc7 log file thank ********* FSUIPC7, Version 7.5.4 (13th July 2025) by John Dowson ********* WebSocket server found: C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe Windows 11 detected - setting DisableMSFSMonitor to 'Enum' Windows 10 Pro 64 Bit reported as Build 26100, Release ID: 2009 (OS 10.0) FSUIPC is running with elevated privileges Reading options from "C:\FSUIPC7\FSUIPC7.ini" Checking the Registrations now ... User Name="CLAYTON " User Addr="*******************" FSUIPC7 Key is provided WideFS7 Key is provided 109 System time = 23/07/2025 10:30:13 109 Allowing calibration when not assigned with 'Send direct to FSUIPC Calibration' 125 ------------------------------------------------------------------- 140 *** Preset name 'Cirrus_SF50_Vision_Jet__MSFS2024_-_Toggle_VNV_Button_in_Autopilot_On_and_OFF' exceeds max allowed length of 63 characters - ignoring 453 *** Preset name 'NAV_GPS_SWAP__NAV__button_on_EFIS_Control_Panel__LEFT_SIDE__CAPTAIN_' exceeds max allowed length of 63 characters - ignoring 453 *** Preset name 'NAV_GPS_SWAP__NAV__button_on_EFIS_Control_Panel__RIGHT__SIDE__FIRST_OFFICER_' exceeds max allowed length of 63 characters - ignoring 468 *** Preset name 'Main_instrument_panel_standby_attitude_indicator_cage_button_release' exceeds max allowed length of 63 characters - ignoring 484 Preset file 'C:\FSUIPC7\myevents.txt' not found [info only] 484 19666 Calculator Code presets have been loaded and are available for use 531 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 547 FS UNC path = "" 547 ---------------------- Joystick Device Scan ----------------------- 547 Product= Bravo Throttle Quadrant 547 Manufacturer= Honeycomb Aeronautical 562 Serial Number= 37772E1220083B00 562 Vendor=294B, Product=1901 (Version 1.5) 562 GUIDs returned for product: VID_294B&PID_1901: 562 GUID= {9F5EAC50-40DC-11F0-8003-444553540000} 562 Details: Btns=48, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z1023 562 Product= WINWING PAP-3 578 Manufacturer= Winwing 578 Serial Number= 81B850B2E4561221F4166002 578 Vendor=4098, Product=BF0F (Version 1.0) 578 GUIDs returned for product: VID_4098&PID_BF0F: 578 GUID= {9F0CE7C0-5280-11F0-8001-444553540000} 578 Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V4095,X0,Y0,Z0 578 Product= T.A320 Pilot 578 Manufacturer= Thrustmaster 578 Serial Number= 1 578 Vendor=044F, Product=0405 (Version 2.0) 578 GUIDs returned for product: VID_044F&PID_0405: 578 GUID= {9F6ED8F0-40DC-11F0-8008-444553540000} 578 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255 593 Product= Saitek Pro Flight Rudder Pedals 593 Manufacturer= Saitek 593 Vendor=06A3, Product=0763 (Version 1.0) 593 GUIDs returned for product: VID_06A3&PID_0763: 593 GUID= {9F6F0000-40DC-11F0-8009-444553540000} 593 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0 593 Product= WINWING PFP-3N-CAPTAIN 593 Manufacturer= Winwing 593 Serial Number= 36650021F7707032D4362012 593 Vendor=4098, Product=BB35 (Version 1.1) 593 GUIDs returned for product: VID_4098&PID_BB35: 593 GUID= {9E0CC350-5806-11F0-8001-444553540000} 593 Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U4095,V4095,X0,Y0,Z0 593 Product= Alpha Flight Controls 593 Manufacturer= Honeycomb Aeronautical 609 Serial Number= BA8E2E1524153B00 609 Vendor=294B, Product=1900 (Version 3.1) 609 GUIDs returned for product: VID_294B&PID_1900: 609 GUID= {9F6FC350-40DC-11F0-800F-444553540000} 609 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z0 609 ------------------------------------------------------------------- 609 Device acquired for use: 609 Joystick ID = 0 (Registry okay) 609 0=Bravo Throttle Quadrant 609 0.GUID={9F5EAC50-40DC-11F0-8003-444553540000} 609 Device acquired for use: 609 Joystick ID = 5 (Registry okay) 609 5=WINWING PAP-3 609 5.GUID={9F0CE7C0-5280-11F0-8001-444553540000} 609 Device acquired for use: 609 Joystick ID = 1 (Registry okay) 609 1=T.A320 Pilot 609 1.GUID={9F6ED8F0-40DC-11F0-8008-444553540000} 625 Device acquired for use: 625 Joystick ID = 2 (Registry okay) 625 2=Saitek Pro Flight Rudder Pedals 625 2.GUID={9F6F0000-40DC-11F0-8009-444553540000} 625 Device acquired for use: 625 Joystick ID = 4 (Registry okay) 625 4=WINWING PFP-3N-CAPTAIN 625 4.GUID={9E0CC350-5806-11F0-8001-444553540000} 625 Device acquired for use: 625 Joystick ID = 3 (Registry okay) 625 3=Alpha Flight Controls 625 3.GUID={9F6FC350-40DC-11F0-800F-444553540000} 625 ------------------------------------------------------------------- 640 LogOptions=00000000 00000001 640 Manually started with DetectToConnectDelay=1, InitialStallTime=20 18531 Simulator detected 19531 Trying to connect... 39968 Trying to connect... 60406 Trying to connect... 80843 Trying to connect... 101281 Trying to connect... 121718 Trying to connect... 142156 Trying to connect... 162593 Trying to connect... 183031 Trying to connect... 203468 Trying to connect... 223906 Trying to connect... 244343 Trying to connect... 264781 Trying to connect... 284781 **** SimConnect open event not received in required time limit: Re-connecting now... 285000 Trying to connect... 305000 **** SimConnect open event not received in required time limit: Re-connecting now... 305218 Trying to connect... 325218 **** SimConnect open event not received in required time limit: Re-connecting now... 325437 Trying to connect... 346343 Failed on SimConnect_Open for AI Traffic Client, return = 0x80004005 FSUIPC7.log
John Dowson Posted July 24 Report Posted July 24 As I said, can you please exit FSUIPC7 before attaching log (and ini) files. But your log shows that FSUIPC7 couldn't establish a connection to MSFS. First, you started MSFS manually, and it looks like you did this before MSFS was running. If starting manually, you should start FSUIPC7 after starting MSFS, and one MSFS has arrived at the main menu. However, it is far better to use the auto-start feature so that FSUIPC7 is started by MSFS when ready. To use auto-start, please re-install and leave the selected components (to install) as they are. For details on tuning the start-up parameters for preventing connection issues, see the following FAQ entry.: Note that once you have configured the DetectToConnectDelay / DetectToConnectDelayAuto parameters correctly, you can also set the InitialStallTime parameter to 0 which will then instruct FSUIPC7 to wait indefinitely for a response to the connection request. Also see the section Auto-tuning of initial start-up ini parameters on page 11 of the Advanced User guide. John
electricclay2000 Posted July 24 Author Report Posted July 24 (edited) Edit: pasted files de;eted = see next comment Clayton fsuipc log and ini files Edited July 25 by John Dowson unneeded pasted files removed
John Dowson Posted July 25 Report Posted July 25 I don't know why you pasted both your log and ini in your last post - I have removed them. They did not add anything new. I was just reminding you to exit FSUIPC7 before showing me files and did not need to see the same one again. And if a file is more than 10 or 20 lines, please attach it rather than pasting it - and this does not mean that I want you to attach them now. Only attach if you have followed my instructions and it is still not working. As for your issue, please re-read my last comments and report back, As I said, try starting FSUIPC7 after MSFS has started and arrived at the main menu, or use the auto-start feature. And if you get the same connection issues, read that FAQ entry and manually configure the initial connection parameters - and read the section on auto-tuning of start-up parameters in the Advanced User guide. John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now