• 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.

P3D v3 Cockpit Sensor/Camera Views - PBH, Tracking, Linking

MIL-STD

MIL-STD

Messages
19
Country
unitedkingdom
Hello all (long time reader, first time poster),

I've been experimenting recently with the camera configuration options afforded by Prepar3D for a VC I'm developing, and there are just a few questions left where some input would be useful (I know this question isn't entirely gauge focused, but this forum would seem the best fit, given it comes out of cockpit development).

1) Camera PBH limits - is there a way, within the confines of the .cfg, to restrict the available degrees of freedom of camera movement around a single origin point? Say, in the case of a cockpit view, when I pan with the mouse, I can only go 90* L/R, rather than the 180* that is the default absolute.

2) Camera Track - Is there any way, again using the native .cfg parameters, of having a camera, once panned, track a specific position in space (say, an arbitrary point on the ground), so as to simulate a tracking sensor view? I know there are ways of getting the camera to ignore PBH shifts caused by the user aircraft, but nothing about following a specific, arbitrary track (or is a gauge driven solution a necessity here?)

3) Camera Linking - If I understand the SDK correctly, there is a parameter to link two camera views together, so that movement in one shifts the other. Whenever I do this, however, selecting one or the other linked view simply causes the view in Prepar3D (3.4) to freeze entirely. Anyone had any luck with this?

Many thanks!
 
Last edited:
1 and 2 require gauge control using the PDK so no not with the cfg although I could be wrong on 1.

3: Never tried that myself so can't say for sure.
 
Many thanks Naruto, that is exactly what I suspected with 1 & 2. 3 remains a mystery (a bug?) so will have to head over to the P3D forums to see if I can get an answer from LM.

On a related aside, is there any recommended documentation/useful threads on developing just such a camera control gauge out there? The SDK documentation I've encountered is a bit, well, abstract, and such a gauge would represent an entirely new vector for me - (I note that the new V4 SDK has a 'controllable camera' entry, but, again, it seems to be at a fairly high level).
 
Not yet. I have done some PDK work with cameras but for a totally different purpose (A-G radar maps) and I never spent much time actually trying to control the camera. Always left it in a default position for my tests. If I do something like that I might look at releasing a PDK tutorial provided the work is simple.
 
Thank you very much again - Interestingly, one of the reasons why I've been exploring the camera system is for a fairly similar purpose, to create an A/G Radar 'patch map' capability (which could be emulated, albeit rather crudely, with a snapshot of a specific lat/lon area, with suitable post-processing. At this stage, I'd be happy with just that, before getting into the more daunting field of gdata decoding and projection correction).

A lot of the key structures are potentially there already, as demonstrated by the existing Radar Service, but the latter has embedded animation/colourization properties that I have yet to find a way of modifying/switching off, hence the desire for a 'clean sheet' approach. You will have a grateful reader here, if you ever have the chance to put out a PDK tutorial.
 
Last edited:
You must log in or register to reply here.
Back
Top