zap737
-
Posts
37 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by zap737
-
-
Well, I'm amazed ! Success !!!! It's working again Thanks a lot John.
I have one other annoying duplicated entry in the registry...
WARNING: Joystick ID 1 is duplicated in Registry
Device acquired for use:
94 Joystick ID = 1 (Registry okay)
94 1=FSSB R3 MJF
94 1.GUID={30AFDF00-6DD4-11ED-8005-444553540000}Product= FSSB R3L MJF J+B
94 Manufacturer= RealSimulator
94 Vendor=12E0, Product=2001 (Version 0.2)
94 GUIDs returned for product: VID_12E0&PID_2001:
94 GUID= {30A382F0-6DD4-11ED-8004-444553540000}
94 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0How can i find the duplicated entry and delete it.
I have already tried running the same procedure as i did for the Zapbox with a removeFSSB.reg file but it didn't work.
-
Ahh ok. Will try and report back.
-
Hi John, I'm not clear on how running that removeZapBox.reg you cited will remove the registry entries. Won't it add those entries?
The device does not have a specific driver to install. It's just plug and play.
-
Hi John, some more info. I have another computer with identical Windows 11 setup and fully updated. When I installed FSUIPC on that computer and connected the same controllers, more than 31 buttons were fully recognized !!!
Could this be a registry issue ?
I have tried many times to uninstall and reinstall FSUIPC on the problematic computer but no joy.
I don't want to have to re-install Windows to fix this problem.
Is there some way of removing all trace of FSUIPC from the problematic computer - including the registry and then trying again ?
Am I clutching at straws ?
-
Hi John, I disabled vJoy but still no buttons > 31.
-
Hi John, vJoy is a virtual joystick and is required for use with Joystick Gremlin which can combine many joysticks with advanced functions.
It doesn't have any buttons itself, however it is the solution to the problem because I can map all of the buttons greater than 32 to this vJoy device using Joystick Gremlin and it is now seen by FSUIPC. In fact I can create multiple vJoy devices and I could break up a large controller with many buttons into multiple.32 button vJoy devices.
Thanks,
-
There were no assignments because I had just reinstalled FSUIPC and wanted to see if any buttons above 32 were recognised in the assignments dialog.
The controller with 71 buttons is: E=ZapBox GUID={A0745EA0-69ED-11ED-8007-444553540000}
Any button less than 32 was recognised in the console window. Anything above 32 there was nothing registered in the console window - see attached image.
Log attached
-
Files attached. Thanks
-
Hi, I have the latest FSUIPC version 7.3.15
I have a controller with 71 buttons and all the buttons work in other games.
However in FSUIPC only 32 buttons can be assigned through the interface.I have tried uninstalling and reinstalling FSUIPC but no luck.
Thanks.
-
Thanks again John, I'll get to it.
-
Thanks John. I think I'll move to using Presets and do away with the .evt files entirely.
I couldn't find the provided myevents.txt file so I made one myself - I suppose that's OK ?
As the events.txt file is so large, how can one reliably find ALL the entries for a particular aircraft and then copy them to the myevents file ?
On Hubhop, I tried to filter out just the ones I needed (e.g A32NX) but when I went to export, it gave me the entire events.txt file !
-
Hi, I have the latest version of FSUIPC 7 - 7.3.15.
Is the Mobiflight WASM required to be installed in the Community folder to have event files work ? The reason I ask is that I do NOT have it installed and it does seem to work.
Is the Mobiflight WASM required to be installed in the Community folder to have the events.txt (Mobiflight/HubHop file) work ? Again, I do NOT have it installed and it does seem to work.
Is is best just to have myevents.txt ONLY in the FSUIPC directory or can I have both the events.txt & the myevents.txt in the FSUIPC directory ?
Thanks
-
Hi,
I have a Lua file which runs automatically and detects whether a button is pressed for a short time or a longer time.
This emulates the push and pull function of the FCU Alt, and Speed knobs on the A32NX which engage the managed or selected functions.
The FSUIPC>AddOns>WASM>Execute Calculator Code works if I execute it within the FSUIPC Interface, but the code in the LUA does not work.
If I execute the following pull event within FSUIPC>AddOns>WASM>Execute Calculator Code, it works
(>H:A320_Neo_FCU_ALT_PULL) (>H:A320_Neo_CDU_MODE_SELECTED_ALTITUDE)
Same for Push.... It works fine within FSUIPC>AddOns>WASM>Execute Calculator Code
(>H:A320_Neo_FCU_ALT_PUSH) (>H:A320_Neo_CDU_MODE_MANAGED_ALTITUDE)
So, the attached Altitude LUA code does not work.
However, the attached LUA file for speed (which is virtually identical), DOES work !
Yes, I have confirmed the button and joystick numbers are correct.
My FSUIPC INI file is also attached.
-
3 minutes ago, John Dowson said:
Ok, then as suspected the error is being displayed by windows after FSUIPC has exited but before the process has finally stopped. I'm afraid that there isn't anything I can do about this.
OK no problem. It is probably something particular with my system. Anyway, I have a good work around. Thanks again.
-
Hi John,
Please note, I had already deleted the changes you had asked me to previously make below.
LogLevel=Debug
LvarUpdateFrequency=6LvarUpdateFrequency=Off
So I used your new FSUIPC.exe without those entries above...
The console log showed as below before I acknowledged pop up......
Console Started ...
216938 3616 === FSUIPC has been stopped
216984 3616 === FSUIPC main window destroyed
216984 3616 === FSUIPC window hooks removed
216984 3616 === Critical sections deleted
216984 3616 === Closing log file....Bye!
216984 System time = 17/06/2021 21:01:49
216984 3616 *** FSUIPC log file being closed
Minimum frame rate was 26.7 fps, Maximum was 117.2 fps
Average frame rate for running time of 157 secs = 65.9 fps
Maximum AI traffic for session was 47 aircraft
Traffic deletions 0 aircraft
Memory managed: 27 Allocs, 26 Freed
********* FSUIPC Log file closed ***********
FSUIPC log also attached
-
19 hours ago, John Dowson said:
Does it also occur if you start FSUIPC7 (without MSFS) and then exit?
No it does not occur.
18 hours ago, John Dowson said:- if using an in-game overlay (e.g. GeForce experience, etc), then maybe try disabling that
I disabled it and no difference
18 hours ago, John Dowson said:check you are up-to-date with the latest windows updates
Yes up to date
18 hours ago, John Dowson said:update your .Net framework
I found I did not have .Net 3.5 installed but I did have 4.8 installed. So I installed 3.5. No difference.
18 hours ago, John Dowson said:run the system file checker (run the command sfc /scannow from an admin command prompt)
One of the first things i did. No issues with resource integrity.
18 hours ago, John Dowson said:check your windows Virtual Memory settings
Mine is system managed on the C drive with 9.7 GB allocated (I have 64 GB of ram)
18 hours ago, John Dowson said:Have you always had this error or is this something new?
Version 7.1 seemed fine. Just started with 7.2
-
10 minutes ago, John Dowson said:
Can you try disabling/unchecking the 'Exit with FS' option. Then when MSFS closes FSUIPC should stay open. Once MSFS has closed, give it a few seconds and then exit FSUIPC.
If you do this, do you still get the error, and if so, when?OK I waited quite a while after MSFS shut down with Alt F4 - well after the cockpit noises stopped - then I exited FSUIPC from the tray icon. Then after about 3 seconds the error popped up.
John it's close to midnight here in Australia so I will have to sign off.
Thanks for your help but I have work arounds for both problems.
I can try some more things if you want to tomorrow.
regards,
Peter
-
47 minutes ago, John Dowson said:
Does the same happen when quitting MSFS from FSUIPC (using the MSFS -> Exit oprion)?
Yes.
47 minutes ago, John Dowson said:Doesn't the logging pause when the pop-up error is displayed? Is that displayed before or after the console log window closes?
No. MSFS disappears, then the logging closes, then the FSUIPC interface disappears, then the pop up error displays.
47 minutes ago, John Dowson said:What about when exiting MSFS from FSUIPC7?
Same problem exactly. Log attached....
47 minutes ago, John Dowson said:Also, can you let me know when this pop-up error occurs, and what happens when it does. Does the FSUIPC7 window/icon and console window disappear before this message is display, or after?
MSFS disappears, then the logging closes, then the FSUIPC interface disappears, then the pop up error displays.
40 minutes ago, John Dowson said:47 minutes ago, John Dowson said:I'm going to try closing with Alt-F4 now to see if that makes a difference....
Nope, still no error for me....very strange....
Well I'm stumped !!
-
22 minutes ago, John Dowson said:
The Exe.xml looks fine. From what folder is it located? Presume you have a MS Store version, and it is under C:\Users\Peter\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache, no?
You could try switching to using the SimConnect document type rather than Launch (as I have seen that this is used quite often). Please change your EXE.xml file to the following:Yes it is in that path but I do have MSFS installed to a separate drive so the C:\Users\Peter\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe part is on my C drive and then it puts a shortcut to localcache from the c drive to the separate hard drive, but yes the path is the same.
The simconnect version did not work.
-
43 minutes ago, John Dowson said:
Once thats done, you couldalso try switching to updating lvars from the client (if not doing that already), by adding this line to the [WAPI] section of your FSUIPC7.ini file:
LvarUpdateFrequency=6
(that is for 6 updates per second). You should also disable updates from the WASM by setting the following in your FSUIPC_WASM.ini - either in your Packages folder, if you have an FSUIPC_WASM.ini file there, or under the fsuipc-lvar-wasm folder (in your MSFS Community folder) if not):
LvarUpdateFrequency=OffSo I did this part as well and I get the same error again when I hit Alt F4. Log file attached.
-
43 minutes ago, John Dowson said:
Could you activate logging for Extras on FSUIPC, and also activate Debug logging in the WAPI by adding this line to the [WAPI] section of your FSUIPC7.ini file:
LogLevel=DebugCould you also have the logging console open when you close down (Log -> Open Console), and let me know what the last message logged is when that error appears.
Send me the log and let me know when the error occured.Ok so I did this part and I still get the error, but when I hit Alt-F4, the console window closed too quickly for me to catch the last message but I have attached the log file for you
-
Hi John,
I changed the start of the lua files to [Auto] in the ini file.
Some interim findings.
For both the Dev and Stable versions of the A32NX, when I exit to the main menu then exit to desktop there is no error message.
However, when I exit a flight using Alt-F4 without going back to the main menu, then I get the error.
I am not au fait with the client side of things but I will attempt to do what you asked.
Also, when I install FSUIPC and ensure a tick is placed in the "Start with MSFS" box, I find that FSUIPC does not start with MSFS. I have checked the Exe.xml (attached) and all seems ok there. The only way I can get it to automatically start with MSFS is to edit out the comments in the bat file.
Any ideas on this one ?
-
Here is the ipcReady.lua file...
I will try the [Auto] section.
It will take me a little while to do the other tests..
-
Hi John, files attached.
Yes it does happen every time on exit but the Lua files work fine.
It is the development version of the A32NX
FCU_Hdg.lua FCU_Speed.lua FCU_VS.lua FSUIPC7.ini FCU_Alt.lua
FSUIPC 7 not recognising More than 32 buttons
in FSUIPC7 MSFS
Posted
Yep, exactly what happens, they get added again !!!