Search the Community
Showing results for tags 'prepar3d v4'.
Found 4 results
-
STB Client and Data Server OFFICIAL Update V4.2.2018.20200 for Prepar3D-V4.2, V4.3 and V4.4
flying-w posted a topic in Flying W Simulation
Here's the next official update for STB for Prepar3D V4, major changes in bold: · Further content updates (airline logos, aircraft and airline configuration files) for Just Flight TrafficGlobal. · Major upgrade of the STB Date-Time architecture to support 64bit values and multiweek schedules. The latter provide schedule repeat periods of TWO, FIVE and EIGHT WEEKS in addition to the default. · Dates now presented in US format (e.g. Month Day) when the local Windows culture is set to US (or any other culture that uses the same convention). · Added the schedule repeat period value to flight details dialogue and show both local and Zulu schedule times when tracing is set to verbose level. · STB is compiling all traffic files starting with ".BGL", rather than those that are ".BGL” exactly. · Bug fix: When determining the width of the airline logo column, the AirlineLogoWidth setting is always used rather than column properties saved to the settings file. · Bug Fix: Null exception caused by STB AI Observer · Add a small margin to the airline logo width column to ensure it displays correctly. · Added exception handling to the methods that handle callbacks from Simconnect that would otherwise fail silently. · Force integer division to double precision where the result can be -1 > 0 < 1, to avoid underrun. The multi week schedule support turned out to be a huge piece of work, essentially requiring a new approach to the concept of time in STB which took quite some time to get done. We need a more flexible approach when displaying date/times, so here's an example of what you'll see with a multi week schedule: Flights that occur a week or more away include the full date and time, while those from tomorrow up to a week just include the day name. The other big change is support for the US style date format, and any other cultures that present the month before the day name. In other words, looking at the screen shot you will now see "Sun Jun 25 06:24" instead of "Sun 25 Jun 06:24". The format is automatically set by the culture your Windows PC is using. You can download the STB Client update from here: http://bit.ly/2JFmf9m And the STB Data Server combined update and installer from here: http://bit.ly/2Ocw6aj STB Data Server is a separate free of charge component, only required on the simulator computer when you are using STB client in a separate remote computer. Please note it is mandatory to update STB Data Server when updating STB Client (using the above links) Many thanks Simon -
I've been running Prepar3D v4 Professional with FSUIPC V5, but suddenly for no apparent reason the FSUIPC5.DLL file, in the Modules folder, is stopping Perpar3d.exe from starting. If I delete the FSUIPC5.DLL file then Prepar3D will load and run. I've tried re-installing FSUIPC again, but it goes back to the same problem. I'm assuming there's a file in Prepar3D that has been corrupted? Can you please help? Thanks Matt
-
Run IvAp v2 at Prepar3d v4 start with FSUIPC5
Jose Vela posted a topic in FSUIPC Support Pete Dowson Modules
Hi I know this topic has been covered before but I've not been able to start IvAp v2 just including the RunIf sentence in the FSUIPC.ini file. This is the path that I use in the desktop shortcut I use to manually open it: "C:\Program Files (x86)\IVAO\IvAp v2\ivap_dllhost.exe" "C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx.dll" I will apreciate any advice as I have tried many combinations of "", Thanks! Jose -
Prepar3d V4 Crashes after installing FSUIPC
VicoLee posted a topic in FSUIPC Support Pete Dowson Modules
Hello all! When I open Prepar3d V4, it loads the splash screen disappears, and acts like it isn't even open. In the task manager, it shows it's open and running. I found out if I take out the FSUIPC .dll file from the modules folder, and reload Prepar3d, it opens perfectly, but FSUIPC isn't running. I have: 1. Deleted the Prepar3d files in the Local,Roaming, and Program Data. 2. Run Prepar3d in admin mode 3. Reinstalled Prepar3d V4 Thanks in advanced!
