Thanks, you are right. I stand corrected on the Asobo Cessnas. I’ll edit my previous comment accordingly.
1 Like
If I remember right, when I was a pilot years ago doing pattern work, I didn’t even use the window. I used the part of the windshield that bent 90 degrees. Maybe I just had my seat too close to the instrument panel, but I used that little space as a left window.
This “issue” give me the opportunity to ask you about “POV/FOV” in this FS2020: seems there are the options to “move forward/backward” and to “zoom in/zoom out” the cockpit views. But.. it seems that both options do the same: they only change FOV! Is there the possibility to adjust distance from cockpit moving forward or backward only the seat without change the FOV? In this Carenado 182, probably change only the seat position (fw, bk, up, down) without change FOV would resolve the problem!
Not exactly. Moving f/b is done parallel to the aircraft Y axis. Zooming in/out moves the camera in the direction it is currently pointing in. This way you can zoom in to a particular instrument.
The way I do it :
- right-click mouse left to turn your head 90° to look at the side window
- use the Right keyboard key to move closer to the instrument panel
- right-click mouse drag right to turn your head 90° back to front.
I have recorded many preset views (Ctrl+Alt+1 to 9) for each plane, to recall with Alt+number on my controller (a MIDI one in fact, thanks to FreePIE and VJoy) for quick changes :
- forward, wide view over cowling (with the technique described above to get my “head” up to the instruments and then wide POV)
- forward, far view over cowling (“head” back to the headrest, then small POV)
- close-up on PFD (or left half of panel) for knob tweaking
- close-up on MFD (or right half of panel)
- left-rear view to check the airfield before entering base
Etc …
Have you gotten this to work? I’m only just now trying it in 1.9.5, and it will not read my cameras.cfg file for the Savage Cub repaint I’m doing. The sim will react to changes to the cameras.cfg file in the main directory, but completely ignores my file in my repaint in the Community directory.
Any idea why? Does it have to do with cached files?
Eek, if you were downwind and using the little bend in the window to see the runway to your left or right, you were leaning over the control column 
We’re not talking about turning to final, we’re talking about flying downwind and looking out the side window.
It’s likely, for the purposes of the general public, the dimensions of the wings have been change to appease those among us who have not flown and want to see the wing when they look out the window. It might also give a user a more “Normal” perspective seeing the wing there.
Yes, the real solution to what everyone here is talking about is changing the “eyepoint=” and Pbhxyz parameters in the cameras.cfg. As noted about, however, the one I’m using in the Community directory in my repaint is being ignored by the software even though it’s in the layout.json.
Then your aircraft definition in the community folder must be incomplete/invalid in some way. In such a situation the simulator rejects it entirely and takes the default files. Your camera.cfg may be still valid, while something else is broken there.
Well, that can’t be so, the livery works great, it’s reading the changes I’ve made to the aircraft.cfg (I removed the copilot and other changes), the flight_model.cfg (I added more load stations) and the panel.cfg (I erased the Registration number on the outside) files just fine. It’s only the cameras.cfg file that’s not having any effect on my model.
There are two things I’m doing in the cameras.cfg file 1. raising the eyepoint a bit, 2. I added a CoPilot camera. Both the changes work just fine if I edit the cameras.cfg file in the default plane directory. I’m trying to use the exact same file in my livery aircrft directory, but it’s ignoring it. I’m assuming it’s either a bug, or there is a dependency I’m missing.
Here’s my Manifest.json
{
“dependencies”: ,
“content_type”: “Asobo-aircraft-savage-cub”,
“title”: “Rosie the Rocketer”,
“manufacturer”: “Zlin Aviation”,
“creator”: “FlyingsCool - Marcel Ritzema”,
“package_version”: “0.1.0”,
“minimum_game_version”: “1.7.12”,
“release_notes”: {
“neutral”: {
“LastUpdate”: “”,
“OlderHistory”: “”
}
}
}
Here’s an excerpt of my Layout.json (which works just fine for the rest of the files)
{ "content": [ { "path": "SimObjects/Airplanes/Rosie/aircraft.cfg", "size": 2143, "date": 1601049098605 }, { "path": "SimObjects/Airplanes/Rosie/cameras.cfg", "size": 2143, "date": 1601049098605 }, { "path": "SimObjects/Airplanes/Rosie/panel.Rosie/PANEL.CFG", "size": 767, "date": 1600438365950 }, { "path": "SimObjects/Airplanes/Rosie/texture.Rosie/SAVAGE_CUB_AIRFRAME_FUSELAGE_ALBD.PNG.DDS", "size": 2097280, "date": 1601033605292 }, { "path": "SimObjects/Airplanes/Rosie/texture.Rosie/SAVAGE_CUB_AIRFRAME_FUSELAGE_ALBD.PNG.DDS.json", "size": 102, "date": 1598003522919 }, { "path": "SimObjects/Airplanes/Rosie/texture.Rosie/SAVAGE_CUB_AIRFRAME_LANDING_GEARS_ALBD.PNG.DDS", "size": 4194432, "date": 1600888321584 }, { ....
Here’s the plane in the game 
Try to use copied original cameras.cfg with just modified a single parameter, e.g. a pilot’s camera height (to be sure it takes any effect). If it doesn’t work, then the problem lies outside the camera.cfg file.
I use modified cameras.cfg files in my community folder of all aircraft just to set the desired default pilot’s head position, and they work great.
Good idea. I just tried it and it didn’t work. Like you, I changed the eyepoint vertical position from 0.7 to 1.2 feet.
When you said it, I realized, too, that I had two other liveries in my Community for the plane, a Mega-pack with a different manifest configuration, and another single livery with a pretty much duplicate configuration and manifest file. (the mega-pack has a dependency on the savage cub, mine does not as seen above). It occurred to me maybe something they are doing is interfering with my model.
So I removed them from the Community folder. No effect, still doesn’t work. And modifying the default cameras.cfg the same does work.
do you mind posting how you installed your cameras.cfg files? Maybe I need to do it separately and not as a part of my livery?
This is my directory structure…
In D:\FS2020\Community\liveries-savagecub-flyingscool-rosie\SimObjects\Airplanes
is
> \Rosie
> |___\Panel.Rosie
> |_____Panel.cfg
> |___\texture.Rosie
> |___(all the texture files, thumbnail)
> |___aircraft.cfg
> |___cameras.cfg
> |___flight_model.cfg
As I said, everything is working except for the cameras.cfg
You can see my manifest.json and Layout.json above
This is my “mod” of C152:
Directory of C:\Users…\Community\myC152
22.08.2020 14:04 1 791 de-DE.locPak
22.08.2020 14:04 1 369 en-US.locPak
22.08.2020 14:04 1 474 es-ES.locPak
22.08.2020 14:04 1 542 fr-FR.locPak
22.08.2020 14:04 1 574 it-IT.locPak
02.10.2020 19:20 917 layout.json
16.09.2020 20:33 460 manifest.json
22.08.2020 14:04 1 479 pl-PL.locPak
22.08.2020 14:04 1 522 pt-BR.locPak
22.08.2020 14:04 2 510 ru-RU.locPak
11.09.2020 18:00 SimObjects
layout.json is shortened to this content:
{
“content”: [
{
“path”: “de-DE.locPak”,
“size”: 1791,
“date”: 132408489797491080
},
< next 7 *.locPak file declarations here>
{
“path”: “SimObjects/Airplanes/Asobo_C152/cameras.cfg”,
“size”: 19006,
“date”: 132381778860000000
}
]
}
and cameras.cfg is placed in \Community\myC152\SimObjects\Airplanes\Asobo_C152\cameras.cfg
It is a copy of the original file with the modification of 2 lines:
InitialXyz = 0.05, 0.125, -0.8 (pilot’s head moved up)
InitialPbh = -4.5, 0, 0 (pilot’s head tilted down)
in the section [CAMERADEFINITION.0]
Great! Thanks, I’ll try that in a little bit.
What does your manifest look like? Any dependencies?
manifest is just a copy without any modifications. All I wanted so far is just adjustment of pilot’s head default position. I use all default aircraft without modes or additional liveries. The only exception is a livery set for A320, but I haven’t modified cameras.cfg for this plane yet.
Just a copy of the default manifest?
That might explain the difference. I am not calling out a dependency to the propdefs
Success!!!
Your solution worked!
Adding propdefs to the manifest in my livery did not work, but your solution did!
Thanks so much!
1 Like
Doesn’t seem to work for Premium aircraft, tho. Just tried it with the Shock Ultra, and no go. No big deal, I’ll study up on the differences in creating liveries for Premium aircraft to see if I can see what the difference is.
You would think they would fix that, it was that way in P3D so suspect that will never happen. Its a odd company, they release a aircraft once and updates are rare. I got a lot of there aircraft, and most are still version 1.x, one is 2x. They do reply in support, not sure if it means anything.
I do like there planes and most work, but when I get a dud, I just toss it as a lost.
I set custom camera position, one to sit above the panel, and 2 for side window views.
Problem is especially for trackir users..