Jump to content
The simFlight Network Forums

Fastlaunch

denwagg

By denwagg
in FSUIPC7 MSFS

 Share

Recommended Posts

denwagg Newbie

denwagg

Posted
Posted

How can I add the -Fastlaunch parameter to the detault FSUIPC7 Startup bat file

-------------------------------------------------------------------------------------------------------------------------------------

@echo off &setlocal 

:: remove CMD window
if not DEFINED IS_MINIMIZED set IS_MINIMIZED=1 && start "" /min "%~dpnx0" %* && exit

:: STEAM installation: start MSFS
start "" steam://rungameid/1250410


:: these variables will be expanded in the HTA code
:: duration and animated dots per second
set /a dur = 30
set /a adps = 3
:: width or height = 0 will set splash image to half your screen size
set /a width = 0
set /a height = 0
:: image from MSFS web site
set "imageurl=https://msfs-cdn.azureedge.net/wp-content/themes/publishing/dist/images/desktop-hero_8711a4cf.jpg"
:: message displayed above image
set "waitmessage=<b>We are preparing the cabin<br>Please wait</b>"

:: Variable to hold delay (in seconds) after MSFS has been started and before FSUIPC7 is started
set /a delay = 120

set "splash=%temp%\tmp.hta"
:: all lines beginning with min. 6 spaces are redirected into the HTA file
>"%splash%" (type "%~f0"|findstr /bc:"      ")
:: cmd.exe /C start mshta "%splash%"
start mshta "%splash%"

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

:: start FSUIPC7
start "" "F:\FSUIPC7\FSUIPC7.exe"
:: start "" "F:\Pushback Express MSFS\Pushback Express_x64.exe"
:: start "" "F:\Flight Crew A320 MSFS\Flight Crew A320_x64.exe"
:: start "" "F:\Pilot2ATC_2020_x64\Pilot2ATC_2020.exe"
exit
:: End Of Batch

      <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "xhtml1-transitional.dtd">
      <html xmlns="http://www.w3.org/1999/xhtml">
        <head>
          <title>MSFS 2020 Splash Screen</title>

          <hta:application
           id="oHTA"
           applicationname="MSFS 2020 Splash Screen"
           border="thin"
           borderstyle="normal"
           caption="no"
           contextmenu="yes"
           icon=""
           innerborder="no"
           maximizebutton="no"
           minimizebutton="no"
           navigable="no"
           scroll="no"
           scrollflat="no"
           selection="no"
           showintaskbar="no"
           singleinstance="yes"
           sysmenu="no"
           version="1.0"
           windowstate="normal"
          />

          <style type="text/css">
            body      {margin:0px 0px 0px 0px;}
            .splashscreen {position: relative;}
            .ctext {
                    position: absolute;
                    top: 5%;
                    left: 10%;
                    text-align: left;
                    font-size: 3em;
                    font-family: "verdana";
                    color: orange;
            }
            </style>

          <script type="text/jscript">
            /* <![CDATA[ */
            
            var oWSH=new ActiveXObject("WScript.Shell");
            var i=parseInt(oWSH.ExpandEnvironmentStrings("%dur%"));
            var a=parseInt(oWSH.ExpandEnvironmentStrings("%adps%"));
            var w=parseInt(oWSH.ExpandEnvironmentStrings("%width%"));
            var h=parseInt(oWSH.ExpandEnvironmentStrings("%height%"));
            var s=oWSH.ExpandEnvironmentStrings("%imageurl%");
            var wm=oWSH.ExpandEnvironmentStrings("%waitmessage%");
            var wm1 = wm + " .  ";
            var wm2 = wm + " .. ";
            var wm3 = wm + " ...";
            if (w == 0) w = screen.width / 2;
            if (h == 0) h = screen.height / 2;
            window.resizeTo(w, h);
            window.moveTo(screen.width / 2 - w / 2, screen.height / 2 - h / 2);
            var j = n = 0;
            var m = a * i;
            var t = 1000 / a;

            function start() {
              window.focus();
              image.src = s;
              image.height = h;
              image.width = w;
              n = j % 3;
              wm = (n == 1) ? wm1 : (n == 2) ? wm2 : wm3;
              document.getElementById("msg").innerHTML = wm;
              if (j++ < m) setTimeout('start()', t);
              else window.close();
            }
            /* ]]> */
          </script>

        </head>
        <body onload="start()">
          <div class="splashscreen">
            <img id="image" src="" alt="" height="0" width="0" /> 
            <div class="ctext" id="msg"></div>
          </div>
        </body>
      </html>

--------------------------------------------------------------------------------------------------

Regards and thank you

Dennis

 

John Dowson Grand Master

John Dowson

Posted
Posted
14 hours ago, denwagg said:

How can I add the -Fastlaunch parameter to the detault FSUIPC7 Startup bat file

The '-FastLaunch' option is automatically added to start MSFS store installed versions, but I don't think this is possible with the steam version as a command line parameter.

To use this option with steam, open your library in Steam, right-click on MSFS and select Properties. Under the General tab, click SET LAUNCH OPTIONS, then enter -FastLaunch in the pop-up dialog.

John

Paulcoy Newbie

Paulcoy

Posted
Posted

HI. I have a registered vers and also MSFS2020 is from the Store. But my desktop icon never opens the Sim just FSUIPC7. Any help would be much appreciated

John Dowson Grand Master

John Dowson

Posted
Posted
10 hours ago, Paulcoy said:

HI. I have a registered vers and also MSFS2020 is from the Store. But my desktop icon never opens the Sim just FSUIPC7. Any help would be much appreciated

Can you please attach your installation log, and also an FSUIPC7.log file please and I'll take a look.

katoema Apprentice

katoema

Posted
Posted

Today, I noticed a new icon on my desktop for what I thought was just the starting of FSUIPC7. I was amazed that it started MSFS and FSUIPC7 together. I have the boxed Premium Deluxe version, which uses MS Store. Glad for one side that this works, but now I wonder how this will affect MSAddon Linker and the presets, as I usually launch MSFS via that app, so not to install everything in the Community folder!

Martin

 

When you start with MSFSAddon Linker, FSUIPC7 does not show that it is launched, BUT when you select Fly it shows up in the BRH corner in the "hide"box.

Paulcoy Newbie

Paulcoy

Posted
Posted (edited)

InstallFSUIPC7.log

********* FSUIPC7, Version 7.0.2 (27th November 2020) by John Dowson *********
Checking for FS path in 'C:\Users\paulc\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = E:\MSFS2020\
WebSocket server found: E:\MSFS Addons\Utilities\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
Reading options from "E:\MSFS Addons\Utilities\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Paul Coyne"
User Addr=
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       47 System time = 13/12/2020 00:45:00
       47 FLT path = "C:\Users\paulc\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
       62 -------------------------------------------------------------------
       62 Registered default HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
       78 FS path = "E:\MSFS2020\"
       78 ---------------------- Joystick Device Scan -----------------------
       78 Product= Alpha Flight Controls
       78    Manufacturer= Honeycomb Aeronautical
       78    Serial Number= E6FD38061B233B00
       78    Vendor=294B, Product=1900 (Version 0.32)
      203    GUIDs returned for product: VID_294B&PID_1900:
      203       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
      203       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
      203 Product= Saitek Pro Flight Rudder Pedals
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0763 (Version 1.1)
      203    GUIDs returned for product: VID_06A3&PID_0763:
      203       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
      203       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      203 Product= X52 Professional H.O.T.A.S.
      203    Manufacturer= Logitech
      203    Vendor=06A3, Product=0762 (Version 32.0)
      203    GUIDs returned for product: VID_06A3&PID_0762:
      203       GUID= {303FE860-AB41-11EA-8002-444553540000}
      203       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
      203 -------------------------------------------------------------------
      203 Device acquired for use:
      203    Joystick ID = 1 (Registry okay)
      203    1=Alpha Flight Controls
      203    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
      203 Device acquired for use:
      203    Joystick ID = 2 (Registry okay)
      203    2=Flight Rudder Pedals
      203    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
      203 Device acquired for use:
      203    Joystick ID = 0 (Registry okay)
      203    0=X52 Professional H.O.T.A.S.
      203    0.GUID={303FE860-AB41-11EA-8002-444553540000}
      203 -------------------------------------------------------------------
      219 LogOptions=00000000 00000001
   195062 Simulator detected
   287375 SimConnect_Open succeeded
   287375 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
   287375 MSFS version = 11.0.282174.999
   287375 Generating controls file list: 'C:\Users\paulc\Documents\FSUIPC7\Controls List for MSFS Build 999.txt'
   287375 Initialising SimConnect data requests now
   296812 User Aircraft ID not supplied -- trying default
   305156 E:\MSFS2020\Official\OneStore\asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG
   305297 flights\other\MainMenu.FLT
   306281 Aircraft loaded: running normally now ...
   307125 Aircraft="TBM 930 Asobo"
   307125 System time = 13/12/2020 00:50:07, Simulator time = 23:49:00 (00:49Z)
   352266 ---------------------- Joystick Device Scan -----------------------
   352266 Product= Alpha Flight Controls
   352266    Manufacturer= Honeycomb Aeronautical
   352266    Serial Number= E6FD38061B233B00
   352266    Vendor=294B, Product=1900 (Version 0.32)
   352266    GUIDs returned for product: VID_294B&PID_1900:
   352266       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   352266       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   352266 Product= Saitek Pro Flight Rudder Pedals
   352266    Manufacturer= Saitek
   352266    Vendor=06A3, Product=0763 (Version 1.1)
   352266    GUIDs returned for product: VID_06A3&PID_0763:
   352266       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   352266       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   352266 Product= X52 Professional H.O.T.A.S.
   352266    Manufacturer= Logitech
   352266    Vendor=06A3, Product=0762 (Version 32.0)
   352266    GUIDs returned for product: VID_06A3&PID_0762:
   352266       GUID= {303FE860-AB41-11EA-8002-444553540000}
   352266       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   352328 -------------------------------------------------------------------
   352375 Device acquired for use:
   352375    Joystick ID = 1 (Registry okay)
   352375    1=Alpha Flight Controls
   352375    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   352375 Device acquired for use:
   352375    Joystick ID = 2 (Registry okay)
   352375    2=Flight Rudder Pedals
   352375    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   352375 Device acquired for use:
   352375    Joystick ID = 0 (Registry okay)
   352375    0=X52 Professional H.O.T.A.S.
   352375    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   352375 -------------------------------------------------------------------
   394969 ---------------------- Joystick Device Scan -----------------------
   394969 Product= Alpha Flight Controls
   394969    Manufacturer= Honeycomb Aeronautical
   394969    Serial Number= E6FD38061B233B00
   394969    Vendor=294B, Product=1900 (Version 0.32)
   394969    GUIDs returned for product: VID_294B&PID_1900:
   394969       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   394969       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   394969 Product= Saitek Pro Flight Rudder Pedals
   394969    Manufacturer= Saitek
   394969    Vendor=06A3, Product=0763 (Version 1.1)
   394969    GUIDs returned for product: VID_06A3&PID_0763:
   394969       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   394969       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   394969 Product= X52 Professional H.O.T.A.S.
   394969    Manufacturer= Logitech
   394969    Vendor=06A3, Product=0762 (Version 32.0)
   394969    GUIDs returned for product: VID_06A3&PID_0762:
   394969       GUID= {303FE860-AB41-11EA-8002-444553540000}
   394969       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   395031 -------------------------------------------------------------------
   395031 Device acquired for use:
   395031    Joystick ID = 1 (Registry okay)
   395031    1=Alpha Flight Controls
   395031    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   395031 Device acquired for use:
   395031    Joystick ID = 2 (Registry okay)
   395031    2=Flight Rudder Pedals
   395031    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   395031 Device acquired for use:
   395031    Joystick ID = 0 (Registry okay)
   395031    0=X52 Professional H.O.T.A.S.
   395031    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   395031 -------------------------------------------------------------------
   425125 ---------------------- Joystick Device Scan -----------------------
   425125 Product= Alpha Flight Controls
   425125    Manufacturer= Honeycomb Aeronautical
   425125    Serial Number= E6FD38061B233B00
   425125    Vendor=294B, Product=1900 (Version 0.32)
   425125    GUIDs returned for product: VID_294B&PID_1900:
   425125       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   425125       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   425125 Product= Saitek Pro Flight Rudder Pedals
   425125    Manufacturer= Saitek
   425125    Vendor=06A3, Product=0763 (Version 1.1)
   425125    GUIDs returned for product: VID_06A3&PID_0763:
   425125       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   425125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   425125 Product= X52 Professional H.O.T.A.S.
   425125    Manufacturer= Logitech
   425125    Vendor=06A3, Product=0762 (Version 32.0)
   425125    GUIDs returned for product: VID_06A3&PID_0762:
   425125       GUID= {303FE860-AB41-11EA-8002-444553540000}
   425125       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   425187 -------------------------------------------------------------------
   425187 Device acquired for use:
   425187    Joystick ID = 1 (Registry okay)
   425187    1=Alpha Flight Controls
   425187    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   425187 Device acquired for use:
   425187    Joystick ID = 2 (Registry okay)
   425187    2=Flight Rudder Pedals
   425187    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   425187 Device acquired for use:
   425187    Joystick ID = 0 (Registry okay)
   425187    0=X52 Professional H.O.T.A.S.
   425187    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   425187 -------------------------------------------------------------------
   447062 ---------------------- Joystick Device Scan -----------------------
   447062 Product= Alpha Flight Controls
   447062    Manufacturer= Honeycomb Aeronautical
   447062    Serial Number= E6FD38061B233B00
   447062    Vendor=294B, Product=1900 (Version 0.32)
   447062    GUIDs returned for product: VID_294B&PID_1900:
   447062       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   447062       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   447062 Product= Saitek Pro Flight Rudder Pedals
   447062    Manufacturer= Saitek
   447062    Vendor=06A3, Product=0763 (Version 1.1)
   447062    GUIDs returned for product: VID_06A3&PID_0763:
   447062       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   447062       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   447062 Product= X52 Professional H.O.T.A.S.
   447062    Manufacturer= Logitech
   447062    Vendor=06A3, Product=0762 (Version 32.0)
   447062    GUIDs returned for product: VID_06A3&PID_0762:
   447062       GUID= {303FE860-AB41-11EA-8002-444553540000}
   447062       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   447125 -------------------------------------------------------------------
   447125 Device acquired for use:
   447125    Joystick ID = 1 (Registry okay)
   447125    1=Alpha Flight Controls
   447125    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   447125 Device acquired for use:
   447125    Joystick ID = 2 (Registry okay)
   447125    2=Flight Rudder Pedals
   447125    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   447125 Device acquired for use:
   447125    Joystick ID = 0 (Registry okay)
   447125    0=X52 Professional H.O.T.A.S.
   447125    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   447125 -------------------------------------------------------------------
   491047 ---------------------- Joystick Device Scan -----------------------
   491047 Product= Alpha Flight Controls
   491047    Manufacturer= Honeycomb Aeronautical
   491047    Serial Number= E6FD38061B233B00
   491047    Vendor=294B, Product=1900 (Version 0.32)
   491062    GUIDs returned for product: VID_294B&PID_1900:
   491062       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   491062       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   491062 Product= Saitek Pro Flight Rudder Pedals
   491062    Manufacturer= Saitek
   491062    Vendor=06A3, Product=0763 (Version 1.1)
   491062    GUIDs returned for product: VID_06A3&PID_0763:
   491062       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   491062       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   491062 Product= X52 Professional H.O.T.A.S.
   491062    Manufacturer= Logitech
   491062    Vendor=06A3, Product=0762 (Version 32.0)
   491062    GUIDs returned for product: VID_06A3&PID_0762:
   491062       GUID= {303FE860-AB41-11EA-8002-444553540000}
   491062       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   491125 -------------------------------------------------------------------
   491125 Device acquired for use:
   491125    Joystick ID = 1 (Registry okay)
   491125    1=Alpha Flight Controls
   491125    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   491125 Device acquired for use:
   491125    Joystick ID = 2 (Registry okay)
   491125    2=Flight Rudder Pedals
   491125    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   491125 Device acquired for use:
   491125    Joystick ID = 0 (Registry okay)
   491125    0=X52 Professional H.O.T.A.S.
   491125    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   491125 -------------------------------------------------------------------
   523875 ---------------------- Joystick Device Scan -----------------------
   523875 Product= Alpha Flight Controls
   523875    Manufacturer= Honeycomb Aeronautical
   523875    Serial Number= E6FD38061B233B00
   523875    Vendor=294B, Product=1900 (Version 0.32)
   523875    GUIDs returned for product: VID_294B&PID_1900:
   523875       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   523875       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   523875 Product= Saitek Pro Flight Rudder Pedals
   523875    Manufacturer= Saitek
   523875    Vendor=06A3, Product=0763 (Version 1.1)
   523875    GUIDs returned for product: VID_06A3&PID_0763:
   523875       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   523875       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   523875 Product= X52 Professional H.O.T.A.S.
   523875    Manufacturer= Logitech
   523875    Vendor=06A3, Product=0762 (Version 32.0)
   523875    GUIDs returned for product: VID_06A3&PID_0762:
   523875       GUID= {303FE860-AB41-11EA-8002-444553540000}
   523875       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   523937 -------------------------------------------------------------------
   523937 Device acquired for use:
   523937    Joystick ID = 1 (Registry okay)
   523937    1=Alpha Flight Controls
   523937    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   523937 Device acquired for use:
   523937    Joystick ID = 2 (Registry okay)
   523937    2=Flight Rudder Pedals
   523937    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   523937 Device acquired for use:
   523937    Joystick ID = 0 (Registry okay)
   523937    0=X52 Professional H.O.T.A.S.
   523937    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   523937 -------------------------------------------------------------------
   567859 ---------------------- Joystick Device Scan -----------------------
   567859 Product= Alpha Flight Controls
   567859    Manufacturer= Honeycomb Aeronautical
   567859    Serial Number= E6FD38061B233B00
   567859    Vendor=294B, Product=1900 (Version 0.32)
   567859    GUIDs returned for product: VID_294B&PID_1900:
   567859       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   567859       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   567859 Product= Saitek Pro Flight Rudder Pedals
   567859    Manufacturer= Saitek
   567859    Vendor=06A3, Product=0763 (Version 1.1)
   567859    GUIDs returned for product: VID_06A3&PID_0763:
   567859       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   567859       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   567859 Product= X52 Professional H.O.T.A.S.
   567859    Manufacturer= Logitech
   567859    Vendor=06A3, Product=0762 (Version 32.0)
   567859    GUIDs returned for product: VID_06A3&PID_0762:
   567859       GUID= {303FE860-AB41-11EA-8002-444553540000}
   567859       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   567922 -------------------------------------------------------------------
   567922 Device acquired for use:
   567922    Joystick ID = 1 (Registry okay)
   567922    1=Alpha Flight Controls
   567922    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   567922 Device acquired for use:
   567922    Joystick ID = 2 (Registry okay)
   567922    2=Flight Rudder Pedals
   567922    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   567922 Device acquired for use:
   567922    Joystick ID = 0 (Registry okay)
   567922    0=X52 Professional H.O.T.A.S.
   567922    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   567922 -------------------------------------------------------------------
   610094 ---------------------- Joystick Device Scan -----------------------
   610094 Product= Alpha Flight Controls
   610094    Manufacturer= Honeycomb Aeronautical
   610094    Serial Number= E6FD38061B233B00
   610094    Vendor=294B, Product=1900 (Version 0.32)
   610094    GUIDs returned for product: VID_294B&PID_1900:
   610094       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   610094       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   610094 Product= Saitek Pro Flight Rudder Pedals
   610094    Manufacturer= Saitek
   610094    Vendor=06A3, Product=0763 (Version 1.1)
   610094    GUIDs returned for product: VID_06A3&PID_0763:
   610094       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   610094       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   610094 Product= X52 Professional H.O.T.A.S.
   610094    Manufacturer= Logitech
   610094    Vendor=06A3, Product=0762 (Version 32.0)
   610094    GUIDs returned for product: VID_06A3&PID_0762:
   610094       GUID= {303FE860-AB41-11EA-8002-444553540000}
   610094       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   610156 -------------------------------------------------------------------
   610156 Device acquired for use:
   610156    Joystick ID = 1 (Registry okay)
   610156    1=Alpha Flight Controls
   610156    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   610156 Device acquired for use:
   610156    Joystick ID = 2 (Registry okay)
   610156    2=Flight Rudder Pedals
   610156    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   610156 Device acquired for use:
   610156    Joystick ID = 0 (Registry okay)
   610156    0=X52 Professional H.O.T.A.S.
   610156    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   610156 -------------------------------------------------------------------
   695156 ---------------------- Joystick Device Scan -----------------------
   695156 Product= Alpha Flight Controls
   695156    Manufacturer= Honeycomb Aeronautical
   695156    Serial Number= E6FD38061B233B00
   695156    Vendor=294B, Product=1900 (Version 0.32)
   695172    GUIDs returned for product: VID_294B&PID_1900:
   695172       GUID= {D9ADC750-AB41-11EA-8001-444553540000}
   695172       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
   695172 Product= Saitek Pro Flight Rudder Pedals
   695172    Manufacturer= Saitek
   695172    Vendor=06A3, Product=0763 (Version 1.1)
   695172    GUIDs returned for product: VID_06A3&PID_0763:
   695172       GUID= {0AB6AB60-D823-11EA-8004-444553540000}
   695172       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
   695172 Product= X52 Professional H.O.T.A.S.
   695172    Manufacturer= Logitech
   695172    Vendor=06A3, Product=0762 (Version 32.0)
   695172    GUIDs returned for product: VID_06A3&PID_0762:
   695172       GUID= {303FE860-AB41-11EA-8002-444553540000}
   695172       Details: Btns=39, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U255,V255,X1023,Y1023,Z255
   695234 -------------------------------------------------------------------
   695234 Device acquired for use:
   695234    Joystick ID = 1 (Registry okay)
   695234    1=Alpha Flight Controls
   695234    1.GUID={D9ADC750-AB41-11EA-8001-444553540000}
   695234 Device acquired for use:
   695234    Joystick ID = 2 (Registry okay)
   695234    2=Flight Rudder Pedals
   695234    2.GUID={0AB6AB60-D823-11EA-8004-444553540000}
   695234 Device acquired for use:
   695234    Joystick ID = 0 (Registry okay)
   695234    0=X52 Professional H.O.T.A.S.
   695234    0.GUID={303FE860-AB41-11EA-8002-444553540000}
   695234 -------------------------------------------------------------------
   783937 C:\Users\paulc\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
   800891 -------------------- Starting everything now ----------------------
  2867375 Sim stopped: average frame rate for last 2067 secs = 37.6 fps
  2867375    Max AI traffic was 148 aircraft
  2867375 -------------------------------------------------------------------
  2870469 flights\other\MainMenu.FLT
  2886531 MSFS no longer running - exiting
  2886531 === Hot key unregistered
  2886531 === Stop called ...
  2886531 === Closing external processes we started ...
  2887547 === About to kill any Lua plug-ins still running ...
  2887703 === Closing global Lua thread
  2888719 === About to kill my timers ...
  2888922 === Restoring window procs ...
  2888922 === Unloading libraries ...
  2888922 === stopping other threads ...
  2888922 === ... Button scanning ...
  2889031 === ... Axis scanning ...
  2889141 === Releasing joystick devices ...
  2889141 === Freeing macro memory
  2889141 === Removing any offset overrides
  2889141 === Clearing any displays left
  2889141 === Calling SimConnect_Close ...
  2889359 === SimConnect_Close done!
  2889359 === AI slots deleted!
  2889359 === Freeing button memory ...
  2889359 === Closing my Windows ...
  2889359 === Freeing FS libraries ...
  2890359 === Closing devices ...
  2890359 === Closing the Log ... Bye Bye! ...
  2890359 System time = 13/12/2020 01:33:10
  2890359 *** FSUIPC log file being closed
Minimum frame rate was 26.4 fps, Maximum was 181.7 fps
Average frame rate for running time of 2570 secs = 48.7 fps
Maximum AI traffic for session was 148 aircraft
Traffic deletions 0 aircraft
Memory managed: 2 Allocs, 1 Freed
********* FSUIPC Log file closed ***********

 

Like Katoema, I also use MSFS Addons Linker. Thanks

 

Edited by Paulcoy
John Dowson Grand Master

John Dowson

Posted
Posted
22 hours ago, katoema said:

for one side that this works, but now I wonder how this will affect MSAddon Linker and the presets, as I usually launch MSFS via that app, so not to install everything in the Community folder!

I know nothing about MSAddon Linker. if you use that to launch MSFS, then can it also launch FSUIPC7? Alternatively, if its ok to start this after MSFS, then you could use FSUIPC's run Programs facilities to start this. Or you could manually change the provided batch script to start MSFSAddon Linker instead of starting MSFS.

22 hours ago, katoema said:

When you start with MSFSAddon Linker, FSUIPC7 does not show that it is launched

It wouldn't if you are not starting it.

22 hours ago, katoema said:

BUT when you select Fly it shows up in the BRH corner in the "hide"box.

This I don't understand. So it is running? What launched it?

21 hours ago, Paulcoy said:

Like Katoema, I also use MSFS Addons Linker. Thanks

Your installation looks fine, and I don't think using MSFSAddons linker should affect the batch start-up script (and it is working for Katoema!).
Can you try starting by double-clicking the file MSFSwithFSUIPC7.bat (located in your installation folder). Using this there will be a command window created (maybe iconized) - please check that for errors.

Also, if you can right-click your standard MSFS start-up icon, select Properties and tell me what it says in the URL field please.

katoema Apprentice

katoema

Posted
Posted

@John DowsonHello John. OK I can clarify that you can select whatever in MSFSAddon Linker, but if you start MSFS directly from the MSFSAddon Linker app, FSUIPC7 does not launch. However, if you select whatever in the MSFSAddon Linker that you want to run, you must launch from the new MSFS/FSUIPC7 desktop icon and everything will run as you have selected i.e., MSFS, FSUIPC7 and what you have selected in MSFSAddon Linker.

It will be up to the author of MSFSAddon Linker to test how it can be used directly I will copy this response to him.

Thanks

Martin

Paulcoy Newbie

Paulcoy

Posted
Posted (edited)

Thanks for your help John. The .bat file just brings up FSUIPC after the splash screen, and the only way I start MSFS is from the Windows 10 start menu, and there is no properties to select. I have also discovered that the fast launch in Addons linker also doesnt work. Plus the task bar Msfs icon that I create keeps disappearing. So I think there is something amiss my end

Edited by Paulcoy
John Dowson Grand Master

John Dowson

Posted
Posted
13 minutes ago, katoema said:

OK I can clarify that you can select whatever in MSFSAddon Linker

Then why not start FSUIPC7 from the MSFSAddon Linker and forget the FSUIPC7 batch script?

15 minutes ago, katoema said:

but if you start MSFS directly from the MSFSAddon Linker app, FSUIPC7 does not launch.

Well, it won't launch on its own with MSFS unless the provided batch file is used. As I said, can't MSFSAddon linker start FSUIPC7?

16 minutes ago, katoema said:

However, if you select whatever in the MSFSAddon Linker that you want to run, you must launch from the new MSFS/FSUIPC7 desktop icon and everything will run as you have selected i.e., MSFS, FSUIPC7 and what you have selected in MSFSAddon Linker.

This is what is confusing me. Are you launching  MSFS/FSUIPC7 using the desktop icon manually or using MSFSAddon Linker? If the former, what is starting MSFSAddon linker?
If the latter, then that seems to solve any issues, no?
Seems like you have a choice of either
   1. use MSFSAddon linker to start MSFS and also start FSUIPC7
   2. use MSFSAddon linker to start both MSFS and FSUIPC7 by getting it to call the MSFS/FSUIPC7 batch script or desktop link
   3. change the FSUIPC7 batch script to start MSFSAddon Linker (which would then start MSFS) instead of MSFS directly

The choice is probably restricted by what MSFSAddon linker can do.

I'll take a look at the MSFSAddon linker at some point, but I won't have time for this for a while.

John

John Dowson Grand Master

John Dowson

Posted
Posted

@Paulcoy That does sound strange... Did you try the batch file directly and checking the contents of the command window for the error? Alternatively, open a command prompt and enter the following and let me know what error you get (or if MSFS starts):
    cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch
You can also try
    start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch

John

katoema Apprentice

katoema

Posted
Posted

@John Dowson I have sent a PM to the author, as he set up my link, because I do not use the full intro for MSFS, as it misses this out and reduces the time it takes to launch MSFS.

 

All MSFSAddon Linker undertakes is to create symbolic links from the Community folder to a folder called "MSFS Addons" and this is where all the "Community" items are held. You can then create presets which, in essence, will only launch what is in that preset.

At present I select the preset, but use the MSFS/FSUIPC icon to undertake the launch and can only launch what the preset is tricking what is "in" the Community folder. You are correct that MSFS/FSUIPC7 should be able to be launched by MSFSAddon Linker (this is undertaken from being set up from the options box in the app). The author has to look at MSFS/FSUIPC7/FSJumpstarter to provide me with the correct solution.

Martin

Paulcoy Newbie

Paulcoy

Posted
Posted

Hi John. Just for clarification, I dont use Addon Linker to start MSFS. Only the start menu icon. I put both command prompts as Administrator in and after clicking enter it went straight back to  C \WINDOWS\ system32>

John Dowson Grand Master

John Dowson

Posted
Posted
3 minutes ago, Paulcoy said:

Just for clarification, I dont use Addon Linker to start MSFS.

Ok. But this seems to contradict your previous statement:

On 12/13/2020 at 1:40 PM, Paulcoy said:

Like Katoema, I also use MSFS Addons Linker.

Not to worry, as I don't think this relate to your problem.

4 minutes ago, Paulcoy said:

I put both command prompts as Administrator in and after clicking enter it went straight back to  C \WINDOWS\ system32>

Well, you shouldn't have done this as an Adminstrator, but it shouldn't matter. But the folder you are starting things from (C \WINDOWS\ system32>) might. Maybe try it again from a non-admin account, and from a non protected folder (if you start a command prompt as a non-admin, it should default to your home folder).

2 hours ago, Paulcoy said:

I have also discovered that the fast launch in Addons linker also doesnt work. Plus the task bar Msfs icon that I create keeps disappearing. So I think there is something amiss my end

Yes, it does seem that something is amiss in your MSFS installation. If its the -FastLaunch option that is confusing things, you could try removing that option from the line in the MSFSwithFSUIPC7.bat file to see if that makes a difference.

Really, you need to determine what command to use to start MSFS. The next time you install, I suggest that you opt to create the desktop start icon, which you can then use to determine the command used (from the URL field in the properties). I have no idea why the standard command that works for almost everyone else is not working for you.

Have you tried running the desktop link as administrator (right-click and select 'Run as administrator')? Maybe also worth trying, but if the start commands don't work in a command window, I doubt they will work from using the link.

John

Paulcoy Newbie

Paulcoy

Posted
Posted
Quote

If its the -FastLaunch option that is confusing things, you could try removing that option from the line in the MSFSwithFSUIPC7.bat file to see if that makes a difference.

I can't open the .bat as a Commant Prompt to see any details, it just instantly runs your splash screen. Yes I do use Addons Linker but only as a replacement for the Community folder, and not to start MSFS. I know this has been asked before, but can you tell me personaliy the best way to completely uninstall FSUIPC7 including any registry items. Then I will re install to default locations

John Dowson Grand Master

John Dowson

Posted
Posted
2 minutes ago, Paulcoy said:

can't open the .bat as a Commant Prompt to see any details, it just instantly runs your splash screen.

Right-click on the MSFSwithFSUIPC7.bat file, located in your FSUIPC7 installation folder (i.e. not the link on your desktop) in windows explorer, an select 'Edit' or 'Edit with Notepad++' (or whatever your preferred editor is).

5 minutes ago, Paulcoy said:

but can you tell me personaliy the best way to completely uninstall FSUIPC7 including any registry items.

Run the uninstaller that is generated in the installation process. You can also find this in your FSUIPC7 installation folder. You can also uninstall using the windows settings apps uninstall page, which will run the uninstaller for you.

John

Paulcoy Newbie

Paulcoy

Posted
Posted

Ok Many Thanks John for all your help. Im going to uninstall restart computer and re install with your default settings, because at the moment it is on my E drive. I have also attached my .bat file for your perusal. Once again Many Thanks Paul

MSFSwithFSUIPC7.txt

John Dowson Grand Master

John Dowson

Posted
Posted

Ok. But I didn't need to see your bat file - I know what is in it! I was just suggesting that you could open it and play around with the command that starts MSFS (including removing the FastLaunch option) to see if you can get it to work. The command is at line 7:
    cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch
Its the same for every MS Store user. This command uses your user AppsFolder  settings, which may be the issue. I don't think uninstalling and re-installing FSUIPC7 is going to help.

John

katoema Apprentice

katoema

Posted
Posted

@John Dowson I placed the bat file D:\FSUIPC7\MSFSwithFSUIPC7.bat into the Custom FS start EXE: address box of the MSFSAddon Linker app and it started and launched MSFS and FSUIPC7 and the preset I selected. And, to boot, the MSFS Jump Starter to reduce loading time.

One happy simmer here now and thank you for your direction.

Martin

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • 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.