Nick Dobda

Losing Clickspots

Recommended Posts

I've had this issue before. Clickspots start to act funny... then they work and stop working randomly... then they stop working altogether. This happens over the span of about an hour.

 

Some background, I am aware of the viewpoint behind the seat issue that is notorious for clickspots vanishing. I have been running EZDOK for about a month now with no issues. I have not changed any viewpoints in the last month, this problem just started tonight on this particular flight. By the end of the flight, clickspots and all buttons were essentially not usable.

 

I remember having this issue in the past, but suspected a fix and tried it, and the problem went away. I was wondering if my theory has any weight or not.

When the problem first arose a few months back, it was on my round the country flight. Each night I would save at the conclusion of the past flight, then start up the next night on where I left off. At one point this clickspot issue thing popped up. I thought maybe there was some sort of error that has accumulated, so one night i loaded up fresh where I left off... that is loading from the root menu by picking the airport and a new gate, then loading a new NGX fresh. The problem went away.

 

When you load up from where you left off, the oil and hydraulic fluid slowly go down. When you load up from where you left off (by a saved flight) the oil and hydraulic quantities are the same as when you left off. IF you load up from the FSX root menu, the oil and hydraulic quantities reset.

 

I guessed that since those oil and hydraulic quantities are being carried over, there must be some behind the scenes things being carried over as well. Im guessing that some sort of something eventually snowballs and the clickspots stop working.

 

 

To run some tests, I saved the flight as the problem was happening. I closed FXS, then restarted.. and loaded up from where I left off. The problem persisted.

 

I then shut down fsx, restarted and loaded from the root menu back at the original airport (new oil and hydraulic quantities) and the problem was gone (at least it didn't resurface in the 5 mins I clicked around the cockpit).

 

My question is... what is going on there? Am I right that picking up where I left off from a saved flight carries information over that over time may become corrupt, and that re-loading from the root menu is like a fresh start?

 

I really hope tomorrow I can re-do the flight fresh from the root menu all the issues will be gone.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

It could be to do with the panel state, but if it was I would expect to appear at the beginning of the flight, when the aircraft is loaded. It's more likely to be due to Ezdok, or rather the way FSX affects it. The viewpoint moves with heading and aircraft latitude due to an FSX bug. So if your heading changes during the flight, or you are flying generally towards the equator, the viewpoint may move aft, enough to put it inside the pilot seat and prevent clickspots working.

 

You mentioned it happened to you during a tour, so you will gave been flying on various headings.

 

As a test, try this. At the most southerly* airport you used on your tour, taxi or slew to various headings: 360, 045, 090, 135, 180. At each heading check to see if the clickspots work. If they always work then the problem may be to do with the panel state.

 

[* if you were flying in the Southern Hemisphere then choose the most northerly airport]

Share this post


Link to post
Share on other sites

Thank you for the advice. I was flying Chicago Midway to Green Bay last night. I knew about the pilot seat issue, so I moved the viewpoint all around and the problem persisted. I have 8 points of view setup, and the clickspots weren't working for any of them. For example, I'd shift from the captains seat to the lower OH panel (eyepoint is mid cockpit) and none of the buttons would work. Sometimes, the clickspots would start working for a click or two, then stop working again. 

 

What happens with the panel state to cause the problem? Is it just an accumulation of information that eventually leads to the problem? Would re-loading a fresh panel state stop the problem if it happens in the future you think?

  • Upvote 1

Share this post


Link to post
Share on other sites

Panel states based on the previous flight can become corrupt and cause problems. If they do it's best to start again from a PMDG default state.

 

I usually use a default state, but I've had random occasions where the VC clickspots ceased to work. Reloading FSX fixed things, so I put it down to a bad load, something not being initialised properly.

Share this post


Link to post
Share on other sites

I found that reloading FSX (with the same panel state) started the buttons to work again too, but stop working again fairly quickly. If the panel state is corrupt though, the problem would come back. 

 

If you are confident that the panel itself can become corrupt and that losing clickspots is one such corruption, I think you're right reloading a fresh panel state would fix the problem. 

Share this post


Link to post
Share on other sites

Nick,

The problem you are experiencing sounds exactly like the issue I was posting about yesterday (Topic called Mouse weirdness)  I've yet to find a fix, it is intermittent so it makes it really hard to fault find.  Saving the flight completely exiting fsx then restarting fsx and reloading the saved flight tends to fix for me at least temporarily.   At a bit of a loss  so If you find a cause or solution please let me know.

 

Thanks

Andy

Share this post


Link to post
Share on other sites

I've the same problem, it started about some months ago, I've also written to PMDG Support, but there is no fix.

 

I think is a problem with FSX:SE (latest Update to prevent mouse frame drop) or the problem came with Windows 10.

Share this post


Link to post
Share on other sites

I suspect it has to do with the panel accumulating a bug. If I load up a fresh panel state and it works then problem solved. Ill post back when I get a chance to fly again.

Share this post


Link to post
Share on other sites

I reloaded fresh at the gate and everything was smooth as silk.

 

I think the problem is an accumulation of something in the panel state that over time makes clickspots stop working. It might have been in my head, but things seemed clearer, frame rates seemed higher, everything worked really well once I reloaded fresh.

 

What I mean by reloading fresh - Do not load a previous flight. Start at a new airport, and load a new NGX at the gate. I think this might refresh the panel state and give you a clean start.

 

Perhaps just loading a new panel state would work if you were experiencing the issue. If someone wants to test it. I overwrote my problem flight so I can't test it.

 

From now on I will not be continuing panel states between flights. I will start fresh everytime and probably never see the problem again.

Share this post


Link to post
Share on other sites

I think I've got this in P3Dv3.1

 

The autobrake, recall, master caution, fire warning buttons + more have no click spot. Other things like the gear lever works.

Maybe this will trigger something with the devs.

Share this post


Link to post
Share on other sites

I always use the C&D default panel state from PMDG.  The problem starts this summer when I switched from Win 7 to Win 10 and from FSX:SP2 to FSX:SE.

 

Sometimes when I switch the views with EZDOK, some buttons are working again, bust just only for seconds. I have to use the 2D Panels instead.

 

The MD11 and 777 don't have this problem in my system.

Share this post


Link to post
Share on other sites

 

 


Sometimes when I switch the views with EZDOK, some buttons are working again, bust just only for seconds. I have to use the 2D Panels instead.

 

Something to make EZDOK aware of.

Share this post


Link to post
Share on other sites

On the subject of running panel states over multiple sessions and the possibility of some sort of error accumulation-

 

I've noticed that over time, the temperature knobs get pretty far out of whack to try and maintain 20 degrees throughout the cabin. Especially in northern climates over the winter here, they programmed in the temp in the forward cabin to drop when the doors are open. So during loading I'll bump up the temp knobs to maintain about 20 throughout the cabin. When the doors close and so forth I'll have to turn the knobs back down to maintain 20.

 

Over time, The knobs are in really extreme positions to maintain 20 even when conditions should be steady and normal, like cruise. When I started fresh last night, the knobs were all in the 12 o'clock position and maintaining 20 when the doors were shut. On the last flight when things were going whacky the forward cabin would be at 9 oclock, mid at 11 oclock, and rear might be 2 oclock and the temps would read near 20 in all cabin areas. It just seems that maybe in the background something isn't getting carried over between sessions, or some data gets slightly off after every session, and that over time those slight losses accumulate and eventually fail the click spots.

 

Also, when I originally had this problem (losing clickspots over a touring flight [that is, re-loading the flight where I left off the night before]) I would eventually arrive in this same situation where things started to get whacky and click spots not working, and this was before I had EZDok. I think changing views gives the panel a kick to make the buttons start working, and it's not ezdok itself, but the changing of the views that does it. Just my hunch though.

Share this post


Link to post
Share on other sites

It don't think it's a problem with EZDOK, I'm using it for years.

I tested it without Ezdok some weeks ago and had the same problems.

Share this post


Link to post
Share on other sites

PMDG said loading any saved flight in P3D 3.0 and 3.1 there is some type of miscommunication between both programs, PMDG aircraft and P3D. They said P3D is aware are working on some type of fix that will come out in version 3.2 whenever that is. For the time being there is nothing that can be done according to what they told me. 

Share this post


Link to post
Share on other sites

Just to chip in again.  Its not an EZDOK thing as I don't have that, and still have the issue. 

It never happened with FSX SP2 and Win 7.  (Ive owned NGX since it was launched)

It started happening about 2 months after buying a new PC with Win 10 and then purchasing Steam Edition. Running a completely fresh install of everything.   For the first two months it was flawless, its only started happening in the last month or so.  It only happens with the NGX to my knowledge I have not seen it happen with the PMDG 777.

 

Andy

Share this post


Link to post
Share on other sites

 

 


It started happening about 2 months after buying a new PC with Win 10 and then purchasing Steam Edition. Running a completely fresh install of everything. 

 

Did you run the required SimConnect installers?

Share this post


Link to post
Share on other sites

Hi Kyle.

Absolutely.  All Sim Connect installers were run in line with the release notes that go with the NGX download.

I can run them again if people think it will help. 

I forgot to mention I have created my own Start up panel state for the NGX rather than using the default engines running state.  Not sure if that's relevant either.

 

Andy

Share this post


Link to post
Share on other sites

Happened to me once.  Naturally once the flight was all set up and read to taxi.  Clicking out to spot view and cycling views brought it back but only long enough to click something once.

 

No reload or non-default panel states/loads either.

Share this post


Link to post
Share on other sites

You guys having the problems, are you loading previous flights or starting fresh? Are you loading the panel state from your previous flight, or loading a panel state from some base panel state? If the problem is what I suspect, then loading a panel state from a base state should fix the problem.
 

For example, if you save your flight (and panel state) at the end of a flight and pick it up the next day when you left off, over the course of 7 flights you would have modified the panel state 7 times, with 7 opportunities for data to become corrupt. At some point the panel will fail, and if you continue to build off that panel state all states after will also fail.

 

P1 - P2 - P3 - P4 - P5 - P6 - P7.. and so on. If P5 becomes corrupt, P5 and P7 will also be corrupt.

 

Instead Start at P1, your "turnaround panel". Then restart all flights from that panel state. You can pick up where you left off, just go into the FMC and re-load that original "turnaround panel".

 

P1 - P1 - P1 - P1 - P1 - P1 - P1

 

I'll probably just load fresh at every airport with whatever the default panel state is, which i believe is the short turnaround state, which I think is most common anyway, although I might try making a few tweaks and saving that state and using that as my "turnaround panel".

 

Of course, I'm not sure the exact nature of whats going on, or that what I'm guessing that's going on is going on if that makes sense. If you happen to be getting ready to push back and see the problem arise, I'm not sure if going into the FMC and reloading up the default long, short, ready for takeoff state (or some other state that was created on the first flight of these default panel states) will get things going again. 

 

For my specific instance, however, I've found that loading up fresh with the default "short" panel state eliminated the problem.

Share this post


Link to post
Share on other sites

Your method doesn't work if you want to pickup a flight at T/D, or practice an intricate precision approach over and over. Since my time is limited I like the ability to be able to resume a flight in progress. I have not been able to do this period.  

Share this post


Link to post
Share on other sites

This issue is in P3D as well. Anyone else experience it?

 

 

I think I've got this in P3Dv3.1

 

The autobrake, recall, master caution, fire warning buttons + more have no click spot. Other things like the gear lever works.

Maybe this will trigger something with the devs.

 

I think (hope) that PMDG are working with Lockheed Martin to resolve this problem.

 

Regardless of correctly installing the legacy Simconnects, and loading up the PMDG 737 first, the VC clickspots issue occurs (for me at least) on a totally random / intermittent basis on P3D v3.1 and Windows 10. I can start P3D, load a saved scenario and get the problem, re-start P3D, re-load the exact same scenario and everything works!

Doesn't seem to happen with the 777 as far as I recall.

I've learned to live with it, hoping that PMDG / LM resolve it in the next release(s), I've no hair left to tear out!

Edit - I also have never used EZDOC

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now