Jump to content
The simFlight Network Forums

danewatson

Members
  • Posts

    79
  • Joined

  • Last visited

Posts posted by danewatson

  1. Thank you John.  I will try to explain a bit better, actually when I load MSFS I always use the FSUIPC7 .bat file that you provide named MSFS.  Prior to this last FSUIPC7 update I never had an issue, but now when MSFS loads as well as FSUIPC7, when I go to use some keyboard commands for my Lua script nothing works.

    So I always have to exit FSUIPC7 and restart it - then everything is perfect.

    Attached are my ini and lua files

    FSUIPC7.ini NpCforMSFS2020.lua

  2. Since this version I have noticed a problem I did not have before.  I have been using the same Lua file for a very long time to control radios, etc. and I notice that if I change planes by going back to MSFS World Map and load up a different plane FSUIPC7 looses connection to MSFS and my Lua script does not function, so I exit FSUIPC7 and reload it and all is OK.

  3. 8 hours ago, Pete Dowson said:

    You probably set an option in LRM to get it to load automatically, or it is loaded by an entry in MSFS's EXE.XML (like FSUIPC7). It isn't being started by FSUIPC7.

    LRM is using FSUIPC to operate. When your system is loaded your aircraft is placed on the runway, and I  expect LRM treats that as a good landing. If you don't run FSUIPC7 then LRM can't get information from MSFS.

    Pete

     

    Thank you Pete

  4. On 4/1/2021 at 2:47 AM, jaxx said:

    Could it be another tool that connects through FSUIPC? I know that for example Landing Rate Monitor has the option to play clapping on good landings.

    You are absolutely correct, thank you... See my reply to John...

  5. 3 hours ago, Milan Putnik said:

    Dear Dane,

    I hope mr.Dowson finds anything in your FSUIPC ini and the most recent log you sent, that might eventually point to the cause of the applause you're hearing.

    For the time being, start your flight and keep the main UI of VoiceMeeter open. Keep an eye at the local section of apps for audio activity - I hope that you have your main virtual B1 local input bus mapped to your hardware A1 with your Realtek integrated sound card tied to it and set as the default audio device ?

    That is used by the simulator, so make sure the applause you are hearing is coming from the B1 - and also that you hear it from the A1 !

    Because you have a few more devices there, and I see you also route 3 virtual audio cables - you also maybe use VBAN for interfacing any sound devices or streams within your LAN.

    Anyway, take a good look at all those sources, start the VB monitor for each of those buses and find out where the applause is coming from - you can identify the source executable if it is coming from any of the local virtual sources, it will appear on the main VoiceMeeter UI.

    But...if you use ASIO on A1, then all of this is done differently - although if you are familiar with the ASIO routing and you have your audio system set up trough it, you surely know what you're doing and have every single bus/line/channel clearly in your mind.

    The point is that you have a full small home audio routing system with mixing in place of the default Windows OS audio system - you should search for the source of that applause trough it.

    Thank you Milan for offering your help - yes I do use VoiceMeeter Banana for my sound control and then when recording a video it is linked to OBS.

    I have found the source of my issue - see my response to John...

  6. 6 hours ago, danewatson said:

    John - I stand to be corrected.  ver. 7.0.5 also causes the applause sound.  However, when I start MSFS without FSUIPC7 (by renaming the FSUIPC7.exe file) the sound file does not get activated.  That's why I originally thought it had something to do with FSUIPC7 - but I certainly could be wrong.

    I will try to search through sound files in my system - this could be a huge job, but will give it a go.

    John, after much searching through my system I have found the source of the sound file triggering the applause of clapping, but I don't understand why all of a sudden this is happening.

    The sound file is coming from an addon for P3D.  I installed this addon in 2019 when I was using P3D but have not flown P3D since MSFS was launched.  The file addon is Landing Rate Monitor (LRM.exe).  I have turned the source off by renaming it and now I do not get the clapping.

    The big question is why or how is it being triggered by FSUIPC7?

    EDIT: I decided to uninstall LRM as I no longer use or need it.

  7. 1 hour ago, danewatson said:

    Thanks John, sorry for my delay, I was away.  As I said when I install ver. 7.0.5 I do not get this applause sound file.  Attached are my ini and log files.

    FSUIPC7.ini 4.63 kB · 0 downloads FSUIPC7.log 5.91 kB · 0 downloads

    John - I stand to be corrected.  ver. 7.0.5 also causes the applause sound.  However, when I start MSFS without FSUIPC7 (by renaming the FSUIPC7.exe file) the sound file does not get activated.  That's why I originally thought it had something to do with FSUIPC7 - but I certainly could be wrong.

    I will try to search through sound files in my system - this could be a huge job, but will give it a go.

  8. This may sound strange - but recently over the past week when I load MSFS and as it gets to the World Map window there is applause of clapping, also upon touchdown at landing.

    It has taken me a couple days and the process of elimination to discover that FSUIPC7 ver.7.0.8 is activating this.  My previous version was 7.0.5 (maybe I missed those between 7.0.5 and 7.0.8) and maybe there is documentation about this which I have missed.

    Please confirm to me is this is correct and if so can it be controlled?

    Regards, Dane

     

    EDIT - to add a very short video of the applause sound file...

  9. On 3/23/2021 at 7:03 AM, Roland said:

    I think I found a solution for the exe.xml problem.

    There are to cases that work

    If FSUIPC7.exe is set to start as administrator, you must start MSFS with admin rights.

    If FSUIPC7.exe is NOT set to start as administrator, do must start MSFS WITHOUT admin rights.

    Every other combination does not work.

     

    Roland - I agree, I have verified this as well.  However I do not know how to check if MSFS is starting with or without Admin rights.  But I have found that if I uncheck FSUIPC7.exe "Run this program as administrator"  then it auto starts as it should.  The minute I run as administrator it will not startup.

  10. 4 hours ago, ricktana said:

    John and Dane,

    The EXE.xml files I shared were all created by me based on what I saw other users doing in their setups. As I stated in my post, all 3 of the Example EXE.xml files I shared were tried and worked in my case.  Including  the one with the Type=" Simconnect". 

    Example 1, (attached) is the one created by FSUIPC, edited with the individual lines shown on top of one another rather than running together.  I find it easier to read this way.  It has the CommandLine option (-auto) and the <NewConsole> entry. It is also the EXE.xml  I am currently using. I don't fully understand how xml files work, I just know in my case that they do.

    Another note: I am starting MSFS using the MSFS icon, not the FSUIPC7 icon. I did not try all 3 Examples using the FSUIPC7 icon to see if they worked.

    Rick S.

    EXE_EXAMPLE-1.xml 1.25 kB · 0 downloads

    Greetings John and Rick,

    Thanks John for trying to help me with this, but it is still not working.

    Thanks Rick for explaining how you created your EXE.xml files - I just know that the only way I can get MSFS and FSUIPC7 started through the MSFS.bat file is by doing it the older (previous) way - that is to say, by removing the commented out commands as you see here...

    :: wait for MSFS to start (2mins)
    timeout /t %delay% /nobreak > NUL

    :: start FSUIPC7
    start "" "C:\FSUIPC7\FSUIPC7.exe"

    II have no clue how an xml file works but I do know that for my system this one does not work - I may have something that is a problem????

  11. 8 hours ago, John Dowson said:

    Thats fine, but as this seems to be an ongoing issue I'd like to know what is causing this and if there is anything I can do to get around this.

    Another user has reported an interesting observation with the EXE.xml (not starting programs more than one folder deep), but it doesn't apply in your situation  - see

    Can you show me/attach your EXE.xml file again please. If that has the correct format and is in the correct location, I do not understand why MSFS isn't picking it up in your installation.

    Greetings John,  I notice in the example EXE.xml files from Rick S that his EXE.xml file structure/coding is different - here is a copy/paste of his first few lines...

    Rick's EXE.xml

    xml version="1.0" encoding="Windows-1252"?>
    <SimBase.Document Type="Simconnect" version="1,0">
        <Descr>Launch</Descr>
        <Filename>EXE.xml</Filename>
        <Disabled>False</Disabled>
        <Launch.Addon>
            <Name>FSUIPC7</Name>
            <Disabled>False</Disabled>
            <Path>D:\FSUIPC7\FSUIPC7.exe</Path>
            <CommandLine></CommandLine>

    This is my EXE.xml

    <?xml version="1.0" encoding="Windows-1252"?>
    <SimBase.Document Type="Launch" version="1,0"><Descr>Launch</Descr><Filename>EXE.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad><Launch.Addon><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Name>FSUIPC7</Name><Path>C:\FSUIPC7\FSUIPC7.exe</Path><CommandLine>-auto</CommandLine><NewConsole>False</NewConsole></Launch.Addon></SimBase.Document>

     

     

     

    I am attaching my EXE.xml file again for you to review.  Also as Rick stated, he found that the FSUIPC7 file should only be one level deep, as is mine (C:\FSUIP7\FSUIPC7.exe)

    EXE.xml

  12. 5 hours ago, John Dowson said:

    The FSUIPC entry added is correct, but the rest isn't! Something else must have written that before you installed FSUIPC, and made a bad job of it....

    Change:

    
    <?xml version="1.0" encoding="WINDOWS-1252"?>
    <SimBase.Document version="1,0" Type="SimConnect">
        <Descr>SimConnect</Descr>
        <Filename>SimConnect.xml</Filename>
        <Disabled>False</Disabled>

    to

    
    <?xml version="1.0" encoding="Windows-1252"?>
    <SimBase.Document Type="Launch" version="1,0">
        <Descr>Launch</Descr>
        <Filename>EXE.xml</Filename>
        <Disabled>False</Disabled>
    

    Leave the FSUIPC7 entry as it is.

    Than try again. You should also commend-out the start of FSUIPC7 from the MSFS.bat file so it doesn't try and start two copies.

    Or you could just delete that EXE.xml and re-install. It will be re-created with the correct format.

    John, I followed your directions - but I am afraid it did not help.  I then deleted the EXE and I re-installed FSUIPC7 - but that also did not help.

    So I went back to the MSFS bat file and removed the commented-out two lines as shown here and FSUIPC7 starts-up along with MSFS ---

    :: wait for MSFS to start (2mins)
    timeout /t %delay% /nobreak > NUL

    :: start FSUIPC7
    start "" "C:\FSUIPC7\FSUIPC7.exe"

    I am OK with that as long as you are as well?

    Dane

  13. 6 hours ago, John Dowson said:

    That is not the issue! You have reverted to the previous way of starting FSUIPC7, directly from the batch file rather than having it started by MSFS using the EXE.xml.

    You log file shows the EXE.xml was updated:

    Could you show me that file please.

    I have had one or two other reports of the EXE.xml not being processed correctly by MSFS. I'm not sure why this is, but if the EXE.xml is as it should be, then for now you will have to use the old method, as you are now doing.

    Here you are John, my EXE.xml file.

     

    Dane

    exe.xml

  14. 7 hours ago, John Dowson said:

    There is no change in this in v7.0.5. Are you sure you selected to install the auto-start component? Try re-installing to make sure, and if you have the same problem show me your install log file.

    Thanks John I have in fact re-installed it three times now and yes the Auto Start Component is checked - see attached.

    Also attached is my Install Log.

     

    Regards, Dane

    Auto Start Component.JPG

    InstallFSUIPC7.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.