Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
We are not talking about xbox running playstation games, I never said they could. We are talking about bioshock working fine in Windows10, we are not talking about trying to get it to work across differnet platforms, its a windows game and it runs in windows 10 fine.
You seriously saying that people shouldn't even try to run any game that doesn't have Windows 10 as a supported OS? You must be extremely young, because PC Gamers have been running games on "unsupported" OS's for years now, I am still playing DOS games on Windows 10, have a Windows 95 game working right now. In the 25 years of PC gaming, this is literally the first time I had an issue getting a game to run on a new OS, and the only reason that happened is because I have no doubt there is something wrong with the Upgrade Path of Windows 10, but a clean install of Windows 10 works great even for older games. But according to you I shouldn't even try to play any of my older games over the years when I got a New OS, despite the fact they worked just fine.
Well this just clears up everything, you are clearly a young person who has simply has no clue, which explains your attitude.
I wish you well, but please stop posting incorrect information, your not helping anyone.
Check your settings or administrator rights.
1. I verified the integrity of my games cache,
2. I went to my steam library in file explore and turned off Read only for the whole bioshock folder
3.I found the Bioshock.exe file and ran it with administrator priviliages
4.I run a crossfire set up so I disabled crossfire
After step 4 it was working no problem :) (I tried running the game after each step but it did not change anything until I disabled croosfire, so I have no idea if the first 3 steps even did anything but thats what other people recomended to do so tried it) I hope this helps anyone with the same or a similar problem.
My Specs:
CPU: AMD FX-6300 Black Edition OC 4.5 GHz
CPU Cooller: Hyper 212 evo
MB: ASRock 970 Extreme3 R2.0
Memory: Corsair Vengeance Pro 8GB (2x4GB) DDR3 1866 MHz
GPU: 2x MSI R9 280X GAMING 3G core OC-1200 MHz memory OC-7200 MHz
PSU: Corsiar CS750M (750W)
Look this diagram:
[.....................DOS...........................] Everything had to be built from scratch
[.........................|.............................] (All games had their own screen management)
[.................Windows 1.x...................] Based on DOS kernel, no toolkits yet
[.........................|.............................] (No changes for games)
[.................Windows 2.x...................] Just a revision of code, still DOS based
[.........................|.............................] (Some games companies started to be famous)
[.................Windows 3.x...................] Jumped from 16 to 256 color display, still relying DOS
[................/...................\..................] (Even on DOS game devs made good 3D games)
[....Windows 3.x....Windows 3.x NT....] Forked in two technologies which NT was 90% better
[..............|........................|...............] (3D games revolution started, openGL)
[.....Windows 9x.........Windows NT.....] Changed to 32 bits memory address, NT still better
[..............|........................|...............] (DirectX and Direct3D born against openGL)
[.....Windows ME........Windows 2k.....] ME technology was obsolete and was the last release
[..............|........................|................] (Direct3D broke some compatibility layer)
[....(discontinued).....Windows XP........] New business model, new colorful GUI
[...................................../.................] (DirectX had huge improvements)
[................Windows Vista.................] Hybrid window management WDM, resource eater
[..........................|............................] (Two screen buffer was used to maintain compatibility)
[..................Windows 7.....................] Old model ditched(GDI) and WDM fully implemented
[..........................|............................] (DirectX had some fix and improvements)
[..................Windows 8.x..................] Testing new GUI, strange and dysfunctional for devs
[..........................|............................] (Nothing special at all, just shoot oneself in the foot)
[.................Windows 10....................] Recovering from shoot on own foot
[.......................................................] (Biggest improvement of all time on DirectX)
That's way too simplistic. If you are part of the Developer Program you will see there are TONS of Kernel Changes, and lots of Graphics Library based changes.
Yes and no, we are talking about 30 years of software compatibility, when they changed from GDI+ to WDM, some old drawing model games broke and when turned the base system unicode some script based games broke too; the developers just did this games once for their fun(and money) and not was intended to be a "rolling release" software like linux; in other words it's more expensive to maintain software than develop new one.
Who develop to Windows since 95 never touched the kernel, it's against the law of closed source code, nobody knows what is inside the kernel code and because that Microsoft developed DirectX API, in DOS era everybody was free to access hw directly which was good for devs and bad for security(I caught once a disk killer virus which came from a floppy disk and infected my hdd, culminating to hdd failure INT13).
The hw access restriction imposed by Windows was to avoid DOS viruses, protecting users.
From DirectX1 to DirectX 5 the coding was the same because hw only had speed improvements, the hw paths was PCI or AGP.
From DX6 to DX11 happened most changes making some sw stop working because the texture mapping and shaders, many codes was turned obsolete and the hw changed to PCIEX, built in memory controler which changed chipsets interacion.
DX12 changed to a real multi-threaded calls balancing cpus cores and they gave more freedom to access graphics card too.
And finally, the bug is caused by the faulty programmers, Many years ago I was a pascal/basic programmer and trust me I know how ♥♥♥♥ happens.
SPECS:
win10 enterprise
i5 4690k
16gb ram
z97 sli krait mobo
gtx 960
1x 240gb ssd + 1 250gb hdd
A ♥♥♥♥ tonne of windows tweaks like disabling the privacy stuff.