Products Support > GSX Support FSX/P3D
This Post is directed to Umberto
kmanning:
Umberto,
I hope you can explain why I'm having these problems. I've been contended with this problem for almost a week, and I'm getting very irritated. I thought you would be the best person to come to with some help and prefer that you help me with this issue if you can. If it's something outside your knowledge, I guess I'll just have to wait until the GSX Update is completed. I don't have any problems in FSX and everything works fine. But in P3Dv4, here's the problem I'm having:
After loading my plane at KSFO gate F82, which is a Flightbeam product, and launching the GSX Parking Facility to dock the jetway, there are no selections for any of facilities normally found in GSX. It only shows 9 items. Items 1 through 8 shows runway start positions and item 9 says 0 suitable parkings, as though there are no parking positions at this airport. See my screenshot in the attachment below. As you can see, there are parking and jetways available at this airport. I've tried everything that I know of to fix this problem.
Another thing that I've noticed is that after running the Live Update and I launch FSX, it prompts me to run the Security Warning, either selecting "Run" or "Don't Run." But when I launch P3Dv4, it does not prompt me to select the Security Warnings as it use to. Everything works fine in FSX. All of my problems are in P3D and I don't understand why I'm having this problem all of a sudden. I've already tried deleting the .ini files in the C:\Users\Admin\AppData\Roman\Virtuali\GSX that relate to KSFO and it made no difference. I would send you a log.report but I don't see a file named log.report. The only file I see that's in the Viruali folder is a file named Couatl.err. I'll post that below but I'm not sure if this is what you need to help you determine what the problem is. If you need the log.report, where is it so that I can send it to you. I hope you can help me with this so that I can continue to use the GSX and all of its features.
Ken.
FOD:
Ken,
Not Umberto but you can often find a solution on the forums.
In this case also try REM out the ini files in the airfield/scenery folder ie change the file from xxx.ini to (say) xxx.bak
Worked for me with several problem airfields.
John R
kmanning:
--- Quote from: FOD on September 03, 2022, 12:53:15 pm ---Ken,
Not Umberto but you can often find a solution on the forums.
In this case also try REM out the ini files in the airfield/scenery folder ie change the file from xxx.ini to (say) xxx.bak
Worked for me with several problem airfields.
John R
--- End quote ---
I've already been to all of these forums. Although it may provide a solution, this is something that should not have to be done to artificially fix another program. I've read in one of the posts that all of these issues have been going on for 2 or 3 weeks, if not longer. The problem is that when this is finally fixed, if that ever happens, one forgets to rename the file extension back to it's original name, or may even forget what the original extension was. When you change the extension of an .ini file, it is no longer a configuration file for that program, and could cause problems later, especially if one forgets to rename the file back to it's original .ini extension if this happens to take several more weeks or months. I'm sure this problem was caused by one of the updates because the fact remains that everything was working just fine until just recently. By the way, what is REM? I do not see anything in that airport scenery folder that says REM.
Ken.
kmanning:
Umberto,
I've just uploaded my GSX Log Report. It's in my original post in the attachments above.
Ray Proudfoot:
--- Quote from: kmanning on September 03, 2022, 05:58:28 pm ---By the way, what is REM? I do not see anything in that airport scenery folder that says REM.
Ken.
--- End quote ---
It's programmer speak for a remark. In short an aide-memoir to the coder as to the purpose of that line or section of code. Because it shouldn't be read by the program it is commented out using a \\ or ; depending on the program in use.
Navigation
[0] Message Index
[#] Next page
Go to full version