From the moment I have installed unregistered version of fsuipc I am suffering from clickspots loss in vc. They start as soon as I load realair duke v2. After removing fsuipc it is fine and works again but I don't want to remove it because it helped with g3d.dll issues.

 

Did anyone have this problem before and knows a way to fix it?

Just tested it, with the latest version of FSUIPC from here :  http://forum.simflight.com/topic/66139-updated-modules/#entry417029

 

and had no problem.

 

I am using the Duke v2, my version of FSX is the Gold version, I'm on DX9 mode, I use Nvidia Inspector, and the only add-on scenery I have installed is the LPMA ( Madeira ) from Aerosoft.

 

My other add-on aircraft are the PMDG 777 and the Carenado B1900d, whith wich I do not have any problems as well.

Ok this is weird... I will try to reinstall duke tommorow

Ok I have read the manual and English is not my native but according to manual vc clickspots transfers your view to a particular panel. I cannot press any button at all in the cockpit or wherever in plane (cannot open doors, table etc)

 

Don't know if this is what is called clickspot but thought it should be

I understand it as being exactly waht you refer to as being zones of the instrument panel that "transfer" your view to other areas of the panel and their perspectives.

They should also be used to open doors, windows, etc...

 

This is not the same as the tooltips, that give you a textual version of an instrument reading.

 

I hope this helps.

 

Many users have complained about this problem. I remember I also had it in the past, but back then  I had, for instance, the A2A C172 installed, and that aircraft in particular had that problem...

Well let's put it this way - none of the buttons in vc is operative and I cannot switch any knob, button - nothing when pressing it with mouse.

A2a is ok in my case. I wonder if it has anything to do with scenery load - I am running it first time on Australia sp4. But I also see this correlation between it an fsuipc....

 

Tommorow will reinstall duke, if it won't help than I guess for duke flights I will be removing fsuipc. This will be a pain but well....

 

 

Tommorow will reinstall duke, if it won't help than I guess for duke flights I will be removing fsuipc. This will be a pain but well....

ipb.global.registerReputation( 'rep_post_2944085', { domLikeStripId: 'like_post_2944085', app: 'forums', type: 'pid', typeid: '2944085' }, parseInt('') );

 

I have a simple batch file to enable / disable FSUIPC

I just use it with a weather injector that requires it. Other than that I do not need FSUIPC.

Users who use it for specif hardware configurations will necessarily have a different oppinion...

And today I lost clickspots with fsuipc uninstalled

 

So I guess this aircraft badly needs a fix. I saw in ra duke thread that many people have it too..

 

A2a managed to fix that on Cessna which I also own so why not here...?

Reloading aircraft doesn't help and funy thing is that clickspots sometimes come back and are lost after 30 seconds again :(

Unfortunately this is something happening with a lot of newer models. Never happened to me but a lot had it in the A2A Cessna and apparently even on the T7 during beta.

 

Email Rob at Realair he may have had a trial for you

Do you have the option - aircraft landing-lights illuminate ground - ON  in FSX graphics options?  If yes, try starting by setting it OFF, and then test again please.

 

Whatever is causing this weird problem, and I did have it on previous FSX installs, is add-on related. The truth is now I do not have the problem, but I just installed

FSX, with only the RealAir Duke v2, the Carenado B1900d, the PMDG 777, and finally the Majestic Q-400, installed in this order.

Just did and sincerely hope that this will work out. 

 

I am also reinstalling product once again because the only thing I can think off which I added to my SIM except airports was livery pack for Duke when it started to happen. Let me check and come back with good/bad news. 

 

Thanks

It may not be fixable unfortunately.

 

Theories on why this happens:

 

Rescaling model parts during development

Over saturated FSX (combination of complex addons)

Those specialized landing lights

Great.... But I have never had this issue on axe, Cessna with new patch and even NGX which is much more complex addon. I hope I did not throw my money into bin. :(

Email RA support - they do a good job

JUst out of curiosity, did you cycle the "enable clickspots on VC" option in the Duke configuration program?