9 hours ago, tooting said:

I'll admit I'm the biggest moaner on here

Not even close. It's a long line and you're nowhere near the front. Don't try to line jump.

BTW, thanks for all that work you did with models and databases in UT2. Super-duper UT2.

8 hours ago, Nemo said:

If you still have P3Dv3 on your system, you probably uninstalled the v3 client. That's what happened to me.

...Me too! Hahaha!

6 hours ago, kevinfirth said:

Are you on win10?

I thought I'd removed the client through settings but I hadnt really.

In win10 apps settings right at the bottom there is a hyperlink to the real programs settings.  Win 10 had allowed me to remive it from the Apps list (each app has a confusing 'uninstall' option) but that had NOT uninstalled it from the programs settings!

After I uninstalled the client through there everything then went as planned...

Thank you Kevin will check into that when I get home this evening. Very possible since I have W10 W/Creators ed.. This wouldn't surprise me a bit.. I appreciate the assistance from everyone too.

Well, update to my situation; no joy on all accounts. Definitely had V4 Client removed V3 was still intact and functional. Went ahead and did the dance. Removed everything from V3 first then V3. Had a few hiccups here with glass fonts stuck in memory, eventually got those out and deleted. Next attempted removal of V4 A2A aircraft only to find none had install.log files and I have no idea where these would have resided. Did the O'l manual deletion process there. Next ran the uninstaller for V4 Content and Scenery then the V4 Pro uninstaller. Manually deleted all associated folders APPDATA & PROGDATA as well as physical folder locations for both V3 & V4. Afterwards, ran CCleaner to remove hung registry references and clean out other deletions. Too frazzled at this point to reinstall will leave that for tomorrow evening. Time for a cocktail and some stress relief.. 

We shall see what tomorrow brings! Though, I am still a little worried about my A2A V4 installers.

On 6/28/2017 at 0:13 PM, steve40 said:

Between steps 2b and 2c, you forgot to turn off the tap after filling your kettle, so now your kitchen is flooded :)

You could have at least pm'd me, mate. It took me two days to notice your post, so now the lounge room is all wet, and the carpet is ruined. Thanks a lot. 

11 hours ago, Pivot said:

Well, update to my situation; no joy on all accounts. Definitely had V4 Client removed V3 was still intact and functional. Went ahead and did the dance. Removed everything from V3 first then V3. Had a few hiccups here with glass fonts stuck in memory, eventually got those out and deleted. Next attempted removal of V4 A2A aircraft only to find none had install.log files and I have no idea where these would have resided. Did the O'l manual deletion process there. Next ran the uninstaller for V4 Content and Scenery then the V4 Pro uninstaller. Manually deleted all associated folders APPDATA & PROGDATA as well as physical folder locations for both V3 & V4. Afterwards, ran CCleaner to remove hung registry references and clean out other deletions. Too frazzled at this point to reinstall will leave that for tomorrow evening. Time for a cocktail and some stress relief.. 

We shall see what tomorrow brings! Though, I am still a little worried about my A2A V4 installers.

Hi there,

What I usually do at (any) LM P3D release is:

1. Downloading the full installer.zip
2. control the checksum and unzip
3. uninstall (from Win10 Apps & features, not from CP) LM P3D client, content and scenery, ONLY these components and NOT the main install
4. install the new client, content and scenery components from the .msi in the unzipped folder of point 1.
5. reboot
6. delete P3D shader cache
7. delete Prepar3D.cfg and fire-up P3D in order to have it rebuilt, customize my settings from scretch
8. update FSUIPC to last version
9. update AS16/ASCA to compatible versions
10. deal with the rest of the addons.

Maybe a bit time consuming but effective: never had a single problem.

Good luck and happy flying,

1 hour ago, ffantasy67 said:

Hi there,

What I usually do at (any) LM P3D release is:

1. Downloading the full installer.zip
2. control the checksum and unzip
3. uninstall (from Win10 Apps & features, not from CP) LM P3D client, content and scenery, ONLY these components and NOT the main install
4. install the new client, content and scenery components from the .msi in the unzipped folder of point 1.
5. reboot
6. delete P3D shader cache
7. delete Prepar3D.cfg and fire-up P3D in order to have it rebuild, customize my settings from scretch
8. update FSUIPC to last version
9. update AS16/ASCA to compatible versions
10. deal with the rest of the addons.

Maybe a bit time consuming but effective: never had a single problem.

Good luck and happy flying,

Thank you Massimo, I think you have the correct approach. The easy way never seems to be the easiest in these things, especially when dealing with Windows. I appreciate your insight and will heed your advice on the next debacle. 

1 hour ago, ffantasy67 said:

Downloading the full installer.zip

1. control the checksum and unzip

Well, why would I do that? If a ZIP is corrupted it will fail to unzip :-)

23 minutes ago, swiesma said:

Well, why would I do that? If a ZIP is corrupted it will fail to unzip :-)

You cannot complain with traditions, I feel neat when checksum matches 

Cheers,

29 minutes ago, swiesma said:

Well, why would I do that? If a ZIP is corrupted it will fail to unzip :-)

Dear Avsim, I think you're overthinking things.

Seriously, 12 pages on how to install a hotfix?!?

I mean, it's literally: uninstall P3D v4 client, download and install new P3D v4 client. If that doesn't work, uninstall all of P3Dv4 program , download and install new P3D v4 full program.

I'll pop back on page 22 and post this again.   

Hello All,,

Hoping someone could clarify something re: applying the P3Dv4 Hotfix. On the Prepar3D website, referenced in the initial message of this topic thread, it indicates that P3D will need to be reactivated, In the moderator's note section in the same message, it indicates that the reactivation step may be bypassed.

Just trying to be ready for when I start the update.

Thanks,, Mike

<edit> 

see instructions in my previous post.

if P3d wants you to reactivate, it'll tell you.

 

3 hours ago, OzWhitey said:

Dear Avsim, I think you're overthinking things.

Seriously, 12 pages on how to install a hotfix?!?

I mean, it's literally: uninstall P3D v4 client, download and install new P3D v4 client. If that doesn't work, uninstall all of P3Dv4 program , download and install new P3D v4 full program.

I'll pop back on page 22 and post this again.   

Well, you see - that's the dilemma of a forum thread. In a perfect world every member would READ the thread first to find the answer before posting a question. However, this is not a perfect world so threads develop a life of their own and unless they get completely out of hand, die a natural death.

To YOU  it may now be a meaningless long thread, but to a newbie it could be a good source of information. That's also the reason we do not delete threads - think of the disk space we could recover!!

See you on page 22...... 

 

Vic

 

22 hours ago, vgbaron said:

Well, you see - that's the dilemma of a forum thread. In a perfect world every member would READ the thread first to find the answer before posting a question. However, this is not a perfect world so threads develop a life of their own and unless they get completely out of hand, die a natural death.

To YOU  it may now be a meaningless long thread, but to a newbie it could be a good source of information. That's also the reason we do not delete threads - think of the disk space we could recover!!

See you on page 22...... 

 

Vic

 

Hey Vic, just to be clear I'm absolutely not saying the the thread should be shut down, if people are having fun discussing something meaningless on the internet, well, that's pretty much what most of the internet is for! 

Of course, if you were to discuss download speeds/% complete for 6 pages, some random mod would probably come along and nuke the thread. 

The point I'm arguing - as per the 'how to boil water' post etc - is that we're making an extremely simple process that takes a couple of minutes and is easily within everyone's tech abilities, sound far more difficult than it is by writing complex and often contradictory instructions. When we start to talk about checking the .zip checksum before step 3c or whatever, it going to put some people off applying the fix, and others will be dissuaded from moving to P3D at all because the 'constant updates' are perceived as being too arduous.

Just my opinion, but i'm encouraging any on-the-fence readers to get the hotfix, read the paragraph on the LM download page and then invest three minutes of their life getting up to date. And if you're a FSXer who is thinking this P3D thing may all be too hard, don't worry, it's not. Get v4+hotfix, and get back in that 64-bit air! 

1 hour ago, OzWhitey said:

Just my opinion, but i'm encouraging any on-the-fence readers to get the hotfix, read the paragraph on the LM download page and then invest three minutes of their life getting up to date. And if you're a FSXer who is thinking this P3D thing may all be too hard, don't worry, it's not. Get v4+hotfix, and get back in that 64-bit air! 

Actually I agree with you but in practice, it's something we have to live with. There are some people, when asked the time, will tell you how the watch works - others will tell you the time. I agree a newbie could get really confused by some of the unnecessary detail.

Vic