FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: kodaryu on September 23, 2022, 04:10:30 pm
-
I also made an update. I also did a reinstall. No corrections.
-
Same here. Garbled text with distance readout selected after updating today.
-
we know hes more worried about the cash cow that is ms2020, and we all know hes not going to pay another staff member to work on the p3d mess.
he couldnt give a toss about the p3d customers, thats old money.
-
MSFS=GSX PRO. We are P3D/FSX = GSX Ama ;D
We may be an experiment. It is very disappointing :'(
-
These kind of comments are very hurtful, considering the time we spent FIXING this problem. The problem doesn't obviously happen here, I double check the updater, and it downloads the correct update file that fixes the problem, see the attached screenshot I just took now.
The files that fixes the problem are the following ones:
\Addon Manager\Simobjects\Misc\FSDT_Font\model\FSDT_Font.mdl
\Addon Manager\Simobjects\Misc\FSDT_Font\model.numbers\FSDT_Font.mdl
If you want to know if you got the correct version, find an MD5 checker utility, and verify their MD5 hash is:
D27EB39C270550A6DA8A66788345FD1A
-
These kind of comments are very hurtful, considering the time we spent FIXING this problem.
screw feelings, this is business. people have paid good money for your software. Man up, get some more staff and create two installers for each sim.
-
These kind of comments are very hurtful, considering the time we spent FIXING this problem. The problem doesn't obviously happen here, I double check the updater, and it downloads the correct update file that fixes the problem, see the attached screenshot I just took now.
The files that fixes the problem are the following ones:
\Addon Manager\Simobjects\Misc\FSDT_Font\model\FSDT_Font.mdl
\Addon Manager\Simobjects\Misc\FSDT_Font\model.numbers\FSDT_Font.mdl
If you want to know if you got the correct version, find an MD5 checker utility, and verify their MD5 hash is:
D27EB39C270550A6DA8A66788345FD1A
Correct me if I'm wrong but your customers including myself are very frustrating. I do know how hard you tried to bring our GSX back for our P3D4.5.
I fly in and out of ATLANTA everyday and almost can't use GSX because it cut so many gates from 100% to only 10%. For example, Terminal D has about 40 gates, with defective GSX, only 10 or less gates available.
Can't even use fuel truck, it came and go, that's it. 2 guys doesn't even get out of the truck and do animate.
For my CRJ-200, they uploaded duplicated loaders and baggage carts. I don't need duplicated.
I certainly hope you will find a way to bring our GSX back very soon so we can fly HAPPILY! :)
-
Man up, get some more staff and create two installers for each sim.
We already have two installers, that's not the issue. As explained so many times, the fact lots of GSX code is shared between P3D and MSFS, is the ONLY thing that will make us supporting P3D for the foreseeable future.
screw feelings, this is business.
You got it backwards: it's *because* of feelings that you are still getting updates. If we only had to look at business, (the cold hard sales numbers), we should have dropped all FSX/P3D support, like everybody else is doing.
-
Correct me if I'm wrong but your customers including myself are very frustrating. I do know how hard you tried to bring our GSX back for our P3D4.5.
And as I've said so many times already, I KNOW in P3D 4 the situation is much worse, there's one P3D4-specific problem caused by an abnormally long time to generate the MODEL cache ( not the airport cache ), which doesn't make any sense, since in P3D4 we have much less model variations that any other sim, thanks to the Render to Texture feature, and this causes the program to timeout and basically stop working.
We are trying to understand why it happens, I must admit we did most of the testing in P3D V5, but we'll surely find the reason.
-
Thank you Umberto for your hard effort. Deeply appreciated.
Couldn't waaaaaaittttt to finally have the GSX back to normal.
Umberto, I wanna tell you something. I saw MSFS and my goodness! They're hundreds and hundreds times better than Prepar3d but unfortunately, the ones I wanted (CRJ-200) won't be available until late 2023 to early 2024. It is developed by VirtualCol.
I use CR2 everyday. That is why I couldn't buy MSFS until VirtualCol finally released the CRJ-200's and will bid a farewell to lousy P3D!
;)
-
Umberto,
Although I do not use GSX (P3Dv4.5) as much as I used to, and I have not observed the font issues mentioned above, I decided to check the MD5 hash for the two files you listed. The MD5 checksums are different.
FYI, the 1st file is dated 8/3/15 and the 2nd is dated 10/2/17.
Claude
-
These kind of comments are very hurtful, considering the time we spent FIXING this problem. The problem doesn't obviously happen here, I double check the updater, and it downloads the correct update file that fixes the problem, see the attached screenshot I just took now.
The files that fixes the problem are the following ones:
\Addon Manager\Simobjects\Misc\FSDT_Font\model\FSDT_Font.mdl
\Addon Manager\Simobjects\Misc\FSDT_Font\model.numbers\FSDT_Font.mdl
If you want to know if you got the correct version, find an MD5 checker utility, and verify their MD5 hash is:
D27EB39C270550A6DA8A66788345FD1A
For the file FSDT_Font.mdl I get MD5 hash FCAF21ABE30F9DD69ACEB6074FA4110B for FSDT_Font\model and MD5 hash 7D45E01C87AFC4BC7F34E6C78CDEACA4 for FSDT_Font\model.numbers
-
Those are the same ones I got.
-
Here the same
-
Try the Live Update again, it should be fixed now.
-
Can Umberto re-instate an older working version of GSX for P3D v5
-
Try the Live Update again, it should be fixed now.
Same result for me. Wrong MD5 hash and garbled text appearing after latest Live Update.
-
me too ;)
-
Me too.
-
Try the Live Update again, it should be fixed now.
Same result for me. Wrong MD5 hash and garbled text appearing after latest Live Update.
The garbled characters can't be cured, and when I tried to move PBB, it turned in a different direction and stopped working. :D ;D ;)
-
Just ran Live Update.
There is no change to the MD5 hash for the two mentioned files.
I did load a scenario at EDDF (Aerosoft). A brief chk of GSX suggests everything is normal.
-
I found the problem, it was a bug in the Live Update, skipping all updates for the base Simobjects ( it only updater the PBR versions ). It should work now.
-
I found the problem, it was a bug in the Live Update, skipping all updates for the base Simobjects ( it only updater the PBR versions ). It should work now.
The MD5 hash is correct now and there is no more garbled text, but the distance readout is too high to see from the cockpit when getting close to parking spot.
-
Oh yeah. Now yes. Although the indications appear too high. Thanks.
-
The indication has been raised because it resulted sometimes in the indication being hidden by a building, that's why it caused the garbled fonts to be seen ( you always had "garbled" fonts, they were just underground ), since the actual font file required to be updated.
-
That makes the indication pretty useless since it can't be seen from the cockpit now. It seemed to me the indication was dependent on where the marshaller stood - if you moved the marshaller position the parking indication would also move. Anyway, is there a way to move it down where it can be seen from the cockpit?
-
if you moved the marshaller position the parking indication would also move.
Yes, but if the terminal has a structure that protrudes over the marshaller, the numbers might have been inside the building.
Anyway, is there a way to move it down where it can be seen from the cockpit?
Nothing you can change by yourself, we'll see to lower it a bit.
-
Great! have been treated. PBB still freezes in a mysterious direction.Thank you for your continued support! ;D
-
Great! have been treated. PBB still freezes in a mysterious direction.Thank you for your continued support!
That issue is not something new, and can usually fixed by uninstalling and reinstalling SODE.
-
Try the Live Update again, it should be fixed now.
Hello Umberto. Updated, restarted and tested. Same results. Duplicated loaders and baggage carts and KATL's gates cut in half.
:'(
-
Hello Umberto. Updated, restarted and tested. Same results. Duplicated loaders and baggage carts and KATL's gates cut in half.
Please clarify if you are referring to the SODE jetway not animated correctly, or you are reporting a new problem.
If you are reporting a new problem, please clarify it better, because it's not very clear what "KATL's gates cut in half" really means, and I can't see any duplicated loaders so, please, provide reproductions steps, possibly on an airport that is either default or one of ours.
-
Hello Umberto, all jetways works fine.
KATL was developed by Imaginesim. Before the update, all 40 gates at Terminal D were working fine with GSX. Not just Terminal D but all Terminal gates worked fine. After the update, it cut from 40 gates down to maybe 10 or 12 gates.
Regarding the loaders and baggage vehicle, every time when I command for my CRJ-200, 2 loaders and 2 baggages carts showed up, before the update, only one loader and one baggage cart showed up. After the update, it kept bringing 2 loaders and 2 baggages.
-
There isn't any CRJ-200 in the GSX internal database, which means nothing in the update could possible have affected the number of loaders on a particular aircraft, it's the airplane configuration that controls that and, being an unsupported airplane, you must have using your own configuration, so you can specify, as usual, which doors gets which loaders and which doors will be disabled.
-
BEFORE the update, it worked PERFECTLY with my CRJ-200. After your MESS UP update, I can't get rid of duplicated loaders. I tried with the aircraft configuration a numerous of times to ensure that the other unused is disabled, still it kept loading duplicated loaders.
-
Please clarify which CRJ-200 you are referring to, and post your custom profile for it.
-
Please clarify which CRJ-200 you are referring to, and post your custom profile for it.
Greetings Umberto!
I finally figured why it kept bringing duplicated loaders and carts, there is another cargo on left side of my CR2 that I overlooked. I did not change the settings, I guess when doing an update it changed without my acknowledge but I changed back to No service. It is working now.
Attached is a picture of so many gates missing at KATL. Those gates at Terminal D, 3 to 9, 12 to 21, 22, 23, 25, 26, 27, 29 to 31 and 35 to 40 did work before the update. Now I am unable to use those gates that the GSX won't recognize when I land/take off.
How can I bring ALL gates back to work again?
Lastly, re-fueling is still not doing an animate, are you still working on it?
Thanks. :D
-
It would be helpful to check your airport profile for KATL.
-
Please remember I'm not an expert with technician, how or where can I find "profile"?
-
If you have one, it's a file named KATL-xxxxxx.INI in the %APPDATA%\Virtuali\GSX folder.
-
Attached
-
Attached
I see you have two .INI files, one made for this .BGL
KATL_ADEX_ADE_med.bgl
the other one made for this one:
KATL_ADEX_ADE_hi.bgl
Which one you use ?
-
I have NO clue, again as I mentioned before I know NOTHING about the system, how it works, how files works. I am totally lost.
-
I have NO clue, again as I mentioned before I know NOTHING about the system, how it works, how files works. I am totally lost.
The GSX airport customization page will tell you which .BGL has been loaded.
But that's besides the point, the point is that scenery has two alternate .BGLs for some reason, which should be known to you, as a user of that scenery so, even without GSX, you should at least know how you configured that scenery.
-
Landed at KJFK yesterday afternoon and noticed all jetways sank. I re-corrected by clicking "elevation to the aircraft" and fixed but this morning I landed JFK and see duplicated jetways.
Problems, problems, one after another.
MESS update!!!!!
I will fly back to KATL today and will screenshot where bgl is and hope you can resolve those problems.
-
I have NO clue, again as I mentioned before I know NOTHING about the system, how it works, how files works. I am totally lost.
The GSX airport customization page will tell you which .BGL has been loaded.
But that's besides the point, the point is that scenery has two alternate .BGLs for some reason, which should be known to you, as a user of that scenery so, even without GSX, you should at least know how you configured that scenery.
Finally back to KATL and here is a picture you asked for about .bgl location.
-
Now it's 4 days and am still waiting for you to fix KATL and KJFK.
-
Now it's 4 days and am still waiting for you to fix KATL and KJFK.
It hasn't been "4 days", it has been only 1 working day since you last posted, and you can't expect a fix for anything in only one working day.
-
15 days and still can't use GSX............................