Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,034
  • Joined

  • Last visited

  • Days Won

    267

Everything posted by John Dowson

  1. The installer for 7.4.12 is exactly the same as the installer for 7.4.11, only the files that are installed have changed. Maybe you can download and try the latest beta: Install_FSUIPC7.4.13b Do you get the same issue?
  2. Can you please download and try this beta: Install_FSUIPC7.4.13b Please add TestOptions=x800 to the [General] section of your FSUIPC7.ini file, and show me your files again if you get an issue. John
  3. Can you please download and try this beta: Install_FSUIPC7.4.13b Please add TestOptions=x800 to the [General] section of your FSUIPC7.ini file, and show me your files again if you get an issue. Also keep Debug level logging in the API for the time being. Did you check your installation location? Still puzzled as to why you can't supply a log file... John
  4. Can you please download and try this beta: Install_FSUIPC7.4.13b Please add TestOptions=x800 to the [General] section of your FSUIPC7.ini file, and show me your files again if you get an issue.
  5. Yes, do that. But this would be an issue for new users who need to validate their registration. But, as I have said, I have no idea why this message box cannot be closed. Very strange. There seem to be a lot of issues with the latest MSFS update at the moment and I really don't have time to look into this installer issue, and do not have a clue as to why it is doing this. It is very strange... I would like to know what folder is being installed into - it may be something to do with file permissions when creating the FSUIPC7.key file, if FSUIPC7 is being installed under a windows-protected folder. Still, I wouldn't expect the installer to hang... John
  6. For the WASM crash issue, can you please download and try this beta: Install_FSUIPC7.4.13b Please show me your files again if you get an issue. John
  7. But you only need to press this once - it will validate both keys on one press, and you should see a pop-up message for each. So, you press Register, a message is display regarding your FSUIPC7 registration. When you close this window, a new message should be displayed with the result of your WideFS registration. Then how can you press the Register button twice? The message pop-up is modal so you cannot press anything in the installer window until the message is closed. Does the red X in top-right corner also not close the message? And remember, you only need to register once. You do not need to re-register each time you update FSUIPC7. but doing so should cause no issues, and I really don't understand this issue, and can think of nothing that could cause this weird problem.
  8. What works? Do you have the MSFS Desktop icon that the installer creates AFTER the registration process? I suspect not if you are killing the installer - although this maybe created now by the MSFS.bat auto-start component (not sure). Can you please re-run the installer and validate again. Do you get the same issue? If so, please check the Windows Event Viewer for any events related to the installer, and if there are any, then save them and attach them here. If you get the same issue, kill the installer, then run it again. This time, skip registration, and you should get to the last page where the desktop icon is created. Do this and finish the installation process, then show me/attach your InstallFSUIPC7.log file. John
  9. Windows does not add an application to the sound mixer until a sound is played from the application. Once FSUIPC has been instructed to play a sound, it should appear. This is how windows works, nothing to do with FSUIPC. John
  10. I am sorry, but that image doesn't tell me anything. It doesn't even show an FSUIPC7.ini file, and I can't tell if that image shows all files in your installation folder, i.e image cropped and not showing scroll bar. At least click on the name to get the files sorted in alphabetical order... You must have an ini file and a log file. Are you sure that is the correct installation folder? If there is no log or ini file there, I think you may be confused as to where you have actually installed FSUIPC7.... When FSUIPC7 is auto-started, use File -> Open Installation Folder to check the folder that is being used. Your log file will be there. Also, can you also please activate Debug level logging in for the WAPI (Log -> WAPI -> Debug).
  11. I have no idea why it cannot install the documents. Are you changing the default installer options? i.e. why is it skipping the hvar files? Please attach your InstallFSUIPC7.log file.
  12. @alexanderluzajic Can you PLEASE read my comments - I am not going to respond to you here, please use your original topic. And I responded to your response., in your original topic.
  13. You do not seem to be using FSUIPC for much - just one button assignment, and one lua running for all aircraft (A320ParkBrake). You have two profiles. but both of these are empty. Your log shows that you have a very long start-up time for MSFS. You have DetectToConnectDelayAuto set to 5 mins (300 seconds) but this still doesn't seem to be enough: From this log, you should set DetectToConnectDelayAuto to 490. Apart from that, your log shows that you didn't start a flight until over 17mins after starting FSUIPC7, and it looks like there was no response from the WASM and so no lvars were loaded and your lua auto wasn't started. I am looking into this issue, reported by many, so please be patient. There will be a new release in the next day or two, John
  14. I have no idea what you mean. Please take care to explain your issue, and provide your files that show the issue - the FSUIPC7.log and FSUIPC7.ini files. Many people are having issues when FSUIPC7 is auto-started. If you exit FSUIPC7 once it is auto-started and then manual start FSUIPC7 does it work? If so, then it is the start-up parameters that are causing the issue. Read the section on this in the Advanced User guide, and post your files here, together with an explanation of your issue and I will take a look. Settings are NEVER lost - they will be in your ini file. They may not be loaded though, and that can be for many reasons, but the usual culprit is using an aircraft that does not match the aircraft names in your profile, as you have not edited them to use substrings for matching. But I cannot tell you anything from a rant/post without showing any supporting information. John
  15. I presume it is this one: If so, please post in that topic. If so, I have already responded there - have you read that response? I have no idea why people are having such problems with the installer - there has been no change in the installer for a long time (over a year), except for the files that it installs. Do you have an InstallFSUIPC7.log? If so, show me that. But PLEASE use the topic you created for your issue, and not post in topics for other issues which are not the same. And make sure you run the installer from Windows Explorer, not in WinRar.
  16. I am just letting you know that I cannot do anything about this until you supply me with the files I need to investigate. There is no point in you posting again until I have these, I have been waiting to see this since your original post. If you want me to look into this, provide the files/information I need. Otherwise there is no point posting about this issue. You started this topic for your issue, I asked for the files to investigate - since then I have been waiting for the correct files.
  17. But what solution? Killing the installer via the task manager is not a solution to this problem - it just stops the installer from completing. Did you do anything to actually resolve this issue? When you validate your license, does the installer hang once the validation success message has been displayed? If not, and you previously had this issue, what did you do to correct this?
  18. Your lua script looks ok. That is because they are NOT events (or k-type variables). They look to be Input Events (or B-type variables). Try listing Input Events - are they listed? You can use Input Events like other events - either assign to them directly (by checking Select for Input Events), and in lua you can use the ipc.execInputEvent function. Please see the Advanced User manual on Input Events, and the FSUIPC Lua Library manual for details on lua library functions for Input Events. John
  19. Sorry, but there is nothing I can do about this issue - there is nothing wrong with the installer. The only thing I can recommend is to update your VC++ redistributables, as described in both the README.txt and in the Installation and Registration guide. When you click Register, is the FSUIPC7.key file generated? That is what this button does - it validates your registration details and generates the FSUIPC7.key file. There may be an issue with this if trying to install into a windows protected folder (e.g. under Documents or Program Files). If this is the case, choose another non-windows protected folder. And please be aware that if you have already registered once, and you have a valid FSUIPC7.key file, you do not need to register when you re-install. Just click Skip - no need to re-register. Other than that, there is nothing more I can say about this issue. John
  20. Please do not posts requests in the User Contributions sub-form - this is for contributions only. It does say NOT for support requests. What version of FSUIPC are you using? I will move your post... Should be relatively straight-forward. To get started, check-out some of the other lua sound plugins available: John
  21. That is interesting... Does that add-on continually create lvars by any chance? I think there could be issues with FSUIPC7 when using add-ons that continually create lvars, due to the way FSUIPC WASM pushes newly created lvars out to FSUIPC7. I will add a fix for this (as detailed in my comments above) in the next release. John
  22. But why? Re-installing will do absolutely nothing. I know, you have said this already. I am still waiting to see a log file from you when PACX was NOT working, i.e. when FSUIPC7 was auto-started. I do not understand the difficulty you are having in providing me with this file. I have no idea why it is not connecting and cannot help you if you do not show me this file. John
  23. First, you posted in the main support forum. For all FSUIPC7 issues, please use the specifc sub-forum for FSUIPC7. I have moved your post. If you want help, you have to explain what your issue actually is. Just saying it doesn't work or you are unable to use an aircraft doesn't help. And I also need to see your files - your FSUIPC7.log and FSUIPC7.ini files, with a description of what is actually not working. There are also several other similar support requests that I am currently looking into. Also, if FSUIPC7 is being auto-started, try exiting it and then re-starting it. Do you then get the same issues?
  24. K-type variables are events/controls. Simulator variables, or simvars, are a-type variables. All events (i.e. k-type variables) are available, either for assignment via the UI, or in lua you can use the ipc.control function. The number for the TOGGLE_EXTERNAL_POWER event is 67090 (see the file Controls List for MSFS Build 999.txt in your FSUIPC7 documents folder for a list of controls with there corresponding event number. You don't need to use lua, you can just assign to it. If you want to use lua, it would be ipc.control(67090, 1) or you can use the calc. code directly, i.e. ipc.execCalcCode("1 (>K:TOGGLE_EXTERNAL_POWER)") John
  25. And how did you solve it then? There is really nothing I can do about such an issue. No idea what could cause this - this is either a windows issue, or possibly caused by trying to install into a windows protected folder. This is NOT an issue with the installer. Maybe check the Event Viewer to see if any error are logged for the installer.
×
×
  • 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.