10 minutes ago, JonP01 said:

Why not if it is a brand new installation they are talking about? This is not an installation that is tailored with add-ons that would either confuse the algorithm or stuff up a working installation. It is an out of the box install they are trying to get working in the first place. I don't think any harm can come by it in the OP's situation but if you differ then at least please provide a technical explanation as to why.

The Steam file integrity check will happily verify the files that the Steam client actually downloaded. And then it will happily delete the 100+gb of files that the sim downloaded because Steam knows nothing about those files.

As mentioned, don't do it.

If you do, the next time you start the sim, it will have to download ALL the files that were originally downloaded. Unless you have a full backup and can restore those files prior to starting the sim after doing an integrity check.

...jim

 

The program crashes for him so is unusable.  Why not try running the verify.  Sure it will take time for the download and install but what does he have to lose.

9 hours ago, Dominique_K said:

that your CPU is below the minimum specifications doesn’t help

Not really, I just recently updated my cpu coming from a i7 3770K which handled MS2020 quite fine, of course my frames were set to 30 but still, it did a great job considering it's a 9 year old cpu.

Considering your plight, go ahead and verify, then take a long nap.

2 hours ago, BBCM said:

According to reports on the Steam MSFS forums, using "verify files" deletes the entire MSFS install.

I'm sorry I don't have a link, but you can find using Google with:  Steam MSFS verify files   

Thank you. A much better response than simply saying don't do it with no explanation as to why though in this case I am not sure the OP has much to lose given they could spend days or weeks in frustration. Probably better to try it anyway since as I said they do not have any additional content to "lose". They just want a working out of the box install.

Edited December 28, 20214 yr by JonP01

Wow, my topic generated lots of good advice. 

Background:  I've been reading horror stories about MSFS ever since it was released.  So I thought I'd try to load it on my one lung machine just to see what it looks like. That didn't work as is obvious by my initial entry in this thread.  I suspect that one of many files downloaded over the night is corrupt.  I also think it would take way too much time to determine which file is broken so I'm not going to do it.  I know that if the sim did run, it would not perform well enough for me to enjoy it. 

I must say that the developer seems to have his head up where the sun don't shine when it comes to the download.  I was looking for the essentials since I'm relatively experienced in simming and a real world pilot (retired) so I thought it would be nice if the developer just gave you the essentials in the first install.  I don't need the tutorials nor do I need all the aircraft he shoves at me since I fly mostly PMDG simulations, especially the C-118.  

I'm going to research the situation some more but If I can find the problem quickly, I'll shoot the SOB and try again later after I've treated myself to a new machine.

Semper Fi,

Jim Driskell

11 hours ago, anden145 said:

For God's Sake - I'm NOT debating whether or not, the Core i7 Ivy Bridge is SUPERIOR to a Core i5 Haswell Bridge!! All I'm saying, is that the architecture is different (it's older!), which is why it fails to meet the requirements of MSFS, as they REQUIRE (when it comes to Intel CPU's) a 4th-gen CPU at minumum.

The architecture is the same, what are you talking about?

3000 series were neglected only due to their age, MSFS can run on a 2600K as well. Once OP resolves his issues with the installation and setup it will work, you'll see.

 

all this discussion over the CPU, but I wouldn't run MSFS with less than 16gb ram.  Windows by itself loves its memory.

Edited December 29, 20214 yr by Isaiah53six

21 hours ago, JonP01 said:

Thank you. A much better response than simply saying don't do it with no explanation as to why though in this case I am not sure the OP has much to lose given they could spend days or weeks in frustration. Probably better to try it anyway since as I said they do not have any additional content to "lose". They just want a working out of the box install.

Because it's been said many many times, at least two other threads within just the last week. I'm sorry I was short with my answer.

Running Steam verify files is a good way to start a complete reinstall. You could of said to the OP that they have nothing to lose, so try a complete reinstall. You didn't, you said to run a verify file integrity which sounds like something simple (and with most Steam games it usually is). With MSFS It will cause a complete reinstall. Many of us have experienced it personally, myself include. So for the last year since that I've tried to warn as many people as I can about it.

Never, Never, run steam verify files with MSFS!

Edited December 29, 20214 yr by Phantoms

53 minutes ago, Phantoms said:

Never, Never, run steam verify files with MSFS!

Well, that's interesting.  I did run the Steam verify and then tried to start MSFS again thru Steam and it downloaded a 53.35 MGB file.  No where the size of the 125 GB file that initially downloaded.  MSFS still didn't run.  Looking in \Users\me\appdata\roaming\MFS I see a rollingcache.ccc 8.3GB file and an error file saying that it can't open a number of ac files that I don't have.  App crash file shows a access violation file by the flight simulator.exe which seems to be followed by a kernal violation file.  I'm pretty sure that initial download is corrupt so I'm going to clean up my machine and then do something productive unless someone can point me in another direction.

Thanks for everybody's  input on this problem

Jim Driskell

2 minutes ago, jmdriskell said:

Well, that's interesting.  I did run the Steam verify and then tried to start MSFS again thru Steam and it downloaded a 53.35 MGB file.  No where the size of the 125 GB file that initially downloaded.  MSFS still didn't run.  Looking in \Users\me\appdata\roaming\MFS I see a rollingcache.ccc 8.3GB file and an error file saying that it can't open a number of ac files that I don't have.  App crash file shows a access violation file by the flight simulator.exe which seems to be followed by a kernal violation file.  I'm pretty sure that initial download is corrupt so I'm going to clean up my machine and then do something productive unless someone can point me in another direction.

Thanks for everybody's  input on this problem

Jim Driskell

If you didn't pick up another 50 or 60 gigs in the content manager, you did not get the whole program. When doing a re-install, you get base program files in the original download, but the rest of the content available to you has to be downloaded from the content manager. Sorry, but your not using the entire content. (reason for missing aircraft files)

That's what I thought.  I'm going to scrub the machine and try again.

Jim

6 minutes ago, jmdriskell said:

That's what I thought.  I'm going to scrub the machine and try again.

Jim

I did all this just last night, trying to get the SWS Kodiak to run. Just to find out today, the problem was with DX12 not MSFS or graphics setup.

I have seen messages saying that running Steam verify did not download large chunks because they had MSFS installed out of the default location. They said this is one of the many advantages of not using the default location.

You aren't really moving any files when you change the location of MSFS. Just changing the files' paths (assuming you still are not moving to a new physical drive). Having done it once and learning how, I could move it again in 2 or 3 minutes. You don't have to edit any .cfg files.

I don't remember seeing any messages asking me where I wanted the bulk of MSFS installed.  I assumed that Steam would put it on my SSD where Steam is and where FSX-Steam is but the installer put the bulk of the files on my c drive which would probably make the whole system run very slowly.  So far, my opinion of MSFS seems to correspond with many of the horror messages that I've read elsewhere.  We had an old saying when I started working with main frames in the 1960s, "Software sells hardware!"  MFSF falls into this category because it sure has made lots of folks upgrade their hardware in order to run this application.

I'm done for a while until either I build a hefty new machine or buy a Cray!

Jim Driskell