Jump to content
The simFlight Network Forums

Leaderboard


Popular Content

Showing content with the highest reputation since 03/19/2019 in all areas

  1. 2 points
    Think that would be a long shot as not sure the current game coding could cope with that one (and as we all know the door has been shut on any development of the current platform!) Probably need to add this to the wish list for the next version once opened up on the forum (along with helicopters which @battlehawk77would love as well!)
  2. 1 point
    Thanks! In the coming days (or perhaps weeks) there will be another update. Probably no changes to the code, but just to keep up with the avalanche of content from AIG just lately. Simon
  3. 1 point
    About STB Betas: Betas offer “leading edge” changes and are the fastest way to get new functions and bug fixes. Compared to “official updates” they may have received slightly less testing with an ongoing effort to bring testing up to "Official Update" standards. The risks are small but should be understood, and I'm here to help with any beta issues. It’s highly valuabled to us when people try betas, and report their experiences as they wish. Here's the next beta update for STB for Prepar3D V4, the first of 2019 with the following changes since the last official update: Summary of Changes in V4.2.2019.08800 Added name and location of the simulator Traffic BGL file supplying each flight to the flight details dialogue. Added content support for Alpha India Group (AIG) “One Click Installer”, covering all airlines suitable for the OCI up to March 2019. Update Make Runways utilities to V4.8.7.1. Fixed bug which ignored flight plans described in a schedule BGL file where the file extension (BGL) is in upper case. Fixed bug that caused mismatches between materialized flights and predicted flights where the aircraft title > 32 characters. We now support titles up to 64 characters. Fixed various problems with reporting blank, null or whitespace-based paths occurring in simulator configuration files, to the content error reporting system. Fixed exception generated when a keyword=value pair occurring in a simulator configuration file contains a value which itself contains one or more equals signs. Fix problem where STB operated aircraft would not go through departure workflow. Fix incorrectly calculated next departure flight schedule time in flight details dialogue. Deprecation of the majority of legacy UT2 code. You can download the STB Client update from here: http://bit.ly/2WqI7fe And the STB Data Server combined update and installer from here (only required on the Prepar3D computer when running STB Client on a separate computer: http://bit.ly/2HLpdfT Simon
  4. 1 point
    I'm new to this awesome sim and this is fantastic! Thanks for taking the time to produce it.
  5. 1 point
    Would love to see all the Real Traffic files blown up and started over. The airlines and airports files really need cleaning up.
  6. 1 point
    Shameless plug, but I did create a real-life schedule for MCO to be used with RT and RC. 🙂
  7. 1 point
    Magic. Thx . I was tilting towards EDDM and KMCO so that's good.
  8. 1 point
    Created another schedule for KPHL, enjoy the airport quirks and all. Found this schedule to be pretty hectic at times making it a decent challenge. Some fun GA and overall works without issues. Testing a few GA's that may have problems but any issues you find I'll see what I can do to fix. Feel free to re-post or what have you and enjoy :) Video for 8am from the schedule here. I played it with a self imposed "scenario" which hosed me but was fun overall lol. Got annoyed at a few bits, myself and just for fun of pushing through. Download Available Here Update: 4/7/2019: Corrected Duplicate plane at 3pm hour. Fixed chart.
  9. 1 point
    Never mind clicked on it. Code needs to be: All works now Thank you
  10. 1 point
    Open you main Tower 3D folder. Open the file Tower3D.rec Add the following text in the logical spot: #airplane1; PUSHBACK APPROVED, EXPECT RUNWAY ;#runway1; VIA ;#taxiway1;#taxiway2;#taxiway3;#taxiway4;#taxiway5;#taxiway6 #airplane1; PUSHBACK APPROVED, EXPECT RUNWAY ;#runway1; AT ;#taxiway1 #airplane1; PUSHBACK APPROVED, EXPECT RUNWAY ;#runway1; AT ;#taxiway1; VIA ;#taxiway2;#taxiway3;#taxiway4;#taxiway5;#taxiway6 If desired, you may also add one more: #airplane1; RUNWAY ;#runway1; VIA ;#taxiway2;#taxiway3;#taxiway4;#taxiway5;#taxiway6   It gets rid of the cumbersome "Delta 2143, Runway 26L. Taxi via Echo." Now you can just say "Delta 2143, Runway 26L via Echo." To me, at least, this is much more intuitive. Enjoy Andrew
  11. 1 point
    MOVED FROM "FAQ" SUBFORUM TO SUPPORT FORUM, the proper place for SUPPORT! It is little to do with FSUIPC. All the facility does is call the SimConnect facilty to save a flight. It is, in fact, exactly the same as using the menu to do so, or using the Ctrl+; shortcut 9I think that's the one). Any "stuftter" this may cause is directly realted to one or both of two things: 1. The use of sohisticated add-on aircraft such as PMDG ones which also then freeze the sim whilst they collect the data from their assorted subsystems so that they can save that too. 2. A slow or nearly full disk, or one in need of de-fragmenting, plus a lack of sufficient free memory for a decent cache. Both of these applies no matter how you save a flight. There's no way FSUIPC can avoid either. The actual code in FSUIPC is pretty much merely the call to SimConnect. The subject is virtually flogged to death, especially on the AVSIM forums. Go take a look. Pete
  12. 1 point
    Consolidated file sent to Gabor today. Will let you know progress etc once Gabor has had a chance to look at the requirements and the time taken to create etc. He is pretty busy with other work at the moment Regards Gary NEO_RC Requests_MASTER.xlsx
  13. 1 point
  14. 1 point
    Hey guys, I'm very pleased to say that the JFK RC update is out now! Big thanks to crbascott, Braf123456, hexzed and Pedantic G! Version number: SP3 Have a great time controlling! Gabor
  15. 1 point
  16. 1 point
    I was told that it could be confusing that I have combined commands with a separator. Therefore I have revised the PDFs, corrected a mistake and also attached my modified tower3d.rec. I hope the voice commands are now more readable. If there are still problems, please contact me or post here in the thread.
  17. 1 point
    Yes you will have to load JFK last in the order. It definitely works though. I numbered it 44.
  18. 1 point
    As well as what John says, generally, whether moving to a new system or merely re-installing windows, attention needs to be paid to the Joystick device identification. The way a device is recognised uniquely is via a thing called a GUID, which is a really big number generated and assigned by Windows when it first sees the device. Those numbers will be different on a new machine or after re-installing windows. Assignments are much easier to sort out again, without re-doing them all from scratch, if Joy Letters were assigned beforehand. Then all the individual assignments use the letters instead of the numerical joystick ID. Then, after moving things over or re-installing, it is just a matter of editing the assignment of letters to devices in the [JoyNames] section of the INI file. John or I can help you sort this out now, which is why he's asked for some files from the new PC. Comparing the assignments between those and the old ones will provide the solution.
  19. 1 point
    Hi Dane, copying across your old files should be fine (presuming you installed FSUIPC first), with some caveats. However, if FSUIPC is not recognising your devices, we need to see the files (log, ini and joyscan.csv) from your current installation, the one with the issue, not your old system. Cheers, John
  20. 1 point
    AIG is stellar, I'm glad I took the trouble to download the OCI and it's all so effortless (time consuming yes, but it was like that with WOAI to) and there's just nothing hard about it. The content is coming along. I've about 30 airlines left requiring IATA codes (down from around 200 at the start), plus a bunch more logos. This may come in two waves, as some logos we can make do with for the time being until they all get upgraded. PS. A lot better now - thanks for asking. Personally the last 4 months have been a difficult journey, as where the last 4 years before that (professionally speaking). Simon
  21. 1 point
    Just checked, I think the latest version is there: What are you seeing? When I first uploaded this, I noted some latency before the files showed up on the public side of the web page, and I also had to clean my browser cache. Thanks Simon
  22. 1 point
    The list can get fairly long. The hardest part for me is to keep up with the newcomers, LCC's going bust and mergers. Not to take anything away from Gabors hard work but I notice that the airlines.txt list put out with each new A/P does still contain a number of defunct airlines and a couple that have merged or their data has changed. Would it make sense to start an airlines sticky post like latest schedules post etc. where any changes to airlines can be listed and as individuals we can update our own airlines.txt files. I don't think this would have any copyright implications as the .txt files are not owned by anybody to my knowledge. Kev M
  23. 1 point
    Yep, this got no traction back in 2017 while now it seems there is an interest with Gabor seeming to be open to ideas like these. Maybe I was ahead of my time. 😉 Sadly, though, I really don't care anymore. 😢
  24. 1 point
    I wouldn't say correctly, but it is somewhat close. Fixing gate definitions and other issues are definitely something needed in the next version.
  25. 1 point
    To keep pace with the market, the needs of the majority of users and make the best use of time, we have decided to end STB development for the older simulator products, including: Prepar3D V1; Prepar3D V2; Prepar3D V3; Prepar3D V4.0 through V4.3; Microsoft Flight Simulator X (in all forms including Steam Edition); If one of these is your simulator, you can continue to enjoy and use STB as it stands today and we recommend you install the latest updates relevent to each version. STB will continue to be available for purchase on the older platforms, however I won't be making any more changes to the software, addressing defects and support will be limited to know issues. That said, I may still publish content updates (for example airline logos and flight codes) as the various AI packages available continue to evolve. Prepar3D V4.4 is our fully supported platform for STB, and I expect resolution of bugs and new feature introduction to be focussed here. Many thanks, Simon
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

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.