search

invernyx / smartcars-3-bugs

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

[BUG] - Smartcars3 will not detect the simulator #331

Closed natedog60 closed 10 months ago

natedog60 commented 10 months ago

Describe the bug

As requested from the TDFi site, I am posting this here. Hi, I fly with MSFS2020/FSUIPC7 under walker air. Trying out smart cars 3 and it will not connect as it doesn't detect the sim. I am at the correct airport with neither application running as administrator as the warning error instructed and it still won't connect.

How do you reproduce this bug?

  1. Open flight simulator
  2. Have the flight selected with your VA so it populates to SC3
  3. Attempt to hit "fly"
  4. SC3 gives you an error when it tries to connect

Expected behavior

It should connect to the plane and simulator and allow you to fly the flight.

Screenshots

error-2023-08-31.log error-2023-09-01.log combined-2023-08-31.log combined-2023-09-01.log Capture (1) Capture1 (1)

Operating system

Windows 10

Community airline

Walker Air Transport

smartCARS Version

The latest one as of 9/1/2023

Plugins installed

chat, flight center, flight tracking, logbook, map

Additional context

The screenshots I posted was one showing the error and one showing proof on my taskbar that FSUIPC7 is running

Specs

Flight Simulator and Version MSFS2020 latest version as of 9/1/2023

OS Windows 10

CPU AMD ryzen 3700X

Graphics Card NVIDIA GTX 1050ti

RAM 64GB DDR4

Thien42 commented 10 months ago

Do you have UAC (User Access Control) disabled in Windows?

natedog60 commented 10 months ago

No I do not. The thing that notifies me if a program might be harmful? That is on as it's important.

bgiorgio0506 commented 10 months ago

@natedog60 the log shows clearly that you are running your simulator as administrator please try to run the sim without admin permission.

And let me know if it works ;)

GenericNerd commented 10 months ago

As we haven't received a response on whether Giorgio's suggestions fixed the issue, we are going to be closing this issue as stale for now. If you still encounter this, please open a new issue and reference this one in the new issue.