I have just started using Smartstarter. Everything installed OK and I have followed the setup instructions.
After choosing my aircraft, time,airport and Panel state, I click on "Set Scenario" and choose the correct scenario in P3d, my plane is placed at Lat 0 and Long 0.
I have tried with different airports as location but always the same result.
Any ideas?
Plane always placed at LAT 0 LON 0 [SOLVED]
Plane always placed at LAT 0 LON 0 [SOLVED]
Last edited by gblair on Mon Jul 02, 2018 6:48 am, edited 1 time in total.
Re: Plane always placed at LAT 0 LON )
pls send the text of your scenario file (*.fxml) so I can have a look at it
Re: Plane always placed at LAT 0 LON 0
I got the fxml files, Delta 737.fxml as used as the default setup and SAA 737NGX.fxml which you say was created by SMartStarter.
I loaded your Delta 737.fxml to my ..Documents/Prepar3dV4 folder and used it in SmartStarter and it works just fine.
The SmartStarter created "new" fxml file that is used in the Scenario Load should still have the same Delta 737.fxml file name.
I do not understand where you get the SAA 737NGX name from?
Do you have an EGLL airport add-on scenery installed?
If yes, did you install the Lorby-SI AddonOrganizer before running SmartStarter?
I loaded your Delta 737.fxml to my ..Documents/Prepar3dV4 folder and used it in SmartStarter and it works just fine.
The SmartStarter created "new" fxml file that is used in the Scenario Load should still have the same Delta 737.fxml file name.
I do not understand where you get the SAA 737NGX name from?
Do you have an EGLL airport add-on scenery installed?
If yes, did you install the Lorby-SI AddonOrganizer before running SmartStarter?
- Attachments
-
- Desktop Screenshot 2018.07.02 - 13.44.54.02.png (860.59 KiB) Viewed 6672 times
Re: Plane always placed at LAT 0 LON 0
Hi Roar,
I decided to uninstall/delete and start from fresh. I also deleted the previous .fxml files so that there is no confusion.
I don't have any add on airports installed and have tried at different airports with the same results
I made a new startup scenario named Delta 737 LAX. I then used SmartStarter with the same aircraft, to set a new scenario at KSEA. The "New" scenario created by SmartStarter now has the same name at the original (Delta 737 LAX) but when I load that in P3D I have the correct aircraft but position is LAT 0 LON 0, not KSEA
The .fxml files are attached. I changed the original setup file name from Delta 737 LAX to Delta 737 LAX_orig manually so that you can see both
Regards
I decided to uninstall/delete and start from fresh. I also deleted the previous .fxml files so that there is no confusion.
I don't have any add on airports installed and have tried at different airports with the same results
I made a new startup scenario named Delta 737 LAX. I then used SmartStarter with the same aircraft, to set a new scenario at KSEA. The "New" scenario created by SmartStarter now has the same name at the original (Delta 737 LAX) but when I load that in P3D I have the correct aircraft but position is LAT 0 LON 0, not KSEA
The .fxml files are attached. I changed the original setup file name from Delta 737 LAX to Delta 737 LAX_orig manually so that you can see both
Regards
- Attachments
-
- Scenarios.zip
- (12.5 KiB) Downloaded 439 times
Re: Plane always placed at LAT 0 LON 0
I had a look at the fxml files now and see that the lat, lon, alt and hdg is not written to the SmartStarter created fxml file.
Can you zip me the g5.csv file and tell me the version number of the MakeRwys.exe ( They are both in the Prepar3D main folder)
Can you zip me the g5.csv file and tell me the version number of the MakeRwys.exe ( They are both in the Prepar3D main folder)
Re: Plane always placed at LAT 0 LON 0
The g5.csv file is attached.
MakeRwys version is 4.8.5.0
MakeRwys version is 4.8.5.0
Re: Plane always placed at LAT 0 LON 0
I don't see any attachement
Re: Plane always placed at LAT 0 LON 0
File is too big, I have emailed it to you
Re: Plane always placed at LAT 0 LON 0
Problem is now solved.
See last comments to find out :
mvr1918:
I believe your system has the decimal symbol set to “,” and not the default “.”
Try to change it to the default “.” In the Region & Language setup for Windows.
gblair:
That was the problem, thank you very much. I don’t remember ever changing this setting !!!
Sorry that you had to give up your time on this when it was not really a SmartStarter problem. Shall I reply on the forum or would you prefer to?
As a side comment, I have been using OC4BA since September 2015 in my 737-800 cockpit. It has made my home cockpit a pleasure to set up. I have just recently been adding on to it and got it to a stage where I think it is now complete for me (for now )
Thanks for the awesome programs and the support, much appreciated.
mvr1918:
Fine.
It could be that you never change the setting as it may be that South Africa uses “,” as the decimal symbol.
My system uses the “.”, so I never had any issues and never though that region settings could cause any problem.
Lesson learned and thanks for your patience. It is almost impossible to have any program code 100% without a lot of testing
from users with different settings.
I will, in a later release, change the code so it accept both symbols.
See last comments to find out :
mvr1918:
I believe your system has the decimal symbol set to “,” and not the default “.”
Try to change it to the default “.” In the Region & Language setup for Windows.
gblair:
That was the problem, thank you very much. I don’t remember ever changing this setting !!!
Sorry that you had to give up your time on this when it was not really a SmartStarter problem. Shall I reply on the forum or would you prefer to?
As a side comment, I have been using OC4BA since September 2015 in my 737-800 cockpit. It has made my home cockpit a pleasure to set up. I have just recently been adding on to it and got it to a stage where I think it is now complete for me (for now )
Thanks for the awesome programs and the support, much appreciated.
mvr1918:
Fine.
It could be that you never change the setting as it may be that South Africa uses “,” as the decimal symbol.
My system uses the “.”, so I never had any issues and never though that region settings could cause any problem.
Lesson learned and thanks for your patience. It is almost impossible to have any program code 100% without a lot of testing
from users with different settings.
I will, in a later release, change the code so it accept both symbols.