Recommended Posts

Posted (edited)

Hi Everyone have recently made the move from FSX to P3D and made several flights including to FSDT sceneries in the PMDG B77W with no problems.  I got a message to update my fsdt sceneries via the live updater which I did with P3D closed, then did a flight only to find my KMEM scenery missing after a 5 hour flight from PANC.  Talk about frustration!! 

Looking at all my FSDT sceneries they have all disappeared despite them being active in my scenery library.  Does anyone know what to do in this situation.

In FSX a restart generally saw them return but not on this occasion.  

Any help or advice would be greatly appreciated.

Edited by barramundilure

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

2 minutes ago, barramundilure said:

Hi Everyone have recently made the move from FSX to P3D and made several flights including to FSDT sceneries in the PMDG B77W with no problems.  I got a message to update my fsdt sceneries via the live updater which I did then did a flight only to find my KMEM scenery missing after a 5 hour flight from PANC.  Looking at all my FSDT sceneries they have all disappeared despite them being active in my scenery library.  Does anyone know what to do in this situation.

In FSX a restart generally saw them return but not on this occasion.  

Any help or advice would be greatly appreciated.

Have you posted this at the FSDT forums? http://www.fsdreamteam.com/forum/

Share this post


Link to post

yep  first port of  call is the fdst  forum  first,  you can  try  manually  using the  addon manger  to  update  from the  fdts  web  page

Share this post


Link to post
Posted (edited)

It happened to me several times during P3D V3 time. Already had a big dicussion at FSDT but after all, none helped. It happened every once a while.
Then I moved to V4 and it happened couple times again. That is before the new FSDT Live Update system take place.
I don't know now since haven't done any flights for months, but it seems you are talking about the same issue. It happened to me once after 16 hours flight. Unbelievable. 

Edited by Hoang

Share this post


Link to post

I ran the updater again and got them back but I have to say that i am done with FSDT and its upgrading system.  It truely sucks, and I am almost certain it's what crashed my FSX setup and forced me into P3D.

Its a pity - good sceneries let down by a terrible updating system.

Share this post


Link to post

simple  solution if  you  are  done  with  fdst   is  to uninstall  them

Share this post


Link to post
2 hours ago, barramundilure said:

I ran the updater again and got them back but I have to say that i am done with FSDT and its upgrading system.  It truely sucks, and I am almost certain it's what crashed my FSX setup and forced me into P3D.

Its a pity - good sceneries let down by a terrible updating system.

Actually if you restart the sim the airport(s) will work fine again, no need to run the update or anything. Not only the airports but also GSX will not work. None of the FSDT products will work if we get into that situation.

Share this post


Link to post

I tend to run the FSDT updater from my desktop not in the sim at least one`s a week and have never yet had a problem with FSDT airports and I have most of them, I also run make runways after installing addons in P3Dv4.

And in the sim you can check the addon manger to see if they are active and installed.

  • Upvote 1

Share this post


Link to post
Posted (edited)

edit

Edited by Rockliffe

Share this post


Link to post
Posted (edited)

This issue has been discussed, answered, and SOLVED already, just a few hours after it was first reported on our forum. And I stayed up all night (until 7:00 AM), until I was sure it was completely fixed, because such hard crashes are taken very seriously.

It affected only users still running P3D 4.1, because we released an update by mistakenly assuming that most of GSX users would have upgraded to 4.2 by now, since 4.1 was extremely buggy with GSX, due to the missing texture problem, which has been fixed only in 4.2.

There was a single line of code that called into a specific 4.2 function, which resulted in the program crashing when run under 4.1, because we still linked to the 4.1 Simconnect, in order not to FORCE users to upgrade to 4.2, which is what would have happened if we used the 4.2 Simconnect, since it's not backward compatible with 4.1 so, the result would have been the same, the software wouldn't start, and GSX and all FSDT sceneries would be gone just the same.

Fortunately, LM stil let you download the 4.1 Client (even if they suggest not to do it)I was able to downgrade my install and found a solution that still works with both 4.1 and 4.2, which has been posted online just a few hours after the issue was first reported on our forum so, it would be enough to just run the Live Update again to get the fixed file, which so far seems confirmed to have fixed the problem for everyone that reported it.

Guys, these things HAPPENS, like when a specific release of FSUIPC (5.123c I believe) prevented P3D from starting, but I haven't see many complaints, other than the usual jokes about Pete being on vacation when a new P3D comes out. And in this case, it was ALSO a very similar problem of different Simconnect versions used.

The issue is, LM suggest developers and users too should always upgrade to the latest version. P3D doesn't use the otherwise pesky and complex Side-by-side loading method, so FSX (when it worked), allowed multiple addons using different releases of the SDK to all run together in the same memory space. It was nice, when it worked, but it was almosts impossible to troubleshoot when it didn't. P3D switched to a different method, which is Static Linking so, an addon made for 4.2, for example, won't even START on 4.1.

Since we know that, because of *other* addons still not compatible with 4.2, some users haven't upgraded, we stayed with the 4.1 SDK, which is compatible with 4.2 so, in theory, it was supposed to work in both versions but, unfortunately, I left a single line of code calling into something 4.2-specific, which resulted in a crash on 4.1.

And just for full disclosure, the function used was related to the new PDK camera SDK. In the constant strive for the maximum efficiency and performance, we stopped used the Simconnect method to ask the sim for the positions of the eyepoint (used by GSX *sounds*, to know where you ears are located) and, since this MUST be done at each frame (the sound would not be smooth if it wasn't), in order to reduce traffic on Simconnect, and be a better citizen in relationship with other addons, we switched to the native PDK solution, which gets data from memory in the official way (no hacking), without having to go through the Simconnect client-server connection, which is shared with all your other addons so, this solution is better for performance, more friendly with other addons, and it's 100% officially documented. It's just what we used in the "4.2 way", without noticing it, but it's all fixed now: the method is still the same, just it's compatible with 4.1 too.

Edited by virtuali
  • Like 3
  • Upvote 5

Share this post


Link to post
Posted (edited)
50 minutes ago, rjfry said:

I tend to run the FSDT updater from my desktop not in the sim at least one`s a week and have never yet had a problem with FSDT airports and I have most of them, I also run make runways after installing addons in P3Dv4.

And in the sim you can check the addon manger to see if they are active and installed.

I actually do the same, and I never have any issues or problems with coault or FSDT's sceneries.

Can't for the life of me understand why people keep complaining about this... In my experience, most of the times, it's the users own mistake, fault or misunderstanding of their system setup, which is leading to instability or weird behaviour of the sim or addons...

Edited by Anders Bermann
  • Like 1
  • Upvote 1

Share this post


Link to post
Posted (edited)
25 minutes ago, Anders Bermann said:

Can't for the life of me understand why people keep complaining about this... In my experience, most of the times, it's the users own mistake fault, which is leading to instability or weird behaviour of the sim or addons...

Well, in this case, no user was at fault.

If we tested it on 4.1, we would have found it before release but the issue is, 4.1 was so bugged with GSX, that I couldn't foresee a GSX user not updating to 4.2 as of today. 

Now, before it starts getting funny, let's say that 4.2 add its own different class of issues to GSX (and every other addon with a menu), but there are workarounds, while there was no way to fix the black textures problem in 4.1, other than just reducing the number of addons installed.

Edited by virtuali

Share this post


Link to post

I did experience one issue where I flew from KSAN to KLAX and KLAX was not there. Even thought, the airport was successfully activated. I check the AM after the incident and it read activate. I double clicked on my activation file, and never had that happen again.

At first I was angry and was going to scream and shout, but I thought about how awesome FSDT sceneries are and I convince myself that it was worth it.

It has not happened again with P3d v4.2.

Share this post


Link to post

I've had my fair number of complaints with FSDT over the years, and I still have a pet peeve with their updater removing my customized AF files, but my experience with their products with their updater in the past past year has been good and I found if I mark the AF file as read only they will be left in place.  I look forward to their increased use of the PDK strategy which is a very good solution to the many limitations of simconnect.  My biggest complaint today is that KORD update is loooong overdue!!

  • Upvote 2

Share this post


Link to post
19 minutes ago, downscc said:

I mark the AF file as read only they will be left in place.

+1 Thanks for this tip.
I have to add KIND to several sim.cfg files otherwise the default GSX liveries loaded instead of the current desired airline.

Share this post


Link to post
6 hours ago, bills511 said:

+1 Thanks for this tip.
I have to add KIND to several sim.cfg files otherwise the default GSX liveries loaded instead of the current desired airline.

Bill,

Could you expand/clarify on this...I'm not sure I understand what you're talking about, but have a feeling it might benefit me to know.

Regards,

Share this post


Link to post
6 hours ago, downscc said:

I've had my fair number of complaints with FSDT over the years, and I still have a pet peeve with their updater removing my customized AF files, but my experience with their products with their updater in the past past year has been good and I found if I mark the AF file as read only they will be left in place.  I look forward to their increased use of the PDK strategy which is a very good solution to the many limitations of simconnect.  My biggest complaint today is that KORD update is loooong overdue!!

Dan,

Is "AF file" AFCAD file (.bgl)?

I'm not sure what you're talking about, but I think I might benefit from knowing what you're doing?

And a HUGE +1 regarding ORD...man do we need a new one. I'm tired of trying to figure out taxiways and runways, when my aircraft FMS's and P3D nav data/magvar tables are up-to-date, but the ORD airport layout is completely wrong.

Regards,

Share this post


Link to post
Posted (edited)
1 hour ago, somiller said:

Bill,

Could you expand/clarify on this...I'm not sure I understand what you're talking about, but have a feeling it might benefit me to know.

Regards,

There are several folders in (P3D\Addon Manager\Simobjects\Misc\) of each GSX objects; FSDT_Baggage_, FSDT_Cargo_, FSDT_Pushback_, and FSDT_Staircase_. In each folder is a sim.cfg file.

For KIND the airlines AA, DL, FFT, UA, and WN always load a default GSX vehicle.

What I edit in the sim.cfg: For example I look for the airline (AA for American) and add KIND to the end of couatl.icaoprefixes= line.

[fltsim.7]
title=FSDT_Baggage_Loader_AA
model=01
texture=AA
couatl.icaoprefixes=K KDFW KJFK KLAX KMIA KORD KBOS KSFO KDEN KMCO KDCA KTPA KPHX KPHL KMCI KMEM KCLT KSDF KIND
couatl.atc_parking_codes=AAL,AALX,LOF

Save file, open the file properies and set as read only so each time you run the FSDT updater it will ignore the read only sim.cfg files.

Edited by bills511
  • Upvote 1

Share this post


Link to post
13 hours ago, somiller said:

Dan,

Is "AF file" AFCAD file (.bgl)?

I'm not sure what you're talking about, but I think I might benefit from knowing what you're doing?

And a HUGE +1 regarding ORD...man do we need a new one. I'm tired of trying to figure out taxiways and runways, when my aircraft FMS's and P3D nav data/magvar tables are up-to-date, but the ORD airport layout is completely wrong.

Regards,

Yeah, I like to use AF instead of AFCAD for the airport file because the program AFCAD is an ancient fossil, most popular today is ADE.  You could also call them ADEX files (compiled for FSX) or ADEP for P3D.  There is a payware AF file editor at Aerosoft (AFX files) but the free ADE is much better.  GSX has gotten pretty good at customizing a parking place so that has eliminated some of the need to edit the AF file, but the primary reason is to modify the taxi links at a parking spot to provide a realistic backup that GSX follows.  It is ironic that I modify the AF to take advantage of GSX features but then FSDT wants me to use their AF files.  The secondary reason I modify AF files is to correct navaids, for some reason developers (not pointing a finger a FSDT here, this is all developers) seem to think it is okay to use default navaids in payware and at least in the US the default navaids at airports is almost always wrong.

I place my AF in the scenery folder, add an ".OFF" to the developer's AF file and from then on, GSX will use my AF file for parking and pushback.  I mark both files 'read only' so when i run the updater all I have to do is go through each FSDT scenery folder and delete the new AF the updater put there and leave my AF file and their .OFF file alone.  I should point out that I do not use AI traffic so I really don't care about taxi lanes and gate assignments, which are of paramount importance to users of AI traffic and would want updates from FSDT for the AF files.  I've asked FSDT in the forum a couple of times to provide an option to not replace AF files but it's not something he wants to do.

  • Upvote 1

Share this post


Link to post
3 hours ago, downscc said:

I've asked FSDT in the forum a couple of times to provide an option to not replace AF files but it's not something he wants to do.

Why you say that ? You have TWO options at your disposal to prevent files for being updated:

1) The creation of a text file named DONTUPDATE, which will prevent the updater from updating *anything* in the folder you place it, and this was added to the Live updater in June 10th 2017, just 8 days after the Live Update was released first:

http://www.fsdreamteam.com/forum/index.php/topic,15922.0.html

2) The question which recognizes that, when the AFCAD is updated, will ask you if you want to overwrite your version. This has been added a bit later, September last year I think.

Of course, this question can only work if your modified file has the same name of our original one, or it the file changed because we updated it, and in both cases you are being given the option to update or not AND it will do a backup of your existing file anyway, in a "backup" sub-folder.

So, if the reason of using a different name was to prevent your file to be overwritten, there's no real need for it anymore, because you can now safely keep the original name, and just reply NO to the update question, without worrying about replying YES by mistake, since a backup will be made anyway.

And, by keeping the same name as the original file, you won't lose an eventual GSX customization we made for our own airports, which is tied to the name of the AFCAD (if the name is different, GSX will work in "default" mode, like on an unknown airport, leaving you with the onus of having to customize it from *scratch* in GSX).

Share this post


Link to post
16 hours ago, bills511 said:

Save file, open the file properies and set as read only so each time you run the FSDT updater it will ignore the read only sim.cfg files.

This is useless now, and possibly VERY dangerous to do, because (and we *did it* in the current update) we might change other parameters not related to the airline assignment, for example the object measurement in the [Couatl] section, or the various "Conditions" that will add additional control to the object usage, usually tied to the size of the parking, the airplane weight, the airplane kind (cargo/non-cargo), etc.

So, by making the file read-only, you are preventing the updater to do its job, possibly causing strange behaviors, because we might have updated the software, expecting the objects having all the most current parameters, but they don't, because you blocked from updating them. Sometimes, if we add an entirely new parameter which the updated software requires, if it's not there (because you kept the old version), it might crash with an error, since it was looking for data that's just not there.

Since more than a year, with the August 10th 2016 update:

http://www.fsdreamteam.com/couatl_liveupdate_notes.html

We added the ability to override the operators assigned to an airport, without touching the AFCAD and without touching the SIM.CFG  of the GSX vehicles, which was really a pain to do (that's why you wanted to prevent them to be updated...)

The airline codes you set in the GSX parking editor will override *everything* set in the GSX SIM.CFGs files, and you can do it by parking, by terminal, or even by airport, depending what you have selected in the left side tree-like structure.

The Airline Codes override is also explained in the GSX manual, on page 29.

Share this post


Link to post

@virtuali Thank you Umberto,
I did away with the sim.cfg read only attributes and ran the live update. The airline code entries in the GSX customization were already entered without any input from me but the default liveries were still loading. So what I did was reenter the codes and hit apply and now the correct liveries will load. GSX is now working as intended.

Share this post


Link to post
3 hours ago, bills511 said:

The airline code entries in the GSX customization were already entered without any input from me but the default liveries were still loading. So what I did was reenter the codes and hit apply and now the correct liveries will load. GSX is now working as intended.

Yes, this is how is supposed to work.

If you don't edit the codes, it will show you what's in the AFCAD, so you have an idea of the codes there, which will be used only to break ties if an operator is already assigned to that airport from the SIM.CFG files.

If, instead, you edit them manually, even if you put the same code as before, GSX will know that you did it yourself, so it will ignore its own assignments, and will trust what you set.

Yes, I know the user interface it's not entirely clear about this so, the next upgrade will modify the window a bit, showing the existing unedited codes as greyed out, and there will be a checkbox named "override operators", which will enable the editing field, making it more clear what's really happening.

Share this post


Link to post

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