Let us know how you find it Dave. GL

Thanks Les. I think this thread is ok for the moment. I might contact you via email about this.

 

Meanwhile I have the co-operation of an independent developer not connected with us, of many years experience, who has installed the Duke V2 and is "trying" to provoke clickspot issues but so far he has not had any. We are trying a few things to see if we can reproduce it. 

 

Best Wishes,

 

Rob - RealAir

 

Hi Rob, 

 

As mentioned in a previous post, I was adjusting the altitude knob on the autopilot panel with the mouse wheel (set in the config to Left+Right click), and braked. Due to the braking the clickspot moved from under the mouse pointer whilst it was still being operated, and following this all my clickspots died. I haven't tried reproducing this yet.

 

Hope this can help.

 

Karl

Ok thanks Dave, I'll try a uninstall / reinstall, (without the auto updates) and see what happens. Cheers.

 

 

Let us know how you find it Dave. GL

 

Hi David,

 

I uninstalled RXP, then re-intalled it, and unticked the "check for updates automatically" box.  I then set up a Duke B60 v2 flight, which I kept in the air for just less than an hour, (before I had to go to take my daughter to Tae Kwon Do!), I had NO clickspot failures in this time.     :cool:

 

Usually (but not always) the clickspots would fail after 10-15 minutes, so I consider this a very promising possibility that your suggestion may have solved the problem - at least for some,

 

More flying and testing over the coming days will further confirm whether or not this has done the trick.

 

Thanks for your great efforts and pragmatic approach to finding the problem..... if it has fixed it, I will certainly owe you some virtual John Smiths tokens....  :drinks:

 

Cheers  

Am really pleased for you Dave, happy to help and lets hope I've found the problem. I thought it might just work for me.

Hi Guys,

 

Rest assured we are looking in to this problem. In all the years we have been developing for FSX never have we seen a bug this hard to crack. Unless I'm much mistaken no developer has found a 100% bullet-proof solution, rather the fixes to date tend to reduce the likelihood of the problem occurring - they might work for some people but not everyone. At the time of release none of our testers were experiencing this problem although we did experience it on an early beta.

 

I strongly believe that there is nothing actually wrong with any of the aircraft that are experiencing this problem, rather it seems that some combination of elements within certain FSX aircraft are triggering a bug within FSX itself. If there was something specifically wrong it would be possible to fix the problem for all users. The way that the fixes to date work for some people but not others suggests that there is no one problem that needs fixing. My gut feeling is that it is to do with complexity, the aircraft with sporadic clickspot issues are all complex in terms of texture count, custom code, sounds and animations. The fixes that have reduced the likelihood of a problem occurring seem to have focused on deleting complex features such as landing lights and a few other things.

 

If you are experiencing this issue and would like to take part in some testing to try to find a solution could you please send me an email. - [email protected]

 

Thanks,

 

Sean.

You should change that to "at" "dot" and "com" so the spammers don't get the email.

Sorry if this has already been asked! But Is RealAir going to support Prepar3d V2?

Hi Alec,

 

We never pledge to support anything until we have seen it working and thoroughly tested it, but we will be looking very closely at P3D and user reactions to it.

 

Rob - RealAir

Thank you for the fine answer!

Let me add my congrats to the developers on an amazing product. I am moving over to P3D and no longer purchase FSX-only products, so I'll add a vote for P3D v2 support.

I purchased the Duke v2 yesterday.  When I started flying it, I said to myself, "this is my favorite twin", but, about a minute (or less) in the flight, I lost the capability to adjust any knobs or switch on/off any switches with my mouse.  I noticed a lot of others have the same problem.  And, this only happens with this aircraft.  I had purchased the A2A 172 shortly after it was released and didn't have the problem as mentioned above.  

 

Are there any fixes to this problem, or ideas?

 

Win 8 64Bit

 

FSX Acc

DX10 (I tried it in DX9 also)

FSUIPC payware

EZDOK (I even shut off EZDOK)

 

The above programs are the only programs running at the time I was flying the Duke.

 

Rod

I purchased the Duke v2 yesterday.  When I started flying it, I said to myself, "this is my favorite twin", but, about a minute (or less) in the flight, I lost the capability to adjust any knobs or switch on/off any switches with my mouse.  I noticed a lot of others have the same problem.  And, this only happens with this aircraft.  I had purchased the A2A 172 shortly after it was released and didn't have the problem as mentioned above.  

 

Are there any fixes to this problem, or ideas?

 

Win 8 64Bit

 

FSX Acc

DX10 (I tried it in DX9 also)

FSUIPC payware

EZDOK (I even shut off EZDOK)

 

The above programs are the only programs running at the time I was flying the Duke.

 

Rod

 

Welcome to the 1%  :wink:

 

Myself and Nyxx had the same problem and appeared to resolve it by uninstalling our Reality XP gauges, and re-installing, with the "auto updates" option unchecked.      Although to be honest I have only performed one small test, so need to test more before reaching a conclusion that the issue is definitely resolved.

 

So question number one would be, are you using the Reality XP 430 or 530 gauges with your Duke B60 v2 ?

I am. Not sure if auto updates are on

Welcome to the 1%   :wink:

 

Myself and Nyxx had the same problem and appeared to resolve it by uninstalling our Reality XP gauges, and re-installing, with the "auto updates" option unchecked.      Although to be honest I have only performed one small test, so need to test more before reaching a conclusion that the issue is definitely resolved.

 

So question number one would be, are you using the Reality XP 430 or 530 gauges with your Duke B60 v2 ?

Dave,

 

Thanks for the response.

 

Nope.  Have no Reality XP products.

 

I'm thinking about uninstalling everything, including FSX, and start from scratch, before I hang it up.

 

I sent an email to Rob and Sean, but have not heard back.  Of all the years of flying FSX (since FSX came out), this is the first I've ever seen this, or even heard of it.  It's a shame, for us, because it's such a great flying airplane.  But I won't enjoy it if this problem continues.

 

Do you use EZDOK and are you using WIN 8?  

 

Thanks again.

 

Rod

Rod, I always send timely responses. I replied to you immediately (if it is who I think emailed me) on seeing your mail. It is currently 11.30 at night here and I do need sleep occasionally.  :blink: