Windows 10 killing Nvidia hardware.

[Purr4me]

Huh ?

Kinda late...in the game, there more required but I'm sharing the news as it just took place.

http://steamcommunity.com/app/377160/discussions/0/496880503083101500/

you need steam account to read most of the data.

[Purr4me]

add on information to windows 10 missing assets the game "fallout4" requires and are not present.

Available to windows 10 are sets. some graphics drivers also require these assets to be online in order to even talk to the game engine.

https://msdn.microsoft.com/en-us/library/windows/desktop/hh802935%28v=vs.85%29.aspx

 

research using the threads posts and using NT-core cff explorer leads to this. I copied the launcher to a folder on the desk top and kept placing the resource files into the same folder and re-verifying the data left "missing" most of the missing data is 32bit...so th4 Assembly of the game used older resource files and newer ones...the missing 2 gigs from the advertised size of the game

Example

http://s26.postimg.org/hbiodrxjd/Wapi.jpg

 

Source

https://www.visualstudio.com/en-us/downloads#d-express-windows-8?CR_CC=200395106

Reason

https://forums.geforce.com/default/topic/514876/missing-dependencies-windows-8/

 

self explanatory.

Edited November 13, 2015 by Purr4me

[Purr4me]

OK, after some really mundane research , I found out what's up with windows 10 and fallout 4 issues in whole, another reason other than security and signatures.

 

I was dumb founded by what I read. Tests reduced amazing results for which I have yet to conduct. 4 hours ago, I copied My Entire 64bit laptop windows 10 steam folder over to my book extended drive, then I hooked into My windows 7 32bit system.

 

Why? running the dependency walker of both version 32 and 64 on 10 produced exact same results there , hundreds of missing API's sub modules 32bit from reading the fallout4.exe.

 

Now on 32 windows ,a work station system, ran the x86 version of the dependency walker program on the engine directly in steams folder.

 

I find only 6 files missing only the 64bit parts are missing. All api's seen missing on 64bit os are here on 32bit.

 

conversions of the product popped into my mind as to what was used to produce such a mess, that led me to a very interesting page.

Ignore the posts under the main material on this page (http://www.techsupportalert.com/content/how-windows7-vista64-support-32bit-applications.htm)

 

what's most important on that page is this Entry / paragraph.

 

Which runs faster 32-bit or 64-bit applications?

This question is asked a lot and there is no general rule because it depends on the application and which CPU features they use.

If we compared 32-bit and 64-bit applications in their native environments then 32-bit application usually use less memory than the equivalent 64-bit application because 64-bit versions use 64-bit values so they take up twice the space. The extra size affects the application startup and shutdown times and other activities that involve accessing the disk drives. Usually this means that the 32-bit application will run faster but 64-bit applications can access new and faster features in the 64-bit CPUs potentially giving improvements of up to 25% in processing speed.

Once both 32-bit and 64-bit versions of a program are running on 64-bit Windows you have to ignore any performance on a 32-bit CPU. The 32-bit application now requires WOW64 to run so that should be included in any performance comparison. This means you need to include all the duplicated resources used to map the 32-bit application to the 64-bit environment it runs under. Duplicated resources are used for memory mapping and redirection of files locations and registry entries. The result is that the 32-bit application uses more memory and runs slower than on an equivalent 32-bit CPU but it may still be faster than the 64-bit application.

 

How Windows 64-bit Supports 32-bit Applications

Submitted by Remah | Last update on

2nd May, 2015 - 5:52am

6 months later we have a release of a game stated for strictly 64bit systems ,but hype claims the Project was started long before this date.

 

this is 2015 Nov...and all the hardware to date have changed sense inception date of the game, but the basics have not. The above paragraph does show that there was lapse's in judgements over at the Studios.

 

so I have yo wait for all my data to trans fer to the book, 555GIG's worth. before I can conduct a VM tests, possibly Copy the 10 files into the VM copy of the stem folder and Just see what that program finds.

 

Program systems "Verify" on an AMD shows clean game files, no missing data for graphics, this one is radon. a cool match to said requirements.

 

Windows 8 did not contain any Elements needed for game so it was flop, even retracted from use for a small time, then history shown that 8.1 was slightly better , but IT lacked enough support for games , every one went back to 7.

 

This research confirms the allegations of that fact...and the why of it all too. this time a finger has been put right on target, this game Fo4 should not have been released in this way....too many variables built into to release of the game and the game useless to 88% of the user base.

 

So, the bottom line was to sell software ."MS" software. Gee, how about that.

 

I think this is about as much i can do for a while.

 

Kitty Black.

[Purr4me]

And in other news !

http://www.forbes.com/sites/erikkain/2015/11/13/the-5-biggest-problems-with-fallout-4/

$750.000.000 not bad so far, now if they invest some of that cash into real programmers expertise and across the board graphics adaptations that work? we will have a game and compatibility that is best for all including the publishers..they then could stand tall.

 

as the page writes, it's a buggy mess..even still $750.000.000 is a lot of cheese !

 

Confirmed issues I identified:

http://www.extremetech.com/computing/218570-windows-10s-broken-fall-update-removes-user-installed-applications-without-asking-first

Edited November 25, 2015 by Purr4me