2K,please make patch to Bioshock to run on Video cards with Pixel Shader 2.0.I log in pettition,but where is PATCH.I like buy and play this great game.I WAITING FOR THIS PATCH!!!![]()
2K,please make patch to Bioshock to run on Video cards with Pixel Shader 2.0.I log in pettition,but where is PATCH.I like buy and play this great game.I WAITING FOR THIS PATCH!!!![]()
I R Angry :d
There are a set of community-produced fixes that add a degree of Shader Model 2.0 support to Bioshock. They're not perfect, but they're pretty good for a game that isn't supposed to run the game at all.
Me Tarzan ! You Jane ! Ough !!!
Go to the directory where your bioshock is instaled and find a file name default.ini . Open it with notepad and go to the bottom. There you will find a line wich says HighDetailShader=True. Replace the True with False and voila ! Your pixel shader 2.0 works ! Also... if you have have nvidia go and download the latest BETA drivers and install it (till yestrday it was 169.09) http://www.nvidia.com/Download/betad...spx?lang=en-us
And hopefully everything will be ok now.
Hmmm... after some more research I don't know if my above suggestion will work...but what the heck !!!! Doesn't hurt to try !![]()
2K why you not respect users and players.We need PATCH!!!
go to http://www.paolofranchini.com/shshock/index.php really works whit shader2.0 thanks ReverendTed iu are really good people
Yes, load times are considerably extended. This is because we haven't been able to determine how ShaderCache.pcs files are generated, and the development team has not responded to requests for information on how that could be accomplished.
Currently, that's the price of admission for individuals who don't want to buy a new video card.
Well, "inconvenient" is better than "completely unavailable".
I've been keeping up with any action on the forums, but the SM2.0b side of the project is probably as good as it's going to get unless someone with more experience in shader coding comes along to sort out the remaining hitches. (Or if we can get some input on how to generate a ShaderCache.pcs file.)
Flint continues to make incremental changes to his SM2.0 fix, which I've been told looks pretty good on SM2.0b cards, and may rival the last SM2.0b update (AOHv4.5).[/QUOTE]
Nobody should be flappin their yaps about the long load times with the Shadershock fixes.
I for one am very grateful that I'm able to play the game at all.
The guys over there, The Rev included, should all be given medals for their devotion and effort.
Thanks guys.
2K,you are stupids!!!Bioshock is best game for PC.Many peoples like patch to shader model 2.0.I like buy this game.Please make PATCH.I like answer from 2K!!!!!!!!!![]()
Dude they cannot even make a patch for shader 3.0 so don't expect anything for 2.0 shaders cards; just install the ShaderShock thing, it is the only way you'll get your game working (hopefully)
I sure noticed that, no problem dude (i'm french and my english isn't very good either):
http://www.paolofranchini.com/shshoc...640aa2e95c77c0
maybe this one???
You should ask it to ReverendTed, it just might get a proper answer for you (don't forget to make a backup of your shadersfile, eventough it doesn't work)
The Radeon X1050 is an R300 core like the 9600, 9800, X300, and X600.
It is a Shader Model 2.0 card (not 2.0b). You can use FlintFix (1.8 or 1.9beta) or one of Phazz's releases (5th Preview).
Today I came across this patch to make this beautiful BS work (and it is total BS that 2.0 shaders were omitted probably because of pressure from hardware companies). I have 512+ (about eight hundred something) RAM, Radeon 9600, 2ghz AMD Athlon - definitely a weak system.
The patch works with the demo so try it out and get a feel for whether it will work well on your system. Honestly, the shadows don't work at all with this patch - so it's best just to turn them off. I turned off most of the features, medium detail at 1024 - it still looks good and runs very smooth. Be patient, the load times are long - but well worth the wait. Excellent demo! I'm going to buy the game now - thanks to indie hacker developers (I think 2K owes them some money from my purchase).
2K MAKE PATCH![]()
![]()
![]()
This is an Unreal 3 engine game.
It IS NOT 2k's fault.
It is EPIC's fault for increasing the minimum requirements of their engine.
I usually am anti-2k, but asking 2k to go back and rewrite pretty much every single shader for 2.0 (i know it isn't technically that much inferior but work wise it IS a lot of work for 2k to do and they won't do it because there's no money involved. The minimum specs on the box clearly state the minimum video cards required and that direct x9.0c is required).
If you game on a PC things like this are going to happen. Now i do have gripes with 2k over lots of other issues and would be happy to join you in those discussions but this is not one of them as you should take it up with epic over at http://gearsforums.epicgames.com/ or whatever it is.
2k.See the pettition.Over 9000 like buy and play this game.Make patch for SM 2.02k i like answer
http://www.petitiononline.com/BioShock/petition.html
This is petition.Make patch.I am very angry.Make patch and i will buy your game!!!![]()
Do some research before posting. Unreal 3 supports Shader Model 2,3 and 4. This has been discussed many times already and a quick google search will report the same results. If the engine didn't support SM2, then the community patch would not work.
2k...for one reason or another, I suspect it was because of a marketing deal, decided NOT to include SM2....and now they won't even throw the poor folks slaving away on a community fix a bone.
I'm not as cynical as you are on this point.
2k wrote custom shader code for Bioshock (which is where the incompatibility lies) and from what I've seen, it seems that they made the decision not to support SM2.0 or 2.0b out of convenience and lack of perceived return on investment of time\money.
It's not their job to help us out. It might be in their best interest, but they're under no obligation to do so.
Past that, (though I'd think this would be a minor concern) allowing us to generate our our ShaderCache.pcs files might present a predicament from a copyright standpoint if any of the project members decided to distribute a pre-compiled Shader Cache. Being a 13MB file, though, I doubt that'd be the case. We'd probably tell people the commands necessary to generate them on their own, if that were possible.