invernyx / smartcars-3-bugs

The bug tracker for the smartCARS 3 application
3 stars 0 forks source link

SmartCars 3 will not Connect to MSFS #339

Closed SnowHawk6 closed 9 months ago

SnowHawk6 commented 9 months ago

Describe the bug

When loaded into MSFS and trying to have SmartCars 3 start tracking the flight, the software keeps attempting to connect until eventually it times me ou. I have ensured administrator is not being ran on MSFS or FSUIPC and even uninstalled and reinstalled FSUIPC. I have attached the logs below from SmartCars 3 along with the screenshot of the screen of SmartCars 3.

How do you reproduce this bug?

  1. Opened SmartCars 3
  2. Logged into VA
  3. Went to flight tracking and noticed it would not connect

Expected behavior

SmartCars 3 should be able to connect and start tracking flights.

Screenshots

image

combined-2023-09-19.log error-2023-09-19.log

Operating system

Windows 11

Community airline

American Virtual

smartCARS Version

3.0.0

Plugins installed

Chat, Flight Center, Flight Tracking, Logbook, and Map

Additional context

No response

GenericNerd commented 9 months ago

It seems there is an error internally that's happening. Do you know whether you're running any application on 7172?

SnowHawk6 commented 9 months ago

The only applications that are running concurrent with SmartCars is MSFS, Navigraph, SimToolkit Pro, and Pilot Core IVAO.

Thien42 commented 9 months ago

Can you double check if the tracking provider is set to FSUIPC in the smartCARS settings?

SnowHawk6 commented 9 months ago

Yes tracking provider is set to FSUIPC in the SmartCars settings

GenericNerd commented 9 months ago

Can you try the following commands? You will need an administrative command prompt. To get one, type "Command Prompt" into the search, right click and click "Run as an administrator":

net stop winnat net start winnat

Please let me know if this fixes it.

GenericNerd commented 9 months ago

Hi @SnowHawk6, has this worked for you? If we don't hear back soon, we will close this issue out as stale

SnowHawk6 commented 9 months ago

@GenericNerd Hello, sorry for the late reply. The command did not work for this.

GenericNerd commented 9 months ago

Can you run the following command?:

netstat -aon

And let me know if any of the following appear under the TCP port section: 0.0.0.0:7172 127.0.0.1:7172 ::1:7172 [::]:7172 [::]:1:7172

GenericNerd commented 9 months ago

Closed as stale. If this is still happening, please resubmit this bug.