XMAN

Prepar3D v4 Default aircraft and Install size

Recommended Posts

Will it be the same , or any new planes, also i wonder how big the total p3d v4 file is , i think i only have about 40 gb left , i might be free up 20 gb more

Edited by Poppet
edited Title to reflect question

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Hello,

From the Prepar3D v4 system requirements at the link below you will need at least 40 gigs of hard drive space to Install and run a default Prepar3D v4 and SDK kit http://www.prepar3d.com/system-requirements/

---------------

This is divided as follows 

Your core Prepar3D v4 Install location will have 24.5 (ish) gig's of data when the Install process has completed 

12 gigs of data (Repair Installers) will Install to your Package-cache folder on your C -drive.      C:\ProgramData \ Package-cache

If you intend to Install 3rd Party Software (Add On's) for Prepar3D v4, you will need a lot more space in your Core v4 Install folder

Note:  Even though you may choose to Install Prepar3D v4 on a different drive other then the default C Drive you will still need at Least 12 gigs of space for them Repair Installers.   

  • Upvote 2

Share this post


Link to post
4 hours ago, Poppet said:

12 gigs of data (Repair Installers) will Install to your Package-cache folder on your C -drive.      C:\ProgramData \ Package-cache

I do so wish they'd stop this practice. I have a tiny 256 GB SSD for my C: drive. I ran out of space installing the latest P3Dv4 beta drop, and had to delete the P3Dv3.x cache files to make room. They should allow the user to pick another drive for the repair cache files. JMHO of course.

  • Upvote 1

Share this post


Link to post

Why not get a second SSD drive, brother, just for P3D?

Share this post


Link to post

Hello Bill 

The only way around this is to Install the Component Installers Individually,  Client, Content and Scenery

This way the repair and prerequisites Installers do not Install to the Package-cache folder. 

Note:  This is also means the below Blue prerequisites Installers do not Install to your Computer.  After you Install the components individually the User "might" have to locate and Install these  (If your windows updates are old) 

1) Microsft Visuals 2015 vcredist_x64.exe + x86.exe Version 14.0.23026.0      
2) Direct X Setup DXSETUP.EXE Product Version 4.9.0.0904   
3) Prepar3D Setup.exe Installer                                    
3) Install_Content.msi                                            
4) msxmI6_x86.msi  Version 6.10.1129.0                            
5) Install_Client.msi                                               
6) Install_Scenery.msi   

7) Net Framework 4.6.2 

Share this post


Link to post
4 minutes ago, Boomer said:

Why not get a second SSD drive, brother, just for P3D?

Just a side-note Boomer: you seem to have a lot of brothers😁

  • Upvote 2

Share this post


Link to post
18 minutes ago, Boomer said:

Why not get a second SSD drive, brother, just for P3D?

That would not help. My OS (Win7) and ancillary files are on my miniscule SSD C: drive. This is the default (and only) place where L-M forces the "repair file cache" to be stored.

I have a 2TB drive for all of my sim software.

Share this post


Link to post
17 minutes ago, Poppet said:

The only way around this is to Install the Component Installers Individually,  Client, Content and Scenery

This way the repair and prerequisites Installers do not Install to the Package-cache folder. 

Yes, that is one "work around" but as you have noted, not without it's own set of issues.

L-M already allows the user to specify whatever drive/path to install the program, so why not allow the user to specify where the Package Cache should be archived? Alas, my pleas from years ago during v1 beta testing apparently fell on deaf ears. :bengong:

Share this post


Link to post

Hi Guys,

Sorry to drop in on the conversation but what about the third party addons LM now requires you to install outside the SIM. I saw a video showing the C:\ Drive- Documents Folder. Is it that having your sim on separate SSD's is now something to consider?

Share this post


Link to post

Get a new, larger SSD... clone your C drive to and and swap.

Share this post


Link to post
16 hours ago, MarlosB said:

Hi Guys,

Sorry to drop in on the conversation but what about the third party addons LM now requires you to install outside the SIM. I saw a video showing the C:\ Drive- Documents Folder. Is it that having your sim on separate SSD's is now something to consider?

You can move whole Documents folder to the different drive, use symlink that points to the Prepad3D addons folder on the different drive or even add additional location to store the addons (this is nicely explained in the docs).

Share this post


Link to post
On 5/30/2017 at 6:05 AM, WarpD said:

Get a new, larger SSD... clone your C drive to and and swap.

So its ok to put both OS and P3D v4 on the same ssd? Why do most people split it, does it have anything to do with SPACE or Performance?

Share this post


Link to post

With an SSD it would have to be space more than anything, though performance is still something to consider.  However, this isn't about installing Prepar3D on the OS drive, but rather how addon discovery in v4 requires some space in the Documents folder.

Share this post


Link to post

Poppet,

I also have a rather small SSD C: drive as well. What will happen if I move the Package-cache folder temporarily to a bigger drive, and transfer it back when a P3D repair will be needed? WIll that be a kind of "work-around" to save space on my C: drive?

 

Thanks,

Hans

Share this post


Link to post
On 29. 5. 2017 at 6:43 PM, n4gix said:

I do so wish they'd stop this practice. I have a tiny 256 GB SSD for my C: drive. I ran out of space installing the latest P3Dv4 beta drop, and had to delete the P3Dv3.x cache files to make room. They should allow the user to pick another drive for the repair cache files. JMHO of course.

This is Microsoft practise, you can repair/mod installed sw from Install programs window. Anyway, you can clearly delete those cached installers. But for repair/modify you have to use original installer

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now