For everyone with this issue, I spent the night mentally processing all of this... I'll need the following info:

1. What aircraft is affected by the issue?
2. Is it happening after a fixed amount of time after restarting ChasePlane
3. Does pressing the Reset Pointers button in the Preferences fix the issue? (Either way, if possible, generate a Report file and send it to us with a reference to this thread)

A temporary solution would be to disable Advanced Features in the Preferences. This will restore camera movements so you can continue using the software at least.

Thanks everyone for their reports and for their patience on this issue.

All I can tell you is , last night I was flying the PMDG NG from LIRF-LICJ and around 20 mins into preflight I went to look around the outside of the aircraft and got a view from inside the cargo bay . No other out side views worked. I closed and restarted chaseplane and all was well again. The next time I noticed something wrong was changing views within the VC, there was an odd sort of small zoom in and out only a split second but it was there . I went to an outside view again and I was back in the real cargo hold, again no out side views worked.

It happened again when I was at LICJ and went to an out side view. Thinking about it I would say it went wrong after around 20 mins every time. 

Sorry no logs and reset it as per your instruction on last page.

Never had or seen this before.

 

What version of CP are we discussing here? I flew KCLT to KJFK in the PMDG NGX last night and had no issues whatsoever. I have auto-Cinematic turned off, and didn't use my assigned button to toggle out to Cinematic, so maybe that's why I don't experience the problem. CP v0.4.182. But then again, I never had any problem with v0.4.183...other than my issue of all the missing airports in Static cams, but this isn't specific to 0.4.183.

2 minutes ago, somiller said:

What version of CP are we discussing here? I flew KCLT to KJFK in the PMDG NGX last night and had no issues whatsoever. I have auto-Cinematic turned off, and didn't use my assigned button to toggle out to Cinematic, so maybe that's why I don't experience the problem. CP v0.4.182. But then again, I never had any problem with v0.4.183...other than my issue of all the missing airports in Static cams, but this isn't specific to 0.4.183.

I guess that's why there is a discussion here! If I was able to replicate the issue it would have been fixed days ago... I'm still trying to figure out what all of those systems have in common.

21 hours ago, RichieFly said:

Same here. I'll try the toggle to get back.

FYI, Each time it stopped responding (CP), it was after I had toggled to the cinematic view and back to VC.

Same thing here for me.  I had initiated cinematic view.  Then it hangs.  I am on a new build though and I did not turn automatic cinematic view off.  Does it remember this setting in the cloud and then use it on a new install?

I wonder if it would have anything to do with power saving features of the O/S?  As I said a few minutes ago, I just completed a new build(Windows 10) and I know I did not check what Windows is doing here with my USB devices.

24 minutes ago, Keven Menard said:

I guess that's why there is a discussion here! If I was able to replicate the issue it would have been fixed days ago... I'm still trying to figure out what all of those systems have in common.

Keven,

Hope I didn't come off as finding fault or being critical of anyone or anything, I was just curious of which version is causing this issue for some folks. I understand the purpose of the discussion, which is why I asked for details, to determine whether I had anything to offer.

Is anybody, or everybody having the problem using Track-IR?

Cheers,

1 hour ago, somiller said:

Keven,

Hope I didn't come off as finding fault or being critical of anyone or anything, I was just curious of which version is causing this issue for some folks. I understand the purpose of the discussion, which is why I asked for details, to determine whether I had anything to offer.

Is anybody, or everybody having the problem using Track-IR?

Cheers,

v0.4.183

It's now been rolled back to v0.4.182

No TrackIR.

Never had a problem with chaseplane in the last year until last night. I'm sure Keven will find the gemerlin.

6 hours ago, somiller said:

Hope I didn't come off as finding fault or being critical of anyone or anything, I was just curious of which version is causing this issue for some folks.

Sorry if my response seemed harsh, it was not the intent :) I get what you're saying!

Just done a full flight with v0.4.185 and all was perfect.

For those who had this issue for a while, did the latest build fix the issue?

8 minutes ago, Keven Menard said:

For those who had this issue for a while, did the latest build fix the issue?

My last flight last night was fine.  No issues.  But I didn't check if I have the latest build or not.  I don't recall what my settings are as to whether it will automatically get latest(experimental or stable) or if I turned that off?

3 minutes ago, klamal said:

My last flight last night was fine.  No issues.  But I didn't check if I have the latest build or not.  I don't recall what my settings are as to whether it will automatically get latest(experimental or stable) or if I turned that off?

If you're on Experimental, you always get the latest one. My question really should be: 0.4.183 was broken, all the other versions should have been working properly. Is that the case?

2 minutes ago, Keven Menard said:

If you're on Experimental, you always get the latest one. My question really should be: 0.4.183 was broken, all the other versions should have been working properly. Is that the case?

Right.  I don't recall where I left that setting.  I think I'm on Experimental yet.  But, I don't know for sure.  Unfortunately I am away from my FS PC right now to check.  Probably won't get the chance again until tomorrow.

17 hours ago, Keven Menard said:

If you're on Experimental, you always get the latest one. My question really should be: 0.4.183 was broken, all the other versions should have been working properly. Is that the case?

I already said above, but yes Keven, all is good now and working perfectly again. So yes it fixed it, whatever it was that was broken. Glad you found the problem. 

Thank you.