[Purchase Page]

Hi John, I have tried update my billing and delivery address. When pressing continue I repeatedly get this:

{"bag_body":"\t

• \n\t\t\t\t\t
• \n\t\t\t\t<\/a>\n\t\t\t\tFSUIPC7 FOR MSFS<\/a><\/span>\n\t\t\t\tJohn Dowson<\/span>\n\t\t\t\tEUR 24.99<\/span>\n\t\t\t<\/li>\n\t\t\t<\/ul>\n

  \n\tTotal: 1 item EUR\u00a024.99
  \n\tCredit: EUR\u00a00.00<\/strong>\n<\/p>","items_total":1,"value_total":"1 items <\/span>EUR 24.99<\/span>","products_name":" x ","dialog_shoppingcart_message":"Product added to shopping cart"}

Can you assist please?

Thanks

Martin

[Reverse Thrusters not working]

Thanks John, I'll leave everything as it is now until the new release.

Just tried the B747 and the A320neo and the reverse thrusters are working.

Martin

[Reverse Thrusters not working]

The 4 auto starters checking now on B747-8, do operate but they cutout when N1 reaches 2.6!

The reverse thrusters were assigned, but just to be sure if I now use your installer which you attached, I will now copy over my ini to use.

Thanks

Martin

 

[Reverse Thrusters not working]

Reverse thruster is activated by lifting the throttle levers over the bar to #29 and #30 on the Hotas Warthog.

It is a Premium Deluxe Boxed version, but then through MS Store.

Engine autostart, I've not tried lately, but will look when I start MSFS again.

Thanks

Martin

FSUIPC7.log

[Reverse Thrusters not working]

Since this weekend the reverse thruster have stopped working. FSUIPC7.ini and FSUIPC7.log files attached.

Thanks

Martin

 

FSUIPC7.ini FSUIPC7.log

[After Latest patch FSUIPC not working]

Yes it's registered, will start a new topic.

Thanks

Martin

[After Latest patch FSUIPC not working]

Hi John, I only use FSUIPC7 for reverse thrust on the planes that you can use reverse thrust. This has been working up until this past weekend.

Yes I have updated FSUIPC7 today and everything is there as per your discussions elsewhere. And to be sure, from your earlier communication in August to move the FSUIPC4.ini over and call it FSUIPC7, I verified that the details were there as I copied version 7 over for clarification.

I am not sure why reverse thrust is now not working. Is it something to do with the latest MSFS update of the fix this weekend that has corrupted something or FSUIPC7

Thanks

Martin

[Chance to reverse throttle axis by button?]

Then, I'm at a loss as to how the reverse thrust is working with FSUIPC. In MSFS I can see the axis travelling  for each slider, but then  it must be on FSUIPC for the buttons.

Martin

 

Martin

[Chance to reverse throttle axis by button?]

Thought it may have helped as to how I have my reverse thrusters operating!

It was at the back of August when I sent you those files.

Martin

 

[Chance to reverse throttle axis by button?]

Sorry John, it's just that you mentioned that I had not made profiles from what you saw.

Martin

FSUIPC7.ini FSUIPC7.log

[Chance to reverse throttle axis by button?]

I have the Thrustmaster Hotas Warthog and simply used FSUIPC 4 or 7 to link 1, 2, 3 and 4 engines for reverse. Remember with this throttle when you are in idle you have to lift the throttle up and back over the bar and reverse kicks in. Just push it forward and you are back in front of the bar, then a slight nudge forward to continue with normal throttle usage. I sent John, by DM, my data/log etc and I have not changed it since. It is buttons 29 and 30 and ZR and Z Axis, with 16384 as idle.

May be this help?

Martin

 

[FSUIPC7 and 4 on same PC issue]

John, Alex is working on MSFS, yes it connects through LittleNavConnect,with my FSX scenery, but we're waiting for the facility to have full connection to the MSFS scenery, etc.

Thanks for clarifying about client programs. Again, with Plan G, it will be the FSX scenery for present.

Martin

[FSUIPC7 and 4 on same PC issue]

5 minutes ago, John Dowson said:

Ok, thanks for the update.

OK, now for the funny part: I am running LittleNavMap which will only run FSX at the moment, Alex currently updating for a MSFS connection, etc.

On another PC I have Plan G and should not be able to connect to MSFS... It is showing the MSFS planes with the Asobo  reg numbers!

 

Both connected by WideClient.

Martin

[FSUIPC7 and 4 on same PC issue]

Giving an update:

MSFS: WideClient connected, no log file produced and the ini file only shows the initial Config of Port, Window and Visible=Yes.

FSX: WideClient waiting for a connection, no ini information or log produced.

FSUIPC folder for MSFS is place on the same Disc as MSFS itself.

FSUIPC for FSX is in the Modules folder of FSX.

Should a connection be possible with both MSFS and FSX on the same computer?

Martin

 

I found beneath the desktop items that were open there was an Administrator request to accept WideClient. This had not happened on any of the other computers. It is now functioning for FSX.

[FSUIPC7 and 4 on same PC issue]

Yes WideClient. Gee, I have the user guide on 6 machines, get verifocals out again!

Thanks

Martin

[FSUIPC7 and 4 on same PC issue]

I have a new PC for MSFS and have now FSX on it as well. I have two other computers which act as clients, both of these I placed WideFS.  Wide FS will not connect for FSX and neither for MSFS.

The .ini file on one says it has picked up FSUIPC7 when I was running FSX, hence no connection!

Any ideas to on what to do?

Thanks

Martin

[Runtime error: VCRUNTIME140_1.dll was not found]

John, to be sure all is OK so far, I attach the 3 FSUIPC7 files. Interestingly  my WideFS details are there, but the log states that it is not user recognised or expired!

I also attach FSUIPC4.ini file. I'd like to have those assignments; then when FSUIPC7 is back to normal operation I can add further assignments to it.

Thanks

Martin

FSUIPC7.log FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC4.ini

[Runtime error: VCRUNTIME140_1.dll was not found]

Hi Pete, Yes it was working on the old computer. I now see where my error cam about with copying what I thought was the previous log. Earlier John was communication with me about the runtime error. When the new computer was updated to W10 v2004 I saved the files again and, of course it was the same one! Attached is the file log from FSUIPC4, 

What should I do to have the .ini file working? I have brought all the controllers in MSFS back to default, as it was in the old computer when I used FSUIPC to make changes to my controllers.

Thanks

Martin

 

FSUIPC4.log

[Runtime error: VCRUNTIME140_1.dll was not found]

As a follow on: Yes the FSUIPC7.exe launched, but after extensive work on my new computer with profiles, etc the informat in my FSUIPC7 log and the FSUIPC7 ini both show  what I was using on the old computer, but doesn't seem to be working on the new computer! Also, the WideFS is now not working, it's not connecting.

What have I missed? The FSUIPC7_prev.log is taken from the old computer.

Thanks

Martin

FSUIPC7_prev.log FSUIPC7.ini FSUIPC7.log

[Runtime error: VCRUNTIME140_1.dll was not found]

I did and that is why I posted. The new PC had to be updated to W10 V2004, and it showed all C++ installations. However, I have just reinstalled again and it has launched FSUIPC7!

 

Thank you

Martin

[Runtime error: VCRUNTIME140_1.dll was not found]

Hi Pete and John, I have installed MSFS on to a new computer and, yes, have copied FSUIPC7 over I am getting this error, see image!

 

Your thoughts, please

Thanks

Martin

[Massive FPS Drop]

As a WideFS user - it's working:)

[MFS Launch August 18, 2020]

Thank you for redirecting me to the source.

 

Martin

[MFS Launch August 18, 2020]

Hi Pete, I have ordered the Premium Deluxe boxed version of MSF from Aerosoft. I posed the question of using FSUIPC and WideClient with MFS to them and, of course, I was directed to ask you directly!

 

Are you currently working on a version of FSUIPC and WideClient for MFS and, if so, when do you see it being released?

 

Thank You

Martin

[FSX or Prepar3D crashes when FSUIPC reads weather data from SimConnect]

Thank you, I had only registered as a member of the forum after the event of the FSUIPC update. I now appreciate the necessity for a log directly after an event. Point noted.

 

Thank you for your time indeed/

 

Martin