Hello everyone Im currently having an annoying issue that I hope I can get some input in order to solve it.. about a week ago I reinstalled FSX with SP2 (I still have the DVD's) and gave it a go with some aircraft I purchased in the past, these are:

RealAir Duke V2

A2A Cessna 172

PMDG 737NGX

Wonderful aircraft, the thing is from time to time they become unflyable due to some click spots disappearing in VC, I already tried moving the eyepoint, changing views and they randomly come and go, I read a few days ago that for the Duke the issue falls in the 3D lights system and splash of the landing lights, however the same issue happens in the other 2 aircraft mentioned above, I'm wondering if the clickspot issue befalls on the 3D custom lights from the 3 planes by itself if it's something that isn't supported by FSX, I'm running on DX10 preview with SteveFX DX10 fixer and no, I'm not using EZDok, I know EZDok causes a lot of problems, I only use OpusFSI but livecamera option is totally disabled.

My system specs are as follows:

Lenovo Legion Y520 Laptop

nVidia GeForce GTX1050

Intel i5 7500 series

8GB of RAM

I would appreciate any input you could give, this issue is very frustrating due to the fact that happens randomly and theres no way to accurately reproduce it.

Thank you

Fernando

 

Seems like a common problem with some payware aircraft!

 

Yeah, it's very frustrating because sometime ago I used fsx on another system and didn't have any problems like these, it was an older spec laptop and even though it ran fsx with single fps digits it never had any problems with clickspots, Im currently figuring it out by changing my default graphics adapter, switching from the Intel integrated one to nVidia. No avail.. some people suggested lowering display settings within fsx already tried that, put them to the minimum, vanilla style lol and didn't change a thing, issue still there, doesn't happen with default ac. I'm wondering if the 3D custom lighting is the culprit...

Edited July 21, 20205 yr by fernando13e

1 hour ago, fernando13e said:

is the culprit.

"That is the problem, if you get too far back the mouse rectangles become inactive.. Don't remember if there is a reset eyepoint command available. If there is, use it. Otherwise use the built in camera views to move around the cockpit. "

 

In other words, move your view a little forward, normally hit

CTRL+BACKSPACE  will do the job.

Edited July 21, 20205 yr by polosim

Thank you for your input! Unfortunately I tried everything with the viewpoints, moved forward, backwards, left and right and even reset the viewpoint, no avail :(, it happens with all 3 aircraft same way

My attempts to isolate the problem in the RealAir Duke V2 have not been successful so far.  The initial Duke V2 release documentation included this:
"This program requires Microsoft .net Framework 4.5 and Microsoft SQL Server Local Database 2012 to be installed and if they are not present the setup will install these components."

A reinstall of Microsoft SQL Server Local Database 2012 had no effect.

Windows 10 has Microsoft .net Framework 4.8 and a change in there MAY be the root of the problem. I have no proof to support that - it's just a suspicion.
 
Assorted experiments seem to indicate the following:
-fault not in panel folder
-fault not in sound folders
-fault not in air file

Interestingly, the earlier Duke V1.5 works just fine! 

2 minutes ago, Ranger75 said:

My attempts to isolate the problem in the RealAir Duke V2 have not been successful so far.  The initial Duke V2 release documentation included this:
"This program requires Microsoft .net Framework 4.5 and Microsoft SQL Server Local Database 2012 to be installed and if they are not present the setup will install these components."

A reinstall of Microsoft SQL Server Local Database 2012 had no effect.

Windows 10 has Microsoft .net Framework 4.8 and a change in there MAY be the root of the problem. I have no proof to support that - it's just a suspicion.
 
Assorted experiments seem to indicate the following:
-fault not in panel folder
-fault not in sound folders
-fault not in air file

Interestingly, the earlier Duke V1.5 works just fine! 

That's curious, isn't supposed that higher Framework versions supercede the required version and it should work anyways?

1 minute ago, fernando13e said:

That's curious, isn't supposed that higher Framework versions supercede the required version and it should work anyways?

That's the theory!

Is the clickspot issue for specific locations on the flight deck, for for all instruments and panels?  One recent issue I had was not being able to use the  Just Flight Piper Arrow II's GNS 430 unit, but it turned out that the unit I could see was only a placeholder for the separate Flight 1 GNS 430 add-on.

Hi!

On 7/22/2020 at 9:13 AM, BF Bullpup said:

Is the clickspot issue for specific locations on the flight deck, for for all instruments and panels?  One recent issue I had was not being able to use the  Just Flight Piper Arrow II's GNS 430 unit, but it turned out that the unit I could see was only a placeholder for the separate Flight 1 GNS 430 add-on.

It's for all the instruments, on every cockpit for every plane I mentioned, tried all variants and every combination possible, reloaded the sim and even played with the display settings, it seems to happen at random times, sometimes I get all the instruments working for an hour and then just boom, no instrument click spots again, restart the sim and even from the start dont have any clickspots available, after 3 or 4 times I can get them to work again, sometimes they work straight just after loading.. very frustrating as I can't replicate anything.

43 minutes ago, fernando13e said:

Hi!

It's for all the instruments, on every cockpit for every plane I mentioned, tried all variants and every combination possible, reloaded the sim and even played with the display settings, it seems to happen at random times, sometimes I get all the instruments working for an hour and then just boom, no instrument click spots again, restart the sim and even from the start dont have any clickspots available, after 3 or 4 times I can get them to work again, sometimes they work straight just after loading.. very frustrating as I can't replicate anything.

Do you get the same issue with the default aircraft?

8 hours ago, BF Bullpup said:

Do you get the same issue with the default aircraft?

Sorry for the delay, fortunately no, default aircraft works fine. I'm considering migrating to P3D, but most of the scenery I use are really old Payware and freeware stuff, some of them even are compatible with FS9, that's the holdback for me. I'm wondering if all the scenery I have in FSX would work on P3D v3 at least

5 hours ago, fernando13e said:

Sorry for the delay, fortunately no, default aircraft works fine. I'm considering migrating to P3D, but most of the scenery I use are really old Payware and freeware stuff, some of them even are compatible with FS9, that's the holdback for me. I'm wondering if all the scenery I have in FSX would work on P3D v3 at least

It must have something to do with an add-on module that all the aircraft you have issues with rely on.  For example, FSUIPC?  An external add-on GPS?

7 hours ago, BF Bullpup said:

It must have something to do with an add-on module that all the aircraft you have issues with rely on.  For example, FSUIPC?  An external add-on GPS?

Hello again!, No external GPS addons, and we'll I have fsuipc, demo version though, planning to get the full version, would that cause issues?

Removing FSUIPC - and everything else, from dll.xml has no effect on the RealAir Duke V2 missing click spots.

WS