安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
To do what? Kill raiders? There's Borderland, Doom, any number of FPS' that allow you to do that *and* do it better than FO4.
To 'quest' together? There's really no questing here. There's no decisions to be made other than 'do I kill raider A or raider B first?' Most of the quests are 'go over there, kill something, come back'.
There are other games that do all that and do it better. What would coop bring to this game? That's something you guys pushing this always talk out your arse about how 'easy' it would be to implement - hint: Its a sight more complicated than you think - but never why it would make the game better.
Bethesda absolutely cares what its customers think - that's why FO4 is the way it is. They bent over backwards to give their customers what they wanted.
But they care about what the *mainstream* of their customers think, not the fringes.
The problem is: It can't be easily done.
In every MP/Coop game the client synchronisation is one of the hardest parts to do.
Since FO4 and it's engine aren't even made with this part in mind, it's even harder.
I think we can cut out a server based option (too time consuming/expensive to develop and maintain).
Leaves a P2P network.
One machine would have to act like a "server" who tells which objects are there, their movement and position. This and much more information (player and NPC stats, HP, AP....) has to be sent to the other computer...close to realtime. This computer has to place and render and move the objects according to the information he gets.
Most of the time UDP is used for this in games, so no error checks in the communication.
The "client" has to do some kind of prediction what happens next if some network packets are lost.
It would end up unplayable, or at least not really enjoyable, due to connection loss, rubberbanding, timewarping and other annoyances we know from almost every online game in their early stages.
Like i said before: The game is not made with networking in mind and therefore not optimized for it, making realtime communication almost impossible to do.
THis is only ever talked about by a select group of fans. Bethesda is not talking about it and certainly haven't scrapped an idea they aren't interested in trying. Its only 'scrapped' because people like you have no control or ability to do this and wishing it into being has not worked so you all move on until someone else posts another BS thread like this and the cycle of wishful thinking/dissapontment starts all over again. Get rekt.
ironically fo4's story was predestined to be coop, 2 parents looking for their son.
might not happen but i am allowed to dream.
I already tried to explain why it won't be done for FO4.
Come back with an idea that might work technically.
I'm not trying to troll... just working in IT for 25 years with main emphasis on networking.
I don't think you have the slightest clue what making a game "multiplayer" is about.
Google the terms UDP and TCP... it should keep you occupied for quite some time.
And if you don't get why you should do it... you really have no clue about what a game/engine can support and what not.
Ok, lol. But Zenimax Online was headed by MMO industry veterans who had made good games before (like Dark Age of Camelot); meanwhile Bethesda hasn't made a multiplayer game since, what, SkyNET?
Nah it was Zenimax Online, a subsidiary of Zenimax (who also own Bethesda).
Add in the fact that Creation can only check on one player at a time (the player is a singleton whose script refuses to let other players get loaded for CPU-sake) as well as the fact that the engine features no workable netcode of any sort, and the long and short of it is that a non-Bethesda Fallout game on a non-Gamebryo-based engine would have to be made before the series could ever feature co-op. Obsidian (the company that series creators JE Sawyer and Chris Avellone work for) refuses to work with Bethesda again over the botched handling of Fallout: New Vegas, so pretty much it's either how Todd Howard wants to do things, or someone creates a Mighty No. 9-like spiritual successor to Fallout with co-op in mind.