Battlefield 4

Neznam, vidi da ti netko nije probio wireless i spojio se bežičnim kablom pa ti mjenja program kad je sulejman.

vecu glupost u zivotu nisam cuo.

I na koliko fps ti radi na med/high?

I može ti se dogoditi da te tv ubije iako se čini da gleda u kuhinju!

Jel ti nije bolje na low pa da imaš puno fluidnije zbivanje oko sebe? Meni ode do 140 (i više) i ne pada ispod cca 70 na low.

Otkrili su kakve igrače vole proizvođači igara:

Probao i ja malo izmjeriti fps u BF4 na  1920 x 1080 sve stock.

Mid

Frames, Time (ms), Min, Max, Avg
  8494,     60000,  90, 174, 141.567

High

Frames, Time (ms), Min, Max, Avg
  5522,     60000,  73, 116, 92.033

Da, na golemim mapama sa 64 igrača pada. Pa nemam ja neku aždaju od grafičke niti imam high end CPU, ne?

https://www.facebook.com/photo.php?fbid=674575315894440&set=a.277208758964433.75470.141795922505718&type=1&theater

Za vježbanje hedšatova.

A nisu jos rijesili ni curenje memorije,jucer alt tabam igru i vidim 7.9gb trosi,fijuu puno je  to

Ma ajd,e šta nam je to, skinuti 15 GB... XD

Sigurno yebeno izgleda kad ti preko toga baci nešto tipa "Something went wrong" 

Nego @smiglcro jel koristiš fraps za mjerenje fps-a?

Ja sam u beti imao dropove na 4-5 fps-a i negdje sam proguglao da se baš fraps zna poklat sad ne sjećam se točno dal sa driverima od grafičke ili sa samom igrom(ironično program za mjerenja fps-ova ti ih ujedno ruši),uglavnom isključio ga i drop-ovi nestali,a frend me uputio da fps-ove pratim preko config file-a.

Inače moja kanta tjera od 58 pa nadalje,neznam točno jer sam odmah locko na 60 fps-a @ 1920x1080 sve na high,2xMSAA,HBAO.

Jesi to ti ili nisi to ti 

Imaš 8 GB memorije, a vidio si da ti igra troši 7.9?

Netcode dečki,slušajte lika šta govori:

Hmmm , what fun it seems to be great interest in the network bits :-)

I've actually been working on the dice for 14 + years and can tell you that the frost bites networking engine certainly is something to hang on the Christmas tree :-)

If you compare the amount of information that needs to be sent over between 1942 and BF4 so it _big_ differences. Mostly it is because the added features on the soldiers / vehicles , maybe not number ... a T90 cost tex _much_ more network-wise than a jetski .

Unfortunately , we can not require the player to have obese connections (although we need more now than 10 years ago ) because then many people ( in the world, Sweden may not ) be able to play . If we were to increase the network rate we would cause packet loss for many and then they would get the rubber band problem.

There are no global delays created by someone with high latency, on the contrary , the engine is very tolerant of bad connections.

I can , however, in a way, agree that a player with very high latency can affect the "death experience " for the others in a negative (but not unfair ) way when highpinger kills them. That person can help with "run - around - corner -death " in that he has in his prediction - time shot to death you might 500ms before you learn it ( which means you can control your hubby 500ms wherever you want before you actually dies ) . Again, this is possibly the only solution to not allow such players on the server.

If you have bad connection , you will also potentially experience " oneshotted " more because you may miss some damage or get it too late before you find out that you died .

I may misinterpret the comment " synchronization objects are between clients" but in fact everything except the small non- gameplay - affecting items are synchronized ( and cullas network-wise to keep the bandwidth requirements). A small roadside tex is not synced as it is considered so small that you can not hide behind it. As much as possible is owned by the server to minimize the likelihood of cheating. The whole world is simulated by the server ( all soldiers , vehicles, objects , etc.) while as few things as possible simulated client ( basically only own soldier / vehicle and the small items I mentioned above)

Prediction is the whole reason to " die around corners ." Prediction is, you may check your soldier / vehicle , shoot and steer the client side before the server has approvat you may move you there. Without prediction and with poor connectivity had your hubby not begun to move immediately when you press forward but had to wait until the server says that you move forward. The same applies when you shoot, then had the shot not triggered directly when pressed but instead triggered x ms later when the server notifies you that you shoot .

If you play a game where you have to aim in front of it moving so it has not to do with prediction , but that one does not have client- authoritative hit detection or law -compensated hit detection .. These two also contributes to some " die behind the corner " effects but gives the shooting a better experience. Here it is really a matter of taste which one prefers , to give those who shoot a better experience , or those who die :-)

The " ultimate" experience you have of course the LAN with as much support as possible mechanisms off ( which would give a horrible experience for those with higher ping or lower bandwidth). We have tried to put us on the level that works best given our scope (again , one can not compare the games with few players , few or no vehicles , no destruction , get dynamic objects etc with one that has these things :-))


( I must admit that it hurts me a little bit to hear that you think the network code should be designed in a way that is not 100% focused on making the gaming experience as good as it will go without a single ulterior motiv)

"I've been thinking about writing about how the network code works in frostbite , there is great interest in this (it would be very technical )

If you ask me, the network code is not bad .. in fact, it delivers a game with 64 players ( soldiers with lots of features) , lots of vehicles ( some of which are very complicated ) , destruction , etc. where everything must nätverkas . This should also work on a mediocre connection ( not all have super connections , especially abroad :-))

I myself have not seen so many other games that deliver this :-)

The good old " die behind the corner " in all networked game that has no prediction (the old quake before quakeworld had not prediction ) .. However, there are tricks to "fool " the player to believe that no dog behind a corner by playing the sequence from the player who killed one ( because you get to see the game from the player's perspective and time .. where is replicated and he is Predicted ) .

And if you are worried , believe me that people are working on both server and client bugs .. Unfortunately, it can be extremely difficult to solve the bugs as we can not gather any information from crashing players to see what went wrong (no appreciate if you copy the entire memory from their computer and send it somewhere :-))"