Once again without fail my scenery is tearing (those nasty little triangular shards of blue all over the terrain) but the R6025 error never showed up. Several flights later still no R6025 error with tessellation ON.

That is a well-known anomaly caused by the old Nvidia drivers V337.88. They are not compatible with P3D. The most recent version, 344.11 are compatible and the blue triangular shards are all gone with Tessellation on.

 

As I stated above, the problem is in the Microsoft Visual C++ 2010 program. It is causing that error to occur (for a very few individuals as not everyone is getting this error). Perhaps Pete (developer of FSUIPC) can do a trap to stop this error from occurring like he did for the infamous g3d.dll error in FSX.

 

 

 

Best regards,

Hi FireHawk44,

 

Must be a problem with the AMD Catalyst drivers also because I'm currently running v14.9. I've attempted changing each and every setting permissible in the Catalyst software with no luck. As part of my troubleshooting I plan on reversing the driver back to 13.1 and 12.1 over this week when I have time to see what difference if any that will make. I'm also researching new hardware, specifically an upgrade for my video card using my current motherboard. Not an easy task, I'm trying to avoid a complete motherboard upgrade which forces me to upgrade most everything else. I'll never get free from poverty at this rate!    I have an extra NVidia card, slightly older but may give it a whirl for test purposes.

 

Cheers

I do not know anything about the ATI drivers but positive you can get good advice in the P3D Forum for the proper drivers. AMD/ATI screwed up big time back when Windows Vista was released (and FSX/Acceleration). They actually refused publically to upgrade their drivers to be compatible. This left a lot of people who had ATI video cards to have to dump their video cards and go for Nvidia (if they also upgraded to Vista). I will never understand their decision not to update. They stated they were tired of all of the Windows upgrades and I suspect they really liked Windows XP Pro. The Microsoft Aces Team were left with using Nvidia cards for beta testing before release of FSX. It was a long time after FSX and Vista were released before ATI decided to get on the bandwagon. Of course we want ATI to continue to develop ATI cards to compete against the evil Nvidia empire. LOL.

 

I actually did not realize there was a problem with tessellation with ATI cards. Thought it was just Nvidia alone. My eyes and ears are turned off when it comes to ATI cards and ATI drivers though. I use to have an ATI video card back in the XP days and I got it as I liked that catalyst program. Nvidia had nothing like that as I recall.

 

If you ever upgrade, I strongly suggest going Nvidia. I upgraded my two year old system with the ASUS Z87 Deluxe, a new CPU - i7 4770K, and video card Nvidia 780GTX. Think it was about $1500 as I gutted my old system and replaced it with the new MB, CPU, and Video Card. I enjoy building computer systems and may upgrade with the release of the new Broadwell or wait for the Skylake chipset. I can get a lot of my investment back by selling the old MB, CPU, and video card. Not sure though whether those chipsets will efficiently run FSX/P3D/X-Plane though. I will also have to upgrade my RAM to DDR4 which costs more. I have an SSD and a bunch of HDD's but would like to get SSD's as they are more efficient and perform better now.

 

Best regards,

Good evening, here it is again, flying nothing spectacular in mid flight, no changes to the set-up. I am pretty sure that it relates to the Visual Basic libraries but I have no idea how to isolate it.

Hopefully it goes away if you disable FSUIPC and/or RAASPRO? Or, do you have a virgin install of P3D too? If you have a virgin install of P3D, try reinstalling in C:\P3D. We have to look at this error or crash as system or installation related as this problem is not occurring in everyone's installation. If that was occurring, then I'm sure LM or FSUIPC/RAASPRO developers would be fixing it immediately.

 

Best regards,

 

During the install of 2.4 I received the notorious...

 

<Could not write value Complete to key \Products\A8FF3B2933C3CFE458D0FC925E24299D\Features. Verify that you have sufficient access to that key, or contact your support personnel.>

 

...I hit the IGNORE button as I did during my original virgin installation and the install completed without further ado (still that error is disconcerting).

 

 

 

I'm really surprised no one has mentioned this. Surely a problem of that nature (sorry I am not familiar with the error itself) compromises the installation right from the get go?

I did a search of my registry and I do not have this key.  I have P3DV2.4 installed (clean install).  So, not understanding why anyone would be seeing this error except maybe in past versions?  Did a Google search for that error - Could not write value Complete to key \Products\A8FF3B2933C3CFE458D0FC925E24299D\Features and see a lot of hits where some have fixed it by editing the registry. But, if you cannot find the key, do not know how it can be fixed. I have P3D Professional installed and maybe that's the difference. That is a permissions problem though and your system was probably not set up properly before installing P3D. This is why everyone recommends turning off UAC and any anti-virus program prior to installing a product as large as this. Anti-virus/malware programs have been known to find false positives and quarantine files needed for proper installation. One thing many can do (and this is in the AVSIM CTD Guide) is to download and install "Take Ownership". Then you can go to the P3D folder, right click it and select Take Ownership. I do not know if this will fix this particular problem or not but it solves the permission issue. Unfortunately, many individuals have several users on one computer and I think this is where problems can occur for many but not for all.

 

Best regards,

Hi FireHawk44,

 

UAC and permissions is not the problem here because on my flight simulator system using Windows 7 Pro 64Bit the UAC is completely turned off and all permissions are turned on. This I configured way back during the early FSX days on my system. I also load most critical flight simulator software to the root drive for similar reasons because the Programs x86 folder can be a stick in the mud, inherently designed that way, preventing our software from freely updating or working with files. The only anti-virus on my system is Microsoft Essentials which I completely turned off during the full install to version 2.4. I use Microsoft Essentials for minimum security since I must connect to the Internet for VATSIM and because I do occasionally browse the Internet for flight simulator related downloads/information, otherwise I wouldn't even have it on my system. So I don't see this as the problem here with the "Could not write value complete to key...". Until someone nails this problem to the wall we cannot say it is or is NOT a P3D problem. In my humble opinion I still believe it is!

 

Speaking again about the R6025 error I'll reiterate as stated in my previous posts, I loaded P3D v2.4 from scratch, full install, no addons whatsoever and will continue testing it for several more days in this state. Nothing so far has changed, the errors described remain consistent. On my system I did receive the "Could not write value complete to key..." error discused above during the installation but I read that clicking on IGNORE should allow an installation to complete successfully, though this should be fixed regardless, it's still disconcerting. Hell, FSX never hit the streets with this consistent an error! You think LM would be hopping all over this one? When flight testing P3D in the raw after the installation with the tessellation turned ON I "see" the scenery tearing in P3D. Now I'll admit I believe this IS a problem with my own hardware/drivers (more about this in a sec). When I turn tessellation OFF, which completely eliminates the scenery tearing (which makes perfect sense if you understand tessellation at it's roots) the R6025 error occurs (?) causing P3D to fail and restart while inflight, again addons are NOT the issue on my system nor should they be on ANY system because as stated I have none loaded, not even FSUIPC, so Peter Dowson can relax. This is a fundemental problem with P3D, and/or each systems drivers and/or hardware. We should not scramble our brains or waste our time trying to isolate addons. If you have this problem you need to strip down to a basic install without any addons and start troubleshooting from there, PERIOD!

 

Now, concerning the scenery tearing I'm almost certain the hardware/driver are at issue, so much so that I have bet my hard earned cash on this and ordered a new video card, an Nvidia GTX 660. I'll give the Nvidia a whirl in this case based on my research and also because it will be my card of choice if I upgrade my MB. I have already matched specs for new system hardware if I go there. I had an older Nvidia card, but if I'm going to try this I figured I might as well only do it once. If it doesn't work then I'll think the worst about P3D and return the NVidia card in less than 30 days to minimize my investment in a lost cause (for now) and continue using FSX only because it works flawlessly with it's impurity. If the new card does work than I'll be convinced my older HD6950 was not up to the task and/or the driver was faulty from AMD (like you say) and I'll run P3D with tessellation turned ON and forget about the R6025 error completely (buying LM time to hopefully fix both the key error and the R6025 error). Then I can focus on loading up P3D with addons and getting connected to VATSIM (what a hoot)! Let ya all know the results of the new card soon. B)

 

Cheers!

Speaking again about the R6025 error I'll reiterate as stated in my previous posts, I loaded P3D v2.4 from scratch, full install, no addons whatsoever and will continue testing it for several more days in this state.

Now, you have to figure out why you are just one of a very small group of individuals who has a virgin install of P3D2.4 and you are getting the R6025 and Microsoft Visual C++ 2010 w/SP1 error (although I get it now with FSUIPC or RAASPRO enabled, I did not with a virgin install). If there was a problem with the LM coding of P3DV2.3 or 2.4, do you not think that everyone who owns this product would be getting this error? They are not. So why would LM be jumping all over this to try and fix a problem that does not exist for, say, 99% of the community?

 

I do not own any anti-virus program. Never have since August 1991, never will. This is something that you might research more as anti-virus programs will not make changes to the system registry, your firewall, your computer system if you have settings set wrong in the program. Maybe this is why that 1% is having problems. The only way you can verify it is not your anti-virus program is to reinstall Windows and do not install the anti-virus program (but be positively sure your Windows Firewall is enabled for your Internet Connection - it is by default). Turn off UAC. On the P3DV2.4 install program, right click and select "Run as Administrator". Most computer experts, except me, recommend installing P3DV2 to the non-default folder so install it in C:\P3DV2 (which you state you have done). For you then it might be the anti-virus issue or even Microsoft Essentials (which I had installed but removed it).

 

Another issue that could be causing your problem(s) (just in your case) is the fact you admittedly do not have a super fast computer system. I do with the i7 4770K CPU and the Nvidia 780GTX video card. Maybe this is why you are having the R6025 error with a virgin install and others are not. You do not indicate your P3D.cfg settings. Are they all at the default, the way that LM configured it for your computer system? Or did you crank up the settings? Did you put the highmemfix=1 line in the P3D.cfg? It should NOT be there as well as any other FSX tweaks. Of course, rebuilding your P3D.cfg will fix this problem if it exists. Now the graphics are not going to be super great but this is how you have to test it. Cranking up the graphics when you are having problems with unexplained errors is a recipe for disaster.

 

Like me, there are a few people who have this error only when RAASPRO and/or FSUIPC is loaded. It's strange this occurs in P3DV2 and not in FSX but I cannot blame the LM software. Perhaps it is a problem with FSCrew or FSUIPC. Again it is not a 100% issue with everyone so frustrating.

 

Personally I wish everyone would have this R6025 error but unfortunately for us they do not. Most have absolutely no problems whatsoever with the software, just me, you, and a few others.

 

Best regards,

Hi all,

 

Quick update, the scenery tearing is fixed. Replacing the video card has eliminated the "blue shards" in the scenery when tessellation is turned ON. As suspected, it was a hardware/driver issue.

 

Concerning the R6025 error, as always if tessellation is turned OFF it crashes P3D within a few minutes into the flight. Since my issue with scenery is resolved and I am getting decent frame rates with tessellation turned ON the R6025 error is a mute point to me right now. The new video card I just installed (and many of you I suspect have even better) provides excellent performance on my system so in my case if I get 30+ frames or better I could not be happier. Theater projectors show movies at approximately 28 fps, the human eye can only see so much, as for the rest oh well. P3D running on my older system is purring like a cat with better than "normal" settings.

 

BTW, the new video card I installed is capable of using the new PCI 3.0 specs but my older motherboard is only PCI 2.0 specs limiting the bandwidth but any loss is negligible. Maybe one day I will cough up the dough for a new motherboard with matching specs and get a second video card to run in SLI, OMG the debt! Still I cannot complain I got a sizable discount on the new card, which cost me less than two bills to save my investment in P3D. I have not got to it yet but I am also interested in what difference, if any, the new card has on performance when using FSX?

 

My next step is to start loading up my addons carefully/methodically testing P3D as I go. I want to see if I experience any of the other issues ya all have discussed such as with FSUIPC (it will be one of the first loaded) since replacing my video card. I do NOT foresee any additional issues at this time (just a gut feeling).

 

Best of success to everyone in sorting out the R6025 error in addition to the "Could not write value complete to key..." error during the installation of P3D, here is hoping someone at LM has the passion to hunt down the source of these issues whether or NOT P3D is the cause (again in my humble opinion these issues are beyond the end users reach). I for one will be very reluctant to fork out the bucks for future P3D revision levels (2.0 to 3.0 to 4.0…) without this being resolved.

 

Cheers!

I had R6025 a couple of days ago, never seen it before, vanilla P3Dv2.4 stock Baron, Win8.1, no addons at all. I had just loaded a saved flight, which was saved in the paused state, in v2.4. The flight loaded up paused and appeared OK ready to go. I left the room for a few minutes, came back and found that R6025 crashed P3D. License run out yesterday, so I'm listening...

Hi SteveW,

 

If you haven't visited the LM forums you might want to keep an eye out there also, same topic concerning R6025.

 

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=8564

 

Regards

Cheers! Seems like maybe anything might appear responsible for it.

Again we have to track down why it happens to just a few and not to everyone who owns P3DV2.4 or 2.3. Unfortunately it does not happen to everyone or else LM could track it down.

 

Best regards,

I was paused when I got the error - avoid pausing!