Keven

I went through pain staking detail to assure I didn't use any of the CP used cameras i.e. camera 1,5,6,or 8 when I set up my own custom camera views for my PMDG 737 virtual cockpit since when I previously used some of the above cameras and the associated HotKeySelect assignments they were all commented out of my aircraft.cfg files (wasn't happy about that). So I read your 1 page manual posting and only used cameras 0,7, and 9 so not to conflict with CP or the cameras typically used by P3D (i.e. cameras 1,2,3, and 4). Once I did this and launched CP again your program again commented out all my new camera view HotKeySelect lines. 

HotKeySelect = 10  for camera 0 assignment

HotKeySelect = 7  for camera 7 assignment

HotKeySelect = 9  for camera 9 assignment

Why is CP changing my aircraft.cfg file for cameras it doesn't use?

The reason I create my own views and want access them is when I fly VR with FlyInside I have to not launch CP because it causes stutters and visual issues. I use these new Virtual Cockpit views I create and can access with key assignments or Voice Attack so I can put myself in front of the Upper Panel or in different custom positions just like I can do with Chase Plane in P3D native VR. I don't use native VR because I find FlyInside much smoother and I prefer their options. But as I stated above I cannot use CP with FlyInside so I created my own work around for custom VC views by adding additional camera views to the aircraft.cfg file just like CP does and stayed away from the cameras CP uses as stated in your a page manual.

BTW I deal with the fact that CP changes the default P3D camera.cfg file by deleting it and letting P3D generate a new one when I fly 2D and the next time I launch CP it edits it again but this is a minor problem. However CP modifies all of my PMDG aircraft.cfg files and this is not acceptable. 

Could you please advise what I am doing wrong or would it be possible for CP at start up to ignore HotKeySelect commands that CP doesn't use i.e. cameras 0,7, and 9 and the associated HotKeySelect commands for them. 

If I can't resolve this I will have to abandon CP since for now VR flying with FlyInside is by far my preferred path. However I still fly in 2D mode and love my CP profiles!

 

Thanks in advance

Joe

Hi,

ChasePlane has to comment HotKeySelect 1, 6, 5 and 8 to be able to trigger its cameras. Those are the best assignments we found where it wouldn't conflict with that users are most commonly using. 

I have done some tests just now and found that if you put a space on either side of the =, it finds it and comments it. We will fix this in the next update.

Temporary solution would be to omit the spaces and just write HotKeySelect=X instead.

Regards,
Keven

Thanks for the response Keven

So I understand the need for HotKeySelect 1, 6, 5 and 8 used by CP but why do you comment out other cameras?

I made sure not to use those listed and CP commented out my HotKeySelect 10, 7, and 9 ??

Are you now saying that if I omit the spaces before and after the  =,  CP will not see them basically and ignore them so not to comment them out?

And if this is true will it also then ignore all HotKeySelect including 1, 6, 5 and 8 or just 2, 3, 4, 7, 9 and 10 ?

 

Thanks in advance

Joe

 

PS  I just looked at my code and I had no spaces on either side of the =  and they were still commented out with 4 redundant 

//  (Disabled by ChasePlane)//  (Disabled by ChasePlane)// (Disabled by ChasePlane)// (Disabled by ChasePlane) HotKeySelect=9  //  edited by Joe for use with Flyinside

 

PSS  Just in case you meant to say if you have a space it won't edit it I went back and put a space on each side of the =  and CP still commented out the HotKeySelct entry. So it doesn't matter the format:

HotKeySelect = 9  //  edited by Joe for use with FlyInside

HotKeySelect=9   //  edited by Joe for use with FlyInside

Both get commented out as shown above

You can still only use 2, 3, 4, 7, 9 and 10.

Very strange oddity you're getting there... Are you modifying the aircraft.cfg or the cameras.cfg?

15 minutes ago, Keven Menard said:

You can still only use 2, 3, 4, 7, 9 and 10.

Very strange oddity you're getting there... Are you modifying the aircraft.cfg or the cameras.cfg?

I fully understand the need to use only the stated cameras above 2, 3, 4, 7, 9 and 10 and did so.

Yes as said above I go into my PMDG 737-800NGX WL aircraft.cfg file for example and I add 2 new unique [CameraDefinition.014] and .015 views and use the HotKeySelect=7 and HotKeySelect=9 respectively. Additionally I add the HotKeySelect=10 to the default [CameraDefinition.010] F/O Seat.

All of these get commented out as shown above. I don't edit the P3Dv4 camera.cfg file but you do if I delete it and regenerate a new one for FlyInside. Regardless of whether the camera.cfg file gets changed by you or was already changed to the CP format my aircraft.cfg file always gets the above mentioned added HotKeySelect entries commented out as shown above.

It appears any added HotKeySelect commands added to the aircraft.cfg file gets commented out not just your protected 4 ?

Joe

 

Heres the aircraft.cfg example after CP comments out:

[CameraDefinition.014]

Title = "VR FlyInside Panel View" //  Inserted this new view

Guid = {c25f2790-d405-412c-ac19-16d3bb2b5efe} // obtained this unique Guid # from website

Origin = Virtual Cockpit

CycleHidden=Yes  // prevents it from showing when cycling views using A Key

MomentumEffect = No  // turn off momentun effect

SnapPbhAdjust = Swivel

SnapPbhReturn = False

PanPbhAdjust = Swivel

PanPbhReturn = False

Track = None

ShowAxis = YES

AllowZoom = TRUE

InitialZoom = 1.0

SmoothZoomTime = 2.0

ZoomPanScalar = 1.0

ShowWeather = Yes

XyzAdjust = TRUE

xyzAccelleratorTime=2.0

ShowLensFlare=FALSE

Category = Cockpit

PitchPanRate=30

HeadingPanRate=75

PanAcceleratorTime=0

InitialXyz=0.50, 0.0, -0.55  // Modified position for optimum upper panel view in FlyInside

// (Disabled by ChasePlane)// (Disabled by ChasePlane)// (Disabled by ChasePlane)// (Disabled by ChasePlane)HotKeySelect = 7  // assigned to camera #7  note CP uses Keys 1,5,6,8 and P3D uses 1,2,3,4

Only the protected 4 should get commented. I am unable to replicate the issue...

Can you copy the content of your camera definitions here so I can work on the same base as you?

Keven

I just deleted the comment      // assigned to camera #7  note CP uses Keys 1,5,6,8 and P3D uses 1,2,3,4

from the 2 [cameradefintions] .014 and .015  I added and the HotKeySelect was ignored this time by CP but not on the [cameradefinition.010](this was a default camera view that I just added the HotKeySelect=10) and strangely the redundant disabled are now only one. It looks like CP picked up the comment numbers I used as thinking it was the HotKeySelect banned numbers but that doesn't now explain why the [cameradefinition.010] still is getting disabled?

see below very strange:

[CameraDefinition.010]
Title = "F/O Seat"
.......
// (Disabled by ChasePlane)HotKeySelect=10 

 

CP got mixed because of the number 10 (thinking it saw the number 1). This is already fixed in the code for the next update.

Very odd that you got the comments twice...

Just saw...

If the line is 

HotKeySelect = 7  // assigned to camera #7  note CP uses Keys 1,5,6,8 and P3D uses 1,2,3,4

ChasePlane will get confused with all of that content... Try putting those notes below the line.

14 minutes ago, Keven Menard said:

CP got mixed because of the number 10 (thinking it saw the number 1). This is already fixed in the code for the next update.

Very odd that you got the comments twice...

Thanks

To be clear did my comment that contained the numbers in it cause the disabling of the HotKeySelect?

If it did that may explain the redundant disables because I had all four of the "banned" numbers in my comments i.e.  

// assigned to camera #9   note CP uses Keys 1,5,6,8 and P3D uses 1,2,3,4

notice it has 1, 5, 6, and 8 

and the disabling happens 4 times:

// (Disabled by ChasePlane)// (Disabled by ChasePlane)// (Disabled by ChasePlane)// (Disabled by ChasePlane)HotKeySelect = 7  // assigned to camera #7  note CP uses Keys 1,5,6,8 and P3D uses 1,2,3,4

Thanks for your prompt help!

Joe

That would explain it indeed!

I made a cleanup and removed some of the code listed above to save space.

2 minutes ago, Keven Menard said:

That would explain it indeed!

I made a cleanup and removed some of the code listed above to save space.

Once again Thanks for all the help I'm glad we figured this out!

So when will the update roll out so I can use HotKeySelect=10?

Joe

We'll be pushing it within the next few days.

Great news!

Again thanks for the prompt support

             you guys are one of the best with forum support!

Joe

Update has been posted!