Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Hozzászólási szabályok és irányelvek
Hozzászólás jelentése
"Setup aggregate ports" I doubt your switch will even do LAG or port-group / port-channeling, if you believe just plugging in 4 cables == link aggregation you are wrong severely.
I don't feel like explaining in length why or why not, I'm not paid to help you.
Set the NAS as a Networked Drive with Drive Letter. Select this in Steam settings. Its that simple. Make sure any PC doing this on the Network has full Write privileges (not Read-Only) or it won't work.
The error I get: "New Steam library folder must be on a file system mounted with execute permissions."
FSTAB is as follows
/IP/Games/ /media/Games cifs Credentials,uid=1000,gid=1000,iocharset=utf8,dir_mode=0777,file_mode=0777
It mounts fine and I can add and delete files just fine. I even created a whole new empty folder and it still doesn't work.
My 'Home Server', an older machine has proxmox installed, which is a pretty good & free hypervisor.
On there is a Truenas VM (with the games backup and other data), windows 10 and a lancache server.
The games are updated/downlaoded nightly through the lancache to the ISCSI drive. My backup is then up to data. Games downloads are then very fast.
Oh and also pfsense router, pihole, ubuntu linux and a few other useful things.
I tried windows for storing games awhile back, but was highly problematic.
That is an interesting concept. I am however am trying to move from windows to linux and I wanted it to be set up the same way it was in windows, only in linux. Kind of sticking it to the man by doing everything I can do on windows in linux instead.
Any and all advice is appreciated though.This also could turn into my next project lol
My setup typically means i use windows for gaming purposes only, and are on windows for a minimum amount of time where games updates are from the lancache Virtaul machine.
So no web browsing ,except maybe drivers on windows. Just updates & games.
Oh and posting on forums like this when waiting for a game server.
As for using linux for games, the biggest issue are the DRM & anti cheat.
I am hoping due to steamdeck, will be forced to play nice with linux.
I am sticking with windows (10) for games for now. I hope it is 100% doable on linux before support ends.
Basically there are few different ways how disk IO may happen:
1. Load big files / assets from disk to scene in memory: This is probably the most common way to access disk, since games knows that this way of accessing data is fast. You should be able to get data 2x speed compared to SATA SSD.
2. Load / access lots of small files: This is actually harder, since on every operation has the starting overhead. Though if game does not wait that the earlier small file load is ready before making the next one, then game can just launch 10000x parallel file operations to the NAS and again you will be able to use the full capacity of the 10Gb network.
3. Random read/write access to a single file: This is not so common operation with big data amounts, so probably amount of data written is small and you will not notice any problems. Though this is the one of the hardest workloads for network drive.
4. Sequential access to files, where next access pointer depends on the earlier data which was read: Pathological case where your network drive will not perform well.
So people are saying that there is a huge overhead in file access through network drive, but actually the overhead is few tens of microseconds per access operation, so when big files are loaded from the network, performance will be good. Though is one compares it to NVMe SSD:s then it will be always a lot slower compared to them.
each access on a hdd or ssd is in a few ms or less
adding network link will increase that time by huge amounts
If something like RDR2 or TotalWar Warhammer then it's much preferred to install to local SSD.
Games like God of War, The Last of Us, Horizon Zero Dawn, Tomb Raider 2013 (or newer TR) play just fine via NAS.
I've used this option for Steam Gamea since Win7 was the everyday OS.
If it's a game where you mod the story and such, much easier to handle that via local drive IMO
I can tell you from experience there is no difference except the fact that EA games and UBI Soft games will not work. Also anything with Anti-cheat because it doesn't like it. I have been running it this way for about 4 years now.
If using windows sharing, it will cause many issues.
ISCSI drives are the way to go in that situation.
I did think about something similar.
I have 2.5 gigbit local lan speeds. This is apparently fine for now, due to the local cache setup.
Frequently accesses data is accessed at nvme speeds.
As for writes, the cache uses a delayed write option, so are written to the NAS a little later. This is typically when gaming and do not notice. Its seems to top out at 200 MB/s write speeds. I know this through the task manager & viewing the ethernet speed.