By Thimo Koolen 1345135
#503413
Bjoern Helge Smaavollan 1055999 wrote:
Thimo Koolen 1345135 wrote:I didn't had problems with model matching, but with the position. Is it possible to move the camera up to be placed above the tower roof?


You can press Ctrl+enter, shift+enter, Ctrl+backspace and shift+backspace to move your "Seat" up, down, back or forward. Same as in any cockpit.

But isn't the point with this feature to simulate a tower view? :p


The tower has like 4 different positions and there are a lot of buildings in the way that would obstruct the virtual tower view. If my camera's placed above, I can just easily rotate and view the field.
By Andrew Morkunas 1017951
#503432 Defining camera views: There are numerous ways to place the camera but I prefer to modify a aircraft.cfg file directly so as to place the camera at the exact tower location in the real world. You can use any aircraft you like and park it anywhere on the airport. Below are the camera definitions I use for KEWR, KLGA, KJFK, and KPHL with an altitude of 100 meters for the tower views. The only thing you need to modify for your own use is to increment the CameraDefinition.x, a new Guid https://www.guidgenerator.com/, latitude, longitude, and the initial camera heading in the InitialPbh line (pitch,bank, heading). More information on configuring fixed cameras may be found at http://www.fstipsandaddons.com/tutorials/understanding-fsx-cameras.html

Code: Select all[CameraDefinition.3]
Title = "JFK Tower"
Guid = {2900F626-8C26-4154-8FDC-E4346177C404}
Origin = Fixed
ShowPanel = No
SnapPbhAdjust = Swivel
PanPbhAdjust = Swivel
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = .75
SmoothZoomTime = 0
ShowWeather = Yes
InitialPbh=0, 0, 130
XyzAdjust = True
XyzRate= 10
xyzAccelleratorTime = 0
Panacceleratortime   = 0
PitchPanRate = 60
HeadingPanRate = 100
AllowPbhAdjust = Yes
ShowLensFlare= Yes
Category = Custom
ClipMode=Normal
CycleHidden=Yes
FixedLatitude=n40.642422
FixedLongitude=w73.781226
FixedAltitude=100

[CameraDefinition.4]
Title = "PHL Tower"
Guid = {cd04bb56-f88b-4a21-893d-1e55c37c820b}
Origin = Fixed
ShowPanel = No
SnapPbhAdjust = Swivel
PanPbhAdjust = Swivel
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = .75
SmoothZoomTime = 0
ShowWeather = Yes
InitialPbh=0, 0, 170
XyzAdjust = True
XyzRate= 10
xyzAccelleratorTime = 0
Panacceleratortime = 0
PitchPanRate = 60
HeadingPanRate = 100
AllowPbhAdjust = Yes
ShowLensFlare= Yes
Category = Custom
ClipMode=Normal
CycleHidden=Yes
FixedLatitude=n39.875656
FixedLongitude=w75.245892
FixedAltitude=100

[CameraDefinition.5]
Title = "PHL 27L"
Guid = {e0c79533-a1a5-480f-ab94-383e22fef8c9}
Origin = Fixed
ShowPanel = No
SnapPbhAdjust = Swivel
PanPbhAdjust = Swivel
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = .75
SmoothZoomTime = 0
ShowWeather = Yes
InitialPbh=0, 0, 300
XyzAdjust = True
XyzRate= 10
xyzAccelleratorTime = 0
Panacceleratortime = 0
PitchPanRate = 60
HeadingPanRate = 100
AllowPbhAdjust = Yes
ShowLensFlare= Yes
Category = Custom
ClipMode=Normal
CycleHidden=Yes
FixedLatitude=n39.866714
FixedLongitude=w75.233173
FixedAltitude=50

[CameraDefinition.6]
Title = "PHL 9R"
Guid = {7e8f025b-829f-4fd1-9121-ed3a281c1ba0}
Origin = Fixed
ShowPanel = No
SnapPbhAdjust = Swivel
PanPbhAdjust = Swivel
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = .75
SmoothZoomTime = 0
ShowWeather = Yes
InitialPbh=0, 0, 300
XyzAdjust = True
XyzRate= 10
xyzAccelleratorTime = 0
Panacceleratortime = 0
PitchPanRate = 60
HeadingPanRate = 100
AllowPbhAdjust = Yes
ShowLensFlare= Yes
Category = Custom
ClipMode=Normal
CycleHidden=Yes
FixedLatitude=n39.860001
FixedLongitude=w75.263926
FixedAltitude=50

[CameraDefinition.7]
Title = "EWR Tower"
Guid = {b522864c-875b-4380-94f2-adb3093f41dd}
Origin = Fixed
ShowPanel = No
SnapPbhAdjust = Swivel
PanPbhAdjust = Swivel
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = .75
SmoothZoomTime = 0
ShowWeather = Yes
InitialPbh=0, 0, 130
XyzAdjust = True
XyzRate= 10
xyzAccelleratorTime = 0
Panacceleratortime = 0
PitchPanRate = 60
HeadingPanRate = 100
AllowPbhAdjust = Yes
ShowLensFlare= Yes
Category = Custom
ClipMode=Normal
CycleHidden=Yes
FixedLatitude=n40.692573
FixedLongitude=w74.182749
FixedAltitude=100

[CameraDefinition.8]
Title = "LGA Tower"
Guid = {ab50b563-036d-4960-96fe-9ef33f2b7f58}
Origin = Fixed
ShowPanel = No
SnapPbhAdjust = Swivel
PanPbhAdjust = Swivel
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = .75
SmoothZoomTime = 0
ShowWeather = Yes
InitialPbh=10 , 0, 350
XyzAdjust = True
XyzRate= 10
xyzAccelleratorTime = 0
Panacceleratortime = 0
PitchPanRate = 60
HeadingPanRate = 100
AllowPbhAdjust = Yes
ShowLensFlare= Yes
Category = Custom
ClipMode=Normal
CycleHidden=Yes
FixedLatitude=n40.775515
FixedLongitude=w73.874495
FixedAltitude=100
By Ross Carlson 887155
#503437
Thimo Koolen 1345135 wrote:Thanks! And others won't be able to see your plane once connected?


As long as you connect vPilot to ES using the .towerview command, then your flight sim will not be connected to VATSIM. It will only be connected to ES. ES acts as a server for vPilot, essentially creating your own private network with ES as the server, and vPilot as the only user. ES takes care of copying the location of all aircraft from the live network to the private network it creates for you.
By Tony Manolo 1323805
#503499
Ross Carlson 887155 wrote:Can you provide a screenshot that shows a B737 that is not resulting in a model match?


Ok I haven't been able to get one of a B737 because lately the 737 has been matching up correctly. I guess it depends on the airline selected. But here is one of an Air Canada 777 showing up as Canadian Xpress 777.

Here is the info shot.
Image

And here is the actual aircraft
Image
By Ross Carlson 887155
#503506 vPilot determines which model to use based on the airline code that is specified in the atc_parking_codes line. So the problem is that you have a model that advertises itself as Air Canada but is actually for Canadian Express. The aircraft config file should probably only state CXA, so that it would only match CXA flights, not ACA flights.
By Tony Manolo 1323805
#503507
Ross Carlson 887155 wrote:vPilot determines which model to use based on the airline code that is specified in the atc_parking_codes line. So the problem is that you have a model that advertises itself as Air Canada but is actually for Canadian Express. The aircraft config file should probably only state CXA, so that it would only match CXA flights, not ACA flights.


But both Air Canada and Canadian Xpress use the 777. And, I'm sure UT2 also has Air Canada models in its database. So why isn't vpilot matching the aircraft up with the 777 in UT2. This didn't happen before in previous versions of vpilot. Why doesn't this happen with other Air Canada models like the A320 or the 767. For those aircrafts it shows the Air Canada livery. Why won't it show the AC livery for the triple 7? It makes absolutely no sense to me.

Tony Manolo
By Ross Carlson 887155
#503508 It used the CXA 777 model instead of the UT2 777 model because you have the CXA folder set higher in your priority list than the UT2 folder.

The core of the problem is that you have a 777 model with a CXA paint job, but the aircraft.cfg advertises itself as an ACA paint job. The model is lying. :)

In version 1, it didn't happen this way because vPilot didn't scan the aircraft.cfg files. It relied solely on the downloaded .VMR files. And either the CXA .VMR file correctly advertised the 777 model as CXA and not ACA, or you had the UT2 .VMR file set to a higher priority than the CXA .VMR file.
By Tony Manolo 1323805
#503509
Ross Carlson 887155 wrote:It used the CXA 777 model instead of the UT2 777 model because you have the CXA folder set higher in your priority list than the UT2 folder.

The core of the problem is that you have a 777 model with a CXA paint job, but the aircraft.cfg advertises itself as an ACA paint job. The model is lying. :)

In version 1, it didn't happen this way because vPilot didn't scan the aircraft.cfg files. It relied solely on the downloaded .VMR files. And either the CXA .VMR file correctly advertised the 777 model as CXA and not ACA, or you had the UT2 .VMR file set to a higher priority than the CXA .VMR file.


So, if I put UT2 above CXA in the priority list, then all Air Canada 777s will display correctly? And, if I do that, would a CXA 777 display the CXA livery or would the same problem occur in reverse where the CXA 777 will show up as an Air Canada 777?

Tony Manolo
By Ross Carlson 887155
#503510 Yes, putting UT2 higher in priority will make vPilot use the UT2 ACA 777 before it will use the (incorrectly configured) CXA 777.

The reverse problem should not happen because I assume the UT2 ACA 777 does not have the same misconfiguration. That is to say, I assume it does not list CXA as the airline code for its ACA 777.

Whether or not the CXA model will get used for a CXA flight depends on whether or not CXA is included in the list of airline codes in the atc_parking_codes entry of the aircraft.cfg file. If it is, it will.

Really, CXA needs to fix their model. Then it wouldn't matter what priority order you set for the folders, since vPilot would never try to use the CXA 777 for an ACA flight.
By Tony Manolo 1323805
#503511
Ross Carlson 887155 wrote:Yes, putting UT2 higher in priority will make vPilot use the UT2 ACA 777 before it will use the (incorrectly configured) CXA 777.

The reverse problem should not happen because I assume the UT2 ACA 777 does not have the same misconfiguration. That is to say, I assume it does not list CXA as the airline code for its ACA 777.

Whether or not the CXA model will get used for a CXA flight depends on whether or not CXA is included in the list of airline codes in the atc_parking_codes entry of the aircraft.cfg file. If it is, it will.

Really, CXA needs to fix their model. Then it wouldn't matter what priority order you set for the folders, since vPilot would never try to use the CXA 777 for an ACA flight.


Ok I'll point the CXA staff to this thread and hopefully they'll decide to do something about it. Thanks for your help.

Tony Monolo