-
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 fs9view alternative in P3D ??
- Thread starter rcbarend
- Start date
- Messages
- 440
- Country
Hi Rob,
I have a tester that, at first, crashed his P3D. I'll have to check with him again but IIRC it works as long as P3D is not under a big load. Both FSX & P3D take a 50% frame hit when used.
I have a tester that, at first, crashed his P3D. I'll have to check with him again but IIRC it works as long as P3D is not under a big load. Both FSX & P3D take a 50% frame hit when used.
Hi Roman,
Thanks ...
I've been looking at other ways of doing it.
The camera system introduced in FSX, is the most obvious one of course; but from what I understand, there's no way to emulate the user interaction via the menu (at least in XML).
There's even no event to spawn a NewView; let alone select a specific camera defined in the aircraft.cfg for that a new view.
Rob
- Messages
- 542
- Country
Hi Rob
Have a look at the following link ,
http://www.fsdeveloper.com/forum/threads/v2-2-radar.429697/
It appears that LM used the fs9view function to implement their " Radar " .
I suspect that is the reason for the problems .
I have been told that my Pave Tack instrument ( fs9view based ) does not work properly in later versions of P3D , including CTD .
It is quite obvious that their radar is fs9view based , and that LM have probably changed the fs9view background code to effect the radar .
Cheers
Karol
Have a look at the following link ,
http://www.fsdeveloper.com/forum/threads/v2-2-radar.429697/
It appears that LM used the fs9view function to implement their " Radar " .
I suspect that is the reason for the problems .
I have been told that my Pave Tack instrument ( fs9view based ) does not work properly in later versions of P3D , including CTD .
It is quite obvious that their radar is fs9view based , and that LM have probably changed the fs9view background code to effect the radar .
Cheers
Karol
- Messages
- 542
- Country
Rob
I'm not sure about that .
LM are doing a good job of improving P3D and any bugs as they go .
They may well do work to restore the previous fs9view functions in the future .
This issue needs to be raised on the P3D forums to get a response from LM P3D programmers .
I do not have P3D installed nor have I got their SDK , so I can't experiment to get a workaround to make the camera gauge work in P3D .
Cheers
Karol
I'm not sure about that .
LM are doing a good job of improving P3D and any bugs as they go .
They may well do work to restore the previous fs9view functions in the future .
This issue needs to be raised on the P3D forums to get a response from LM P3D programmers .
I do not have P3D installed nor have I got their SDK , so I can't experiment to get a workaround to make the camera gauge work in P3D .
Cheers
Karol
- Messages
- 440
- Country
Deleted.... False info
Last edited:
I don't have P3D myself, but I'll ask one of the MV22B users to test it.
Thanks for the tip ... ...
Cheers, Rob
- Messages
- 440
- Country
Just FYI.. fs9view:view is in the P3Dv3 SDK in a well hidden, possibly orphaned document. (as are some others)
Guess it's time to get a developers version and give it a go.. Don't want a tester to be continually crashing.
Custom Vars - http://www.prepar3d.com/SDKv3/LearningCenter/utilities/variables/custom_variables.html
Possibly orphaned, many are not referenced anywhere else.. (folder) - http://www.prepar3d.com/SDKv3/LearningCenter/utilities/variables/
Guess it's time to get a developers version and give it a go.. Don't want a tester to be continually crashing.
Custom Vars - http://www.prepar3d.com/SDKv3/LearningCenter/utilities/variables/custom_variables.html
Possibly orphaned, many are not referenced anywhere else.. (folder) - http://www.prepar3d.com/SDKv3/LearningCenter/utilities/variables/
- Messages
- 542
- Country
Hi Roman
It's good that you are going to look further into this subject .
Please keep us informed of your findings .
Years ago I used the ESP SDK to create my Pave Tack instrument , as you probably know ESP is the original basis of the LM Prepar3D .
Following is from the ESP SDK ,
*************
************
From the above I presume the variables should be along the following lines ,
When I created the Pave Tack I used the following variable format eg; (L:OffsetForwardStep, number) .
This variable format might possibly be the reason for the problems being experienced now in P3D ,
perhaps I should have used (C:FS9VIEW:OffsetForward, number) .
The clue may be calling the Module name , in this instance FS9VIEW in the variable .
Cheers
Karol
PS
For ESP SDK ,
https://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjfx53P7IrTAhUX22MKHVdxCMQQFggZMAA&url=https://msdn.microsoft.com/en-au/library/cc526953.aspx&usg=AFQjCNHTFyedFVTuNgJbtP2nIxeRUSj9RQ
Scroll about one third down .
It's good that you are going to look further into this subject .
Please keep us informed of your findings .
Years ago I used the ESP SDK to create my Pave Tack instrument , as you probably know ESP is the original basis of the LM Prepar3D .
Following is from the ESP SDK ,
*************
Code:
FS9VIEW On bool Yes Turn an auxiliary view on or off.
FS9VIEW Zoom float Yes
FS9VIEW Pitch float Yes Pitch of the view in degrees.
FS9VIEW Bank float Yes
FS9VIEW Heading float Yes
FS9VIEW OffsetRight float Yes Offsets in meters from the normal viewpoint.
FS9VIEW OffsetUp float Yes
FS9VIEW OffsetForward float Yes
To use a custom variable, precede it with C:<module name>: , for example:
C:pOI:SelectedTargetNameFrom the above I presume the variables should be along the following lines ,
Code:
C:FS9VIEW:On
C:FS9VIEW:Zoom
C:FS9VIEW:Pitch
C:FS9VIEW:Bank
C:FS9VIEW:Heading
C:FS9VIEW:OffsetRight
C:FS9VIEW:OffsetUp
C:FS9VIEW:OffsetForwardThis variable format might possibly be the reason for the problems being experienced now in P3D ,
perhaps I should have used (C:FS9VIEW:OffsetForward, number) .
The clue may be calling the Module name , in this instance FS9VIEW in the variable .
Cheers
Karol
PS
For ESP SDK ,
https://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjfx53P7IrTAhUX22MKHVdxCMQQFggZMAA&url=https://msdn.microsoft.com/en-au/library/cc526953.aspx&usg=AFQjCNHTFyedFVTuNgJbtP2nIxeRUSj9RQ
Scroll about one third down .
Last edited:
As a sidenote, another (functional) problem I have with fs9view is this (and this is in FSX-Accel):
I'm trying to make a forward-looking fuel probe camera, positioned near the origin of the fuel probe.
But whatever I try, the probe visual part doesn't show (it's groundshadow does !)
The funny thing is, that if I change the view heading to outside the +45 to -45 degree sector (relative to the longitudinal axis), the probe shows up fine.
So I did a few more experiments, in several (even default) aircraft.
When I position the camera "inside" the visual model, the same thing happens: if the view heading is within the +45 to -45 sector, all aircraft (visual model part) disappear.
While the ground shadow is fine.
Rotating the camera to > 45 or < -45 degrees: the view is fine (I can see the model details as if viewed with the regular FSX camera view defined in the aircraft.cfg)
Always the same problem, in any aircraft I tried.
So this makes me wonder: would this "feature" be deliberately programmed in the fs9view module ??
Rob
I'm trying to make a forward-looking fuel probe camera, positioned near the origin of the fuel probe.
But whatever I try, the probe visual part doesn't show (it's groundshadow does !)
The funny thing is, that if I change the view heading to outside the +45 to -45 degree sector (relative to the longitudinal axis), the probe shows up fine.
So I did a few more experiments, in several (even default) aircraft.
When I position the camera "inside" the visual model, the same thing happens: if the view heading is within the +45 to -45 sector, all aircraft (visual model part) disappear.
While the ground shadow is fine.
Rotating the camera to > 45 or < -45 degrees: the view is fine (I can see the model details as if viewed with the regular FSX camera view defined in the aircraft.cfg)
Always the same problem, in any aircraft I tried.
So this makes me wonder: would this "feature" be deliberately programmed in the fs9view module ??
Rob
- Messages
- 542
- Country
I have not been able to find any documented references or information on FS9VIEW .
The only reference is the SDK detailed above , and the only application is in the Spirit of St Louis aircraft periscope .
I use it in the old Alphasim F-111 , in that aircraft the only part of the aircraft visible is the cockpit , interestingly all effects ,
exhaust , flares , lights , etc are visible to the instrument .
I tried it in the FSX native YF-23 and the skins are visible .
I suspected at the time a relationship to the " Preview Direct 10 " as it behaves in a similar manner with Older vs newer native (dds) aircraft textures .
Karol
The only reference is the SDK detailed above , and the only application is in the Spirit of St Louis aircraft periscope .
I use it in the old Alphasim F-111 , in that aircraft the only part of the aircraft visible is the cockpit , interestingly all effects ,
exhaust , flares , lights , etc are visible to the instrument .
I tried it in the FSX native YF-23 and the skins are visible .
I suspected at the time a relationship to the " Preview Direct 10 " as it behaves in a similar manner with Older vs newer native (dds) aircraft textures .
Karol
- Messages
- 440
- Country
Well... Just don't know. 
Installed the developers version (pro version w/ 30 day limit) and it worked right from the get go. Tried my hardest to make it fail without it ever happening.
Maybe the pro version is required? My tester has academic and he reconfirmed that it fails now.
Maybe a video card / P3D graphics setting? Inquiring minds want to know.
Just for kicks here is my relevant code -
Installed the developers version (pro version w/ 30 day limit) and it worked right from the get go. Tried my hardest to make it fail without it ever happening.
Maybe the pro version is required? My tester has academic and he reconfirmed that it fails now.
Maybe a video card / P3D graphics setting? Inquiring minds want to know.
Just for kicks here is my relevant code -
Code:
<Element Name="THE VIEW">
<Position X="124" Y="45"/>
<CustomDraw Name="fs9view:view" X="197" Y="197" Pitch="90" Bank="0" Heading="0" OffsetUp="@Up" OffsetForward="@Fwd" OffsetRight="@Right">
<On>1</On>
<Zoom>(L:Driftmeter_Zoom, number) 0.25 max</Zoom>
</CustomDraw>
</Element>
Roy Holmes
Resource contributor
- Messages
- 1,805
- Country
Rob,
When you are inside an unoccupied and unfinished part of the model are you not looking at the wrong side of the surface, one-sided polygons?
Roy
Hi Roy,
No.
When I set the heading to 44 degrees, all visual parts are gone ( so I only see the sceneny, and aircraft shadow); when I set it to 45 degrees (or higher) all parts I should see are suddenly visible.
Always the same, in any aircraft I tried.
Rob