Jump to content
The simFlight Network Forums

flying-w

Members
  • Content Count

    2,811
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by flying-w

  1. flying-w

    I got an issue among many :)

    That's working correctly, nothing will happen if you click it. It's simply there to feedback the STB Plugin DLL was loaded by the simulator. Are we good to go now? Thanks Simon
  2. flying-w

    Cockpit View plus Diversions

    Most likely you were talking by me as I'm the only person at Flying-W. I'm afraid I don't remember too much about it as I have a great deal of these kind of conversations, but let me make some general observations. 1) STB for Prepar3D has a lot more "View AI" related options, including looking forward from the AI pilot's point of view. I'm not sure any of my AI aircraft have 3D cockpits or 2D panels, but if you know how to set that sort of thing up in the simulator it would be worth exploring. STB does not have to do anything different here, it's a simulator decision concerning what gets rendered in each view. 2) The flight "diversions" as they stand today are just intended to add a little "colour" to the board. In the "reality" of the simulator the flight didn't really get diverted, but I think we mark them as such when an arrival flight shows up for a while but for whatever reason the simulator deletes it before it gets to the airport. 3) An automatic divert facility would be quite a lot of work, biggest challenge is how do I know where else to send it? STB knows about every airport the simulator does, but it's no idea about alternative destinations nor any facility to work out which alternative airports would be suitable. 4) A user driver facility where you choose the ICAO sounds more possible, I will add it to the list if it's not already there. The list is long by the way, so I can't say when this might happen or even if it will happen at all. Thanks Simon
  3. flying-w

    I got an issue among many :)

    Now I understand you a little better. What you are showing me from the client point of view is absolutely correct and normal. The deployment tab is all about doing configuration within the simulator itself, and of course if you are running STB Client on a separate computer there is no simulator there to configure. Hence the "Unavailable" in the screenshot. So let's deal with one problem at a time. There are two add-on.xml folders for STB-DS on the Prepar3D computer: "DataServer" simply starts STB-DS whenever you start Prepar3D. "Common" provides the "Flying-W Invisible Aircraft" which is a feature of little use now in Prepar3D, and also the simulator Plugin which we still need for things like "Delete AI". If "Common" is enabled as you say but netiher the Flying-W aircraft nor the STB Plugin Menu: Then the simulator isn't loading it for some reason. Do you see the above? If not, you'll need to enable "Content Error Reporting" in the simulator and send me the file it produces. Thanks Simon
  4. flying-w

    I got an issue among many :)

    1) Do you have this file on the client: If so, please send it over. Also check it's enabled in the Add-ons menu in the simulator 2) What's wrong with the AI views?
  5. flying-w

    Keeping configuration settings with re-install?

    The STB Application Data folder holds the files you are looking for. In the case of STB for Prepar3D, make a backup of the following:
  6. flying-w

    I got an issue among many :)

    Bob You say STB-DS crashes but the crash file you sent me is from STB Client? I already investigated that crash to do with logos, exact same problem as before. Soemthing in the next beta may help you understand what it is. Thanks Simon
  7. flying-w

    I got an issue among many :)

    For an Simconnect client (say STB, Active Sky, PlanG, etc.) to talk to the SimConnect Server (Prepar3D) we need to have 1) On the SimConnect Server Prepar3D, a simconnect.xml in ProgramData. The XML needs to specify a global scope on some port number of it's own choosing. Many clients can connect to a single port. It can specify other local and global scope communications points also, but at least one must be global for remote clients. 2) On the SimConnect client PC, a simconnect.cfg file is required in My Documents (may also work in the execution path of the add-on concerned, typically the install path, but I've never tried that). Simconnect.cfg points to the Prepar3D server, and in particular a global scope communication point. It does this by using the same port number as specificed simconnect.xml It's all about the port numbers really, that has traffic from one PC gets to the right application on another PC. For Simconnect (and other applications in this world), the client port and server port must match (I've actually simplifed it here, the reality is a little more involved but you don't need to worry about it. Send me your simconnect.cfg and simconnect.xml as of right now! Simon
  8. flying-w

    Simconnect error

    Hi Paul Glad to hear it's resolved as I know reinstalling windows onwards is quite a task. I've not tried PSXseecon, however I expect it will work like the other traffic injectors out there such as UTLive as far as it's interface with the simulator is concerned. For traffic injectors we do not get as detailed information from the simulator as we do for traditional schedules, so there are some limitations. Please see here for details: http://www.supertrafficboard.com/ExternalSchedulingEngineSupport.html Thanks Simon
  9. flying-w

    I got an issue among many :)

    I can use any port, and an existing entry in the simconnect.xml if other add-ons have already put something there. Just need to match the port and computer name/IP address on the client side via simconnect.cfg simon
  10. flying-w

    Simconnect error

    It's unlikely an add-on by itself could cause this kind of behaviour in Prepar3D. If it can, Lockheed Martin has a problem to fix here. You'll see plenty of these errors if you google, and mostly do to with other add-ons. The actual error code is coming from Windows, and SimConnect relies heavily on Windows network services (even when everything is self contained on a single computer) to deliver it's work. Not sure reinstalling simconnect is going to help. Unlike a lot of apps out there, STB uses the native Prepar3D v4.2 simconnect client which does not require installing in any event. That's most likely a side effect of the simconnect issue described above. All that said I will try to help, as I've never seen this error in the 10 years since I've been doing this. First of all, please check for the following files and send them over to me if you have them 1) My Documents/simconnect.cfg 2) simconnect.xml from the Prepar3D Program Data Folder. (check the application data folder also) Thanks Simon
  11. flying-w

    I got an issue among many :)

    Bob On your Prepar3D computer, just simconnect.xml On your separate STB client computer, just simconnect.cfg Unless you have some particularly complicated setup where you need multiple connections on different ports or add-ons that require something unique from SimConnect, the STB configuration wizard (and the one in STB-DS) will take care of these files. For whatever reason, computer names seem to work better than IP addresses here. Thanks Simon
  12. flying-w

    I got an issue among many :)

    Bob, your simconnect.cfg file is wrong. It should be plain text, while yours for some reason is XML and it looks more like the simconnect.xml file which it should not. Mine looks something like this: [SimConnect] Protocol=Ipv4 Address=192.168.0.31 Port=9017 MaxReceiveSize=4096 DisableNagle=1 Thanks Simon
  13. flying-w

    I got an issue among many :)

    Send me the simconnect.xml from the LM Program Data Folder and I'll have a look Thanks Simon
  14. flying-w

    Is there a way to go back?

    1. Already done, 30 seconds work. Expect it in the next beta!
  15. flying-w

    Is there a way to go back?

    1. It means there are still problems in your Traffic BGLs. However I will consider moving this to the new content error reporting system so you can turn that message off. 2. Add the "Object ID" column to your display. Set up a trace as per Appendix C of the user guide, restart STB, reproduce the problem, send me the trace file and a new screenshot showing one the problem. Make sure the Object ID value is visible for each flight in the screenshot. 3. Can't really imagine what it is without a picture. What version of STB are you currently using? Thanks Simon
  16. flying-w

    Airport names

    Sorry I'm afraid there isn't - the airport names come from the simulator AFD files so you'd need to change it there. Simon
  17. flying-w

    New Router and cannot now connect to Data Server

    I've no idea how Windows goes about figuring out the computer name to IP address to MAC address relationship, but I guess it just took its sweet time on this one. Typilcally there's no meaningful error with this sort of thing, just "connection timed out" which is all Microsoft is prepared to tell us. Simon
  18. flying-w

    Is there a way to go back?

    Cancelled arrivals are typically flights expected to happen on the basis of the traffic BGLs, however for whatever reason the simulator never created them. The number of flights you see at any particular airport is highly dependent on the choice of AI package, quality of schedules therein and the airports involved having sufficient parking for the demands of the traffic BGLs. What you see is not unreasonable, but like I say there's no hard and fast rule. Simon
  19. flying-w

    Compiler crashing with Multi-week plans

    Good to hear, thanks for letting me know. Simon
  20. flying-w

    Compiler crashing with Multi-week plans

    I'd like to think it's all complete in the "Official Update", not had any reports of trouble from anyone while it was in beta. You must be on 4.2.2018.20200 or later for this to work, as it changes the content of the traffic BGLs I read. Simon
  21. flying-w

    Compiler crashing with Multi-week plans

    Please see the following: "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. " FSX never claimed to support multiweek schedules for AI aircraft so we are all fortunate this is working in any shape or form. Simon
  22. flying-w

    Configuration crash

    It means in your scenario the file is required, it was always going to be a long shot.
  23. flying-w

    Configuration crash

    Last two suggestions I'm afraid: 1) Delete trafficboardfrontend.exe.config 2) If that does not help, consider reinstalling Microsoft .net V2 and V3.5 Sorry I can't find a better solution. Simon
  24. flying-w

    Crash

    OK, It's one of your "Piedmont" flights. Most are fine, but one is crashing. I'll have to add more debug to determine what the problem is, because it looks fine from the trace. Simon
  25. flying-w

    Is there a way to go back?

    There's a mismatch in your airport database files, so something went amiss somewhere when you were uninstalling. Go to your STB Application Folder, then the Database folder, then delete files ending in ".bin". C:\Users\simon\AppData\Roaming\FlyingWSimulation\SuperTrafficBoard V4 Client\Prepar3D V4\Database
×

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.