search

invernyx / smartcars-3-bugs

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

[BUG] - Linux Client Denies Connection #329

Closed Rastuasi closed 1 year ago

Rastuasi commented 1 year ago

Describe the bug

Downloaded the latest plugin and installed as of tonight. Loaded a bid from Walker Air and get two options as the return. In 20 loads, 18 were the screenshot attached, saying cannot connect, the 2 others were "invalid scenario" and it claiming no flight plan, but one is clearly there.

How do you reproduce this bug?

  1. Install latest linux client on Manjaro
  2. Load sim and at airport.
  3. Load smartcars3, go to bid screen, find the single bid, activate bid
  4. Wait for failure.

Expected behavior

It would connect and track flight

Screenshots

image combined-2023-08-30_bug.log image image

Operating system

Manjaro Arch Linux

Community airline

Walker Air

smartCARS Version

0.14.0

Plugins installed

chat, flight center, flight tracking, logg

Additional context

No response

Rastuasi commented 1 year ago

Also forgot to mention, I did already try clearing out the .config/smartCARS 3 files as well when updating, so it should not be an old config file from the previous installations.

Rastuasi commented 1 year ago

error-2023-08-30.log Just for addition, this file was also there, but the errors are probably from me trying my pilot ID instead of email to log in.

GenericNerd commented 1 year ago

This is not a bug. You need to change your settings to use the X-Plane client, rather than the FSUIPC client which is currently selected.

Rastuasi commented 1 year ago

This is not a bug. You need to change your settings to use the X-Plane client, rather than the FSUIPC client which is currently selected.

Reread it and know your software. The linux client defaults to only xplane. I am not selecting the FSUIPC client, that's just what your error says. Please reopen

Rastuasi commented 1 year ago

Already provided a screenshot, but just to prove it again: image As you can see, NO FSUIPC client option and no option for Xplane, because it DEFAULTS to XPlane, bug is valid, reopen it please and investigate why the last version connected through UDP but the new one fails to connect.

GenericNerd commented 1 year ago

You're right, I forgot that we have platform-specific options and the tracker is one of them. I've re-opened the issue.

Can you try setting port 49010 in smartCARS instead of the legacy port 49000?

Rastuasi commented 1 year ago

No worries, I did try changing the ports in mix of those 20 attempts and restarts, but didn't save off a log, let me get that real quick.

Rastuasi commented 1 year ago

@GenericNerd no luck. I opened smartcars, set the setting, closed it fully, loaded sim up, had wheels on ground, bid placed, plane loaded, started smartcars, confirmed setting held the new port and attempted to connect. Same error.

One thing I did notice, I don't have the option for setting x-plane in the UI, but the config.json has a setting line there and it does say fsupic.

So for testing, I tried switching that myself to xplane and tried x-plane. Still no connection on either port, but it did change the error to say "cannot connect to simulator" and no reference to fsuipc. So I am guessing that Linux truly does default and ignores that config, but the error message tricks you to think it's looking for fsuipc.

combined-2023-08-31_49010_attempt.log image

Rastuasi commented 1 year ago

okay was able to find that it should be "xplane" if this were a windows client, where I could set it, via looking at the:

SmartCars/resources/app/dist/plugins/com.tfdidesign.flight-tracking/plugin.json

Setting that manually then in my .config/smartCARS 3/config.json presents this as the error:

image

So removes the reference of FSUIPC, but still no connection on either port.

Thien42 commented 1 year ago

The FSUIPC error message is only a visual bug which will be fixed, as we use the X-Plane tracker on any non-Windows environment regardless of the tracking_provider value.

With that being said, I was not able to reproduce the aforementioned issue. Could it be that you have a firewall that is blocking incoming traffic on either the X-Plane port (49000) or the port smartCARS 3 uses (7172)?

Rastuasi commented 1 year ago

I have other apps that use UDP of XP, they don't have issues, so I know 49000 works. Did smartcars3 change to 7172 from something else? Up until this latest version I didn't have issues, so long as I loaded sim first. I'd get this error before if I loaded SC3 before the sim, but it's consistent now, regardless of order

Thien42 commented 1 year ago

Yes, before being 7172, it was a random port assigned by the OS but that would cause other issues in the long run.

I will add an option to manually select a port, hopefully that will fix the issue for you

Rastuasi commented 1 year ago

Great! Well outside my router having a firewall externally, the internal sim communication should be firewall-less, but if the sim connection requires both ends, could be an issue. I'll do some digging on this new port you mentioned and then report back, at least as a way to verify or whatnot on if this is the issue or not

Rastuasi commented 1 year ago

Saw that there was a new client, loaded it in, did port forwarding on 7172 on router, tried setting XP to do its own UPnP, tried 49000 and 49010, all with the same results. combined-2023-09-01_latest_PortForwarding.log error-2023-09-01.log

Thien42 commented 1 year ago

I'm not sure what you mean, there is no need for either port forwarding or UPnP to track a flight with smartCARS 3. The port to be used for X-Plane is 49000

Rastuasi commented 1 year ago

Not meaning much than forcing the ports that worked prior to be listed on the network, that's all, but even that didn't work. It really shouldn't be a marker though on my network, since the previous version worked. So essentially, I am just trying things and reporting what I am trying so that it may point your dev team into what might be my issue, either way.

Rastuasi commented 1 year ago

Additional follow up, I reverted all my testing changes, back to what router was before changes suggested in this ticket on ports and had a flight tracked. Not sure what or why, but it picked up the 7172 just fine, worked like it did before 0.14.0. Not sure why the past several days was a no go though. Going to do a few more test flights and report back.

Does the UDP to XP go out and away from the home network to communicate with SC3? I would not think it would, same network, same machine, it should just connect, wondering if something external was the issue. Just weird how the night before the update, I did a flight, updated and since then, had issues.

Thien42 commented 1 year ago

Does the UDP to XP go out and away from the home network to communicate with SC3?

Glad you could have it sorted!