"...but that is quite difficult because those without the problem do not contact us or post."

 

Rob, et al

 

I have not experienced this issue but happy to help in any way possible. Perhaps a dedicated website and/or thread might be more appropriate.

 

 

rgds / Les Parson

 

A note regarding the A2A 172: After reading Rob's post I got to thinking about the fact that with the exception of Affinity Mask I've got just about every freekin tweak  ever mentioned in my fsx.cfg. I went and commented out every one but left in HighMemFix and the WS ones. I kept frames locked at 30, LOD at 6.5, Autogen at 4, T_B_M back to 40. I commented out the DisablePreload one as well. Given all the various mentions about possibly using the default flight, or fsx Safe flight, or loading a default plane first, etc.,  with these newer planes, I couldn't figure whether or not it would have a positive/negative effect so I commented it out as well.

 

I then went and reapplied the 1.03 patch to eliminate the Hotfix patch(s). I ran my standard test flight on GPS from Edwards to Nellis taking off just before dawn utilizing landing and taxi lights, half way through the 2:15 flight I paused the sim and changed the time to late dusk so that when I got to Vegas all the lights would be on which crushes both my rigs even in the daytime. True enough, frames dropped to about 7 momentarily at their worst as I paralleled the Vegas strip but I got all way to touchdown and taxi to parking never losing clickspots at any time. Watching those landing/taxi lights illuminate the terrain/runway/taxiways and parking ramp opened my eyes very wide.

 

All during the flight I kept switching views, panning around, flipping switches and adjusting light intensities, into windowed view to see what was going on in Task Manager (Working sets and free memory) as well as NVI monitor to see what my GPU temps and usage were. As the landing lights started to illuminate the ground and runway at Nellis I kept checking and never once lost clickspots. I need to do more flights but my optimism meter is on the rise at this point.

 

So if you, like me, are a member of the "tweak it till its broke" club this might be something to look at.

 

So far I've only tried it on my 2700 rig. My 4770 has an almost identically blinged cfg. I installed the AUS SP4.003 patch on it, took off at Canberra, switched to the 172 - clickspots lost immediately.

 

I7 2700 @4.6, 8GB @ 1866, NVGTX580, C=256SSD, E&F=600 V-raps, 30" Dell, CH/Saitek Prod. W7-64 (REX, FEX, GEX, UTX, OPUS, AeroSoft, Fly Tampa)

 

I7 4770 @4.3 16GB @2133, NVGTX780, C=1TB Samsung, Sony 40", CH?Saitek Prod, W7-64 (REX, FEX, Orbx)

In the meantime, to sooth the savage breast (or is it beast?) here's another paint to be going on with.

 

HERE

Nice!

"...but that is quite difficult because those without the problem do not contact us or post." Rob, et al I have not experienced this issue but happy to help in any way possible. Perhaps a dedicated website and/or thread might be more appropriate. rgds / Les Parson

 

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

I've had my clickspots dissapear at random as well. I have a stable computer and vanilla FSX with no other addons than FSUIPC and FSGRW installed. I use a Saitek cockpit setup with SPAD drivers and FSUIPC mappings, don't know if that's where the problem lies.

 

None of our aircraft require FSUIPC to run. Many have it installed because it is required for some other addons. I emphasise here that I'm not in the least blaming FSUIPC itself, but it might be possible that something in the Duke doesn't like it.

Removing FSUIPC while flying the B60 is not an option for me, because FSUIPC is fundamental to many other parts of my FS experience, including many key and button assignments, Lua scripts etc.

 

I know you weren't suggesting that Rob, I'm just commenting that I hope the problem is not with FSUIPC, (and I'd find it hard to believe that it was when virtually every other add-on works flawlessly with FSUIPC).

 

Cheers.

I assume this issue has been investigated on a 'clean' fsx ? ie. no add-ons or mods except the plane itself ?

It sure looks to me like something else is the cause of this and the loss of click spots is a symptom of something else.

Very possibly Jim.    But then, the A2A 172 suffered exactly the same issue, and a patch was released that resolved it.  So that suggests it was something within the realm of the add-on itself.    (Unless of course the patch changed something to address an incompatibility with another add-on, in which case we're back to your theory :lol:).

 

But it's all conjecture for now I know.    I'm sure Rob and Sean are working hard on investigating the issue and I have every confidence they'll crack it.   :smile:

To cut a long story short I think I have solved my click spot problem by un-installing reality xp and re-installing it and making sure it does not look for auto updates.

 

Done 2 flights now with no problems. fingers crossed .

For clarification David, was that un-installing RXP from the PC, or just removing it from the Duke?

 

Just out of curiosity, for anyone that doesn't have RXP installed, are you aware of the problem after installing the Duke and leaving the configuration tool thingy with all the default settings?

To cut a long story short I think I have solved my click spot problem by un-installing reality xp and re-installing it and making sure it does not look for auto updates.

 

Done 2 flights now with no problems. fingers crossed .

 

Hi David,

 

As far as I can see, my RXP 430 WAAS doesn't look for updates automatically.  When I first installed it, it did check for an update, and updated itself to the current version (1.6.0.1) just that once.  Beyond that I cannot see it attempting automatic updates, and can't see anywhere where that could/would be de-selected?

 

Cheers,

Dave.

Dave it's the 530 I have and the only time I saw the option is when installing. The clue is the B60 loads within a second into the fsx free flight window if its looking for updates it takes 4-5 seconds for it to show and even then the update window pop up when loading is around 30% if  it thinks you need an update.

 

@ Paul.

I un-installed it from PC(add/remove windows programme) installed it fresh. The first or one of the first option is, would you like reality xp to auto look for updates. uncheck the box as it's checked by default.

Re do the Duke's control panel to include it after new install. jobs a good one.

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

I've been a long time sufferer of the clickspot issues. Right now all is well with the Duke. I have them with the Flight 1 King air. They are so sporadic finding a solution is a big challenge. Every time I think I've found the cause I'm proved wrong. often times I have no issue for days and then all of a sudden it happens. often times a reload of the aircraft solves the issue. Sometimes it doesn't. That issue is often accompanied by frozen PFDs and MFDs and view problems. Whatever the issue is it's common to at least 3 aircraft. The A2A 172 and the Duke and the King air.