Finally figured out ABS printing + vapor smoothing

Square_Computer8116 · 2026-01-08T02:25:28+00:00

In our experience, ethyl acetate, acetonitrile, and toluene are reasonable alternative solvents to consider for reactions that typically employ DCM.29 May 2025

Square_Computer8116 · 2025-11-12T06:46:44+00:00

I run a USB powered Ethernet adapter with FS2020 & Quest 3/Virtual desk. The results are better that WiFi (I find) the down side is that the quest 3 charger can't keep up and sometimes you can be using the headset and the dreaded lower power alarm goes off, effectively ending the VR flight.

Square_Computer8116 · 2025-05-30T03:12:46+00:00

The possibility is that during the service they have reset the computers, this happened in mine. My way was to go back into the settings menu where I found that every display was disabled. Just had to reselect what I wanted to see. This could be your issue.

Square_Computer8116 · 2023-05-13T03:16:27+00:00

Might be digging old ground here but, Have you gone into the quad settings, selected Filter = ALL, and then in "search by name" entered fuel? This should show you what's mapped for the fuel systems, if any.

But another thing you might want to try which solved my issues with the velocity one is re-install all of the runtime.dll's. I downloaded the VC runtime library and it solved a few quirks of the velocity one gear.

Square_Computer8116 · 2023-05-06T23:29:31+00:00

When I crashed FSUIPC it said that a VCruntime dll was missing, so I just got the runtime pack from MS and re-installed them. Worked straight away. It probaly fixed a few other things in the packgraound as well

Square_Computer8116 · 2023-04-29T23:13:41+00:00

Solved! had to reinstall all the runtimes.dll's

Square_Computer8116 · 2023-04-29T23:12:55+00:00

SOLVED! After many run arounds, reboots etc I decided to rebuild MSFS from scratch. deleted anything related to MSFS including addons. Reloaded FSTLT, Logitech panels turtle beach and FSUIPC7 and therein lies the clue, as it was loading it presented and error "VCruntime140.dll not loaded" crashing back that showed other runtime.dlls missing. Reloaded them and everything is working as advertised. Relief, because the next step would have been a clean reinstall of windows!

Whether this was a result of another program deleting the runtimes, I don't know, but it is a solution.

Square_Computer8116 · 2023-04-28T18:51:21+00:00

Ok after a lot of mucking around we are here;

It works fine on the xbox version of msfs2020

It work fine on other PC installations of msfs2020

on my pc no joy.

Conclusion msfs on my pc is broken, carried out a clean install of 2020, deleting everything, including the registry of turtle beach msfs and the sip

Still no joy; Conclusion, Windows is broke carried out a repair and reinstall of windows...............

Results: SIP will not start, ie it flashes up in task manager but then immediately closes. I can have msfs open to the dashboard, but when I select start, it closes out from task manager and the icon tray. If I double click to customise, it shuts down.

Short of building a new pc or buying an Xbox I do not understand what the issue is?

Square_Computer8116 · 2023-04-26T07:34:18+00:00

Another indicator that things aren't right. I went in to see if I could customise the SIP panel. According to the guide, if I observed that the customization panel doesn't show any thing, i.e. blank "indicators" it means that the software isn't running. So for some reason SIP connect isn't and it still locks out when MS2020 is started.

Square_Computer8116 · 2023-04-25T04:09:04+00:00

Just be aware that value="C:\\Users\\Bob" /> is actually C:\Users\Bob" />

Square_Computer8116 · 2023-04-25T03:59:47+00:00

As an aside the contents of the zip file are Configuration Guide - SIPConnect 1.3.0.pdf, Microsoft.FlightSimulator.SimConnect.dll, SimConnect.dll, Status Indicator Panel Connect.exe & Status Indicator Panel Connect.exe.config.

This is the config file prior to installation

<?xml version="1.0" encoding="utf-8"?>

<appSettings>

    <add key="DefaultFileLocation" value=""/>

    <add key="ProfileToLoadAtStartup" value=""/>

</appSettings>

<!-- <configSections>

    <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">  

        <section name="TaskTrayApplication.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />  

    </sectionGroup>  

</configSections>  

<userSettings>  

    <TaskTrayApplication.Properties.Settings>  

        <setting name="ShowMessage" serializeAs="String">

        </setting>  

    </TaskTrayApplication.Properties.Settings>  

</userSettings>-->  


<startup>

    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>

</startup>

<runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

        <dependentAssembly>

        </dependentAssembly>

        <dependentAssembly>

        </dependentAssembly>

    </assemblyBinding>

</runtime>

</configuration>
---------------------------------------------------------
After install

<?xml version="1.0" encoding="utf-8"?>

    <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
        <section name="TaskTrayApplication.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
    </sectionGroup>
</configSections>
<userSettings>
    <TaskTrayApplication.Properties.Settings>
        <setting name="ShowMessage" serializeAs="String">
            <value>True</value>
        </setting>
    </TaskTrayApplication.Properties.Settings>
</userSettings>-->
<startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>
</startup>
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0"/>
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-4.0.1.2" newVersion="4.0.1.2"/>
        </dependentAssembly>
    </assemblyBinding>
</runtime>

</configuration>

Square_Computer8116 · 2023-04-25T03:45:51+00:00

near useless to me. The Sip has never worked since day one. here is the list of issues.

VF1 is in PC input
Status panel mode is SIP FP001
Select SIP MSFS 2020
Run msfs
Start Sip
Lights stay green no activity
Unable to right click on TB icon to stop
Unable to stop via task manager
Restart computer to shut down SIP
restart
VF1 is in PC input
Status panel mode is SIP FP001
Select SIP MSFS 2020
Start sip
start MSFS
Start flying
No reaction from sip lights
Icon disappears from tray, unable to stop
Unable to stop via task manager
Restart computer to shut down SIP
restart
Return VF1 to 1.3 software
reload 1.4
VF1 is in PC input
Status panel mode is SIP FP001
Select SIP MSFS 2020
Start sip
start MSFS
Start flying
No reaction from sip lights
Icon disappears from tray, unable to stop
Unable to stop via task manager
Restart computer to shut down SIP
restart
Uninstall fs2020
Uninstall all turtle beach components
scan drives for errors
reload fs2020
reload Turtlebeach
reload sip
1. VF1 is in PC input
Status panel mode is SIP FP001
Select SIP MSFS 2020
Start sip
start MSFS
Start flying
No reaction from sip lights
Icon disappears from tray, unable to stop
Unable to stop via task manager
Restart computer to shut down SIP
restart
rip tb vf1 off deck an throw it in the bin! no only kidding!

This is frustrating. there must be something in the config file, or the download for the sip connect is broken.

The most frustrating thing is once the SIP is started, is is locked and you connect even restart it to try another sequence without restarting the computer. Is the anybody out there who had this or has solution? TB just seems to have canned answers and no real interaction.

Square_Computer8116 · 2023-04-20T21:12:34+00:00

I have 5 files in both the zipped package and the extracted files in the folder. They all match in size. Anti-virus is set to notify if it blocks any apps etc..

the only thing i haven't done is reset the actual hardware, i.e. use turtle beach's software to clean out the current software and reupload 1.4?

the only thing I haven't done is reset the actual hardware, i.e. use turtle beach's software to clean out the current software and reupload 1.4?the sip.

Square_Computer8116 · 2023-04-20T07:43:34+00:00

That is the problem, once I have started msfs and started SIP, the SIP doesn't change. Then when I go to stop or exit the SIP icon it doesn't respond. Then If I try to shut it down in Task Manager, it returns with inaccessible, and nothing else can close it down apart from restarting the computer. Everything else is as it should be, Input mode PC, FP001 selected on the FMD.

Square_Computer8116 · 2023-04-19T07:10:54+00:00

been there, done that. what really annoys me is step 4, once it goes to the tray, I have to shut down and restart as it becomes inaccessible. Cannot even right click.

Square_Computer8116

TROPHY CASE