Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi, Pete,

I'm using registered version of FSUIPC7 and Self Loading Cargo.

The problem is (as I think) Self Loading Cargo is not recognizing some inputs as Battery, External Power, Transponder settings, and some more little things (I'm using SLC on remote PC).

Is there any way to SLC recognize those functions through FSUIPC? The developper (Steve) says there some problems because WASM modules (I installed them when installing FSUIPC7).

Best regards and thanks,

Vasco

Posted
16 hours ago, Vasco Oliveira said:

Is there any way to SLC recognize those functions through FSUIPC?

I have no idea as I don't have SLC and know nothing about this....

16 hours ago, Vasco Oliveira said:

The developper (Steve) says there some problems because WASM modules (I installed them when installing FSUIPC7).

What does this mean?

There is a known issue with the WASM in that it can crash when using complex aircraft and complex add-on scenery. There is a FAQ entry on this with a fix - see 

If that is not your issue, please provide a more detailed explanation of what the problem is, and please show me/attach your FSUIPC7.log and FSUIPC7.ini files, attached when FSUIPC7 is NOT running, and also your FSUIPC_WASM.log file (see the Advanced User guide if you do not know where this is located) attached when MSFS is NOT running and after a session where you experienced your issue.

John

Posted
19 hours ago, Vasco Oliveira said:

(I'm using SLC on remote PC)

I think this maybe the issue...Are you also running FSUIPC7 or WideClient on the remote machine as well, or just SLC?
If running FSUIPC7, have you configured this for remote access on both the [General] and [WAPI] sections (as explained in the appendix on setting-up FSUIPC7 for remote access)?

Posted (edited)
49 minutes ago, John Dowson said:

I think this maybe the issue...Are you also running FSUIPC7 or WideClient on the remote machine as well, or just SLC?
If running FSUIPC7, have you configured this for remote access on both the [General] and [WAPI] sections (as explained in the appendix on setting-up FSUIPC7 for remote access)?

Hi,

I run FSUIPC7 (not the WideClient) on the remote machine where SLC runs too.

I think I did everything well, even the configuration of FSUIPC7.

I'm sending you my FSUIPC7.ini, LOG files and simconnect.cfg.

Thanks. 🙂

FSUIPC7.ini FSUIPC7.log InstallFSUIPC7.log SimConnect.cfg

Edited by Vasco Oliveira
Posted

I have discussed this with Steve, the SLC developer, and it looks like there are currently restrictions when using SLC on a remote/client PC:

Quote

The Settings screen in SLC specifically states that the more advanced functionality won't work:

THESE SETTINFS WILL NOT WORK IF USING WIDEFS ACROSS A NETWORK AND MAY CAUSE UNPREDICTABLE OR INCONSISTANT RESULTS

So that appears to be the issue - when using a client PC "normal" FSUIPC functionality will work, but the functionality which requires LVARs to be read will not.

SLC will need an update to handle lvars on a remote machine.

31 minutes ago, Vasco Oliveira said:

I run FSUIPC7 (not the WideClient) on the remote machine where SLC runs too.

Ok. Looking at your log file, there are a few issues I need to fix when running FSUIPC7 on a client machine:
   - I need to update the PMDG 777 thread to be able to use the remote connection
   - WASM / WAPI facilities are disabled as no WASM installed - the WASM is on the server machine and these facilities should be available
     (this was previously working, but I think a recent change in initialization order has broken this)

I will look into these issues, but I'm afraid that this will not fix your issues with SLC.

John 

Posted
25 minutes ago, John Dowson said:

Ok. Looking at your log file, there are a few issues I need to fix when running FSUIPC7 on a client machine:
   - I need to update the PMDG threads to be able to use the remote connection
   - WASM / WAPI facilities are disabled as no WASM installed - the WASM is on the server machine and these facilities should be available
     (this was previously working, but I think a recent change in initialization order has broken this)

I have corrected for this in the attached version, 7.4.17b,  if you could try it.

Please show mr your FSUIPC7.log file from the client PC after using - and please exit FSUIPC7 before attaching files.

John

FSUIPC7.exe

 

Posted
11 minutes ago, John Dowson said:

I have corrected for this in the attached version, 7.4.17b,  if you could try it.

Please show mr your FSUIPC7.log file from the client PC after using - and please exit FSUIPC7 before attaching files.

John

FSUIPC7.exe 664 kB · 0 downloads

 

Ok, John. Thank you very much.

I'll try it after this flight I'm doing from LFPO to LGAV.

Regards,

Vasco

Posted

Hi, John,

I was making a flight from EGLL to LPPT with the Fenix A321.

Improves with FSUIPC7 version 7.4.17b:

* Battery and Ground power detected;

* Transponder sets recognized;

During t/o SLC crashed...

I think I'll try using SLC on MSFS machine. I'm tired of this.

Thanks anyway

Posted
11 hours ago, Vasco Oliveira said:

Is it needed to install lvarmodules with this FSUIPC7 version?

You use the exe I provided to replace the current one in your FSUIPC7 installation folder - iy will use the same installed WASM as the previous release (i.e. no WASM update).

8 hours ago, Vasco Oliveira said:

Improves with FSUIPC7 version 7.4.17b:

* Battery and Ground power detected;

* Transponder sets recognized;

Ok, good to know, thanks - probably due to the PMDG 777 thread now running. Could you please show me your FSUIPC7.log file from this version, on the client machine, so that I can check a few things.

8 hours ago, Vasco Oliveira said:

During t/o SLC crashed...

I think I'll try using SLC on MSFS machine. I'm tired of this.

8 hours ago, Vasco Oliveira said:

But SLC was crashing anyway since the last update (1.6.4.5).

You should raise a support ticket for this. Also ask if lvar access when running across a network can be added as this should be possible and relatively straightforward, as the .Net dll that SLC uses for this already allows for this.

Regards,

John

Posted

I think Steve is a bit angry with me by posting these issues on remote. But, since I believe we can do it and certainly other users would like to run SLC on remote, I'll insist on this improvement on both softwares.

When I arrive at home, I'll send you the files.

By the way, I installed the latest lvar modules on that flight.

Regards,

Vasco 

 

Posted
8 minutes ago, Vasco Oliveira said:

Here it is, John.

Looks likes you attached that log when FSUIPC7 was running, and it ends after less than 0.5 seconds and doesn't really show much...very strange - did FSUIPC7 crash?

Posted

No. Just SLC.

But now I'm flying from LPPT to LPMA with the Fenix A320 and SLC on remote again.

For now, everything is going ok. I'm almost at the middle of the flight. Then, I'll tell you something and I'll send you both the FSUIPC7 and SLC logs. 

Thanks, John.

Posted
4 hours ago, Vasco Oliveira said:

I think Steve is a bit angry with me by posting these issues on remote. But, since I believe we can do it and certainly other users would like to run SLC on remote, I'll insist on this improvement on both softwares.

Regards,

Vasco 

Where do you get the idea that I'm somehow "angry"? That's not the case at all 🙂 

The only thing I will say is you will probably have more luck talking to me directly about issues concerning my software - if you had put forward the information about you running SLC on a remote machine to the simulator during our support communications, I could have told you immediately that SLC works remotely for basic functionality but does not support LVARs via WideClient (and it says as such on the Settings screen). This will change in the near future, but you will have no luck at the moment and so should turn off the advanced functionality that requires LVARs in SLC Settings on the Compatibility > Aircraft tab.

P.S. The Settings.xml file you posted is a template and is not the Settings file that is active within the application.

 

Posted
32 minutes ago, FPVSteve said:

Where do you get the idea that I'm somehow "angry"? That's not the case at all 🙂 

The only thing I will say is you will probably have more luck talking to me directly about issues concerning my software - if you had put forward the information about you running SLC on a remote machine to the simulator during our support communications, I could have told you immediately that SLC works remotely for basic functionality but does not support LVARs via WideClient (and it says as such on the Settings screen). This will change in the near future, but you will have no luck at the moment and so should turn off the advanced functionality that requires LVARs in SLC Settings on the Compatibility > Aircraft tab.

P.S. The Settings.xml file you posted is a template and is not the Settings file that is active within the application.

 

Hi, Steve.
I do not use Wideclient some time ago. Calm down.

I flew from LPPT to LPMA and things were going ok, except the transponder. The flight was completed as you can see on Arrivals on Discord.

Now, I'm flying from LPMA to LPPD and SLC crashed  after takeoff.

I'll wait for an update. SLC is awesome, I love it, but I don't like to use it on MSFS machine. I tried today and the main button doesn't open the other wheels. That's one reason to use it on remote.

When I said "angry" it was on good way. Because I'm always asking you things and I don't like to get much time of people, since you have more things to do. 😉

Regards. 🙂

  • Thanks 1
Posted
14 hours ago, Vasco Oliveira said:

Here re the files for analisys, John.

Your looks fine, although looks like you were using the Fenix A320 rather than the PMDG 777 so I couldn;t check if that thread was started/terminated correctly.

John

Posted
47 minutes ago, Vasco Oliveira said:

When I'll fly the 777, I'll send you the files.

Ok, thanks, Just want to check that the PMDG 777 thread is started/stopped correctly when needed (on the client PC/installation).

Posted

Your remote log looks good, thanks.
Your MSFS machine log does show some re-connection attempts at start-up. Looks like your DetectToConnectDelayAuto ini parameter is set too low: the current value is 115, you should change this to around 170.

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
×
×
  • 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.