• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

CameraDefinition (views)

Messages
100
Country
unitedkingdom
Looking for some help with Cameraviews and how are they set up.

Do you need extra software to set these up.

Is it possible to set views up about 1nm away from the aircraft.

Reason being that on FSInn server the peer2peer has a lag of around 1nm-1.5nm difference.
With AAR the refuelling aircraft is that far behind the tanker.
If set up of two new cameras looking back from each wing/hose 1nm-1.5nm away from the tanker you would see the incoming aircraft better/closer.

As always any help always appreciated.
 
I hate to say this, but the SDK has some great information on adjusting the camera settings. They did good on that little area of the sim.

When I adjust the camera settings, I just jump in and start experimenting on them. I copy/paste a similar camera angle from another plane and rename it what it needs to be and then start changing the zoom, angles, adjustability, etc, etc. It looks really sophisticated, but its not. Most of the settings you will not touch, mostly only the location from eye point, then angles and zoom percentage.

Do you have the SDK installed?
 
Yes SDK installed.

I did think of just using any camera and adding to appropiate files within my aircraft but wanted feed back first so not to mess thing up.

I will give this a try today,thankyou for your help.

regards

Paul
 
Hey Paul,

I know it isnt much help but at least a good direction.

Note that there are external views and internal views. I use stock FSX planes 'camera views' as templates and go from there. If I want a panel shot (like the radio stack or an odd cockpit view angle) I use a similar one from a plane's camera view that is similar. I then adjust the axis, zoom, and angles.

Here is a sample;

[CameraDefinition.001]
Title = "Right Seat" <--- NAME OF VIEW
Guid = {195EAB58-9E4A-1E2A-A34C-A8D9D948F078}
Origin = Virtual Cockpit <--- INTERNAL OR EXTERNAL
MomentumEffect = Yes
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.75 <<---- ZOOM SETTING, IMPORTANT
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit <<---- INTERNAL VIEW
PitchPanRate=20
HeadingPanRate=60
InitialXyz=0.6, 0.03, -0.1 <<---- LOCATION FROM EYE POINT
InitialPbh=0, 0, 0 <<---- ANGLES IN DEGREES, 0-360


Those are some of the basics, almost all that you need as the rest is preset. You can do some cool angles and shots, like a belly cam, rudder view point, passenger seat in the tail, engine cowling looking at the engine if you have a cowling that raises, etc, etc.
 
Though I don't think it'll break the simulator if you don't, it's still good practice to change the GUID. After all, it is a globally unique identifier.
 
Lionheart, that is a great explanation and will help tremendously,i will post my testing results,thanks again.

Ollyau,if you could explain how you change the GUID would also be a great help,or do you simple paste and copy a new one in.
I understand the reason for the GUID and i have GUIDGen installed but never had to change one before.

Great feed back guys thanks again.
 
Last edited:
Lionheart, that is a great explanation and will help tremendously,i will post my testing results,thanks again.

Roger that. Glad to be of help.


explain how you change the GUID would also be a great help,or do you simple paste and copy a new one in.

Yep, just generate a new one, copy/paste it in. I 'think' it isnt required as mine always work on modified versions, as the GUID is being used in the aircraft.cfg (where its being called upon) so that what plane you are flying in, that camera view will be active. I havent seen memory pulling other camera views out before, but it is good to be safe in case everything changes.


Bill
 
FWIW, I have a "standard set" of CameraDefinition.00x entries that
I copy into each of my aircraft.cfg files along with "HotKeySelect="
assignments that map them to the #2 hat on my X-45 stick.

The views are right seat, a foward view and a back view. I modify these
on a per-aircraft instance to suit that VC. In single seat aircraft the
views might be down and left, down and right and up over the cowl.

A two-seat aircraft might would be the right seat, perhaps the overhead
panel, and perhaps a central instrument panel view.

In my A2A Accu-Sim B-17G I have several additional view...upper
turret, bombardier position, tail gunner position and a bomb bay view.

I haven't bothered to change the GUID's from aircraft to aircraft. I
do believe I just changed those mwithin a given aircraft if I did a
copy/paste of an existing view in that aircraft and created a new view.
I just change one or two of the values in the existing GUID rather than
generate an entirely new GUID. Of course this if for my own use and not
for distribution. In the case of distribution, generating a new GUID
makes sense I suppose.

Paul
 
Thanks Paul! I never knew one could assign hot keys to these. I'll have to check that out.



Bill
 
CameraViews.jpg


Not sure if this will help others but made for a diagram for future reference.All this diagram shows is how to move camera view/direction and camera fix/position point.

Moved wing cameras on the aircraft to see the hoses when extended.Still got to online test so pictures to follow.

I was curious if two external views can be seen in the same window as one view.
I have a left and right hose view could they be put together so you can see both in one view at same time to see two aircraft refuelling.

Feed back has been excellent thank you all.

regards

Paul
 
Just a quick note on my attempt to move the cameras as far back as 1-1.5nm from the aircraft.

InitialXyz=-15.318, -1.183, -450.00
InitialPbh=5, 0, 180

-450 seemed to be the very max which i think relates to 450 meters before strange things starting happening and the camera was US.

Thanks guys for all your quick replies been very helpful.
 
Hey Paul, you have given me a bunch of ideas which I always had in mind to do with some VCs but did not know where to start!!...Thanks.:)
 
Back
Top