Jump to content

Ellert

Members
  • Posts

    10
  • Joined

  • Last visited

  1. How do i make it that i can select 33 in the middle dropbox? It goes from 1 to 32.
  2. Do you mean to select the last numbers in the drop boxes at Settings -> Misc settings -> Cloud Settings after disabling the 'auto cloud' checkbox ? Those numbers are 35, 32 and 28. If so, no difference. in fact, if anything, it got worse.
  3. hooked everything up as suggested, it was playable for a while, but now getting 'beavered' all the time.
  4. I am getting it every other match or so, mostly when the match just started.
  5. Note that in setup B the PS4 is not connected directly to the Duma, so is basically the most possible hops away from the outside. Having the switch between the PS4 and the Duma like this will not hurt performance/ping ? I am unsure. Hm, thought of a 3rd way to hook it up, with the essential stuff directly on the duma. I will need to pull 2 cables instead of just one, but that is quite possible.
  6. Sorry, have been away for a bit. Work and stuff. Anyway, thank you Chive, i might take you up on that, after i get something sorted first: my network layout. I have attached my current setup and 3 proposed ways to fit in the Duma. I obviously tried A first. Some observations: - The scanner/printer has wifi so can be disconnected from the wired network. - the server in the basement MUST be reachable over 2 ports (i put 1 in the diagram but i just checked, 2 ports) and has a fixed internal ip. - The shitty Fritzbox (god i despise that thing) can not be taken out, there is no way to fully replace that box with the Duma (can not log in onto the providers (xs4all) network and will not have phone). Also i do not believe it can be put into DMZ mode, so quite out of luck here, double NAT seems to be unavoidable. - For option C i will have to pull an extra cable. Any suggestions?
  7. The location of another player is not defining that players lag or lack thereof, but what does is his ping and packetloss. That is why i find the geoip filter thing useless. Filtering on ping, very strict filtering on packetloss, and the possibility to whitelist your laggy friends would be 10 times more usefull. Geoip is a gimmick.
  8. Sorry but that unfortunately is nonsense Gazz, physics and hitdetection going on a server anywhere? dream on. Bungie will not spend a cent on extra hardware if they can avoid it, and running the central server mechanics of their games on anything else then one of the player's consoles would cost them hugely in hardware and hosting. They are only going to move the score-tallying to the matchmaking servers to make it harder to perform a dos attack on the one hosting a match by letting 50 friends check the score all the time. It is very disappointing, but not very unexpected.
  9. I have a Nedduma since a bit over a week, and have used it for about 3 hours. It is now back in its box, as i lack the will to spend more time on dicking around in the interface and restarting destiny for 600 times. The issues are the following: The interface is overwhelming and messy, and does not work very well on any browser under osx. Destiny on PS4 craps out constantly, and if it does, it kicks me back to the loading screen. Something with doing a 'cloud update' has scrolled past in these forums, no idea what or how, or why, nor why it takes so long to insert a couple ip addresses in a central whitelist or have the router record the ip adresses it encounters. And YES i want it to do deep packet inspection if that will automate this. The geoip filter is a charming idea, but not very usefull. I dont care where players are from, as long as they are not skipping around like laggy timelords. Ping based filtering would be a lot more usefull, if it would work propperly. - the measured numeric pingtimes do not correspond with the graph - pingtimes should use a running average to prevent disnconnection after a spike, or have some threshold to retain them after an initial triage at first connect. It is not clear if and how this is done. - the bars in the graph change color all the time - there is no log of the actual ip's, nor a relation to the graph - there is no way to whitelist my laggy friends from closeby or the non-laggy friends that live on the other side of the earth. - i dont see any indication or measure of the devil of all ping problems: packetloss And last but not least: a clear and not too hard to follow step by step instructional document or video of how to set things up and tune them for specific purposes (in my case: "how to set up the netduma if you have a provider-bound router that can not be disabled", and "the best settings for destiny") would somewhat compensate for the lack of a proper manual and the jumble of an interface.
×
×
  • Create New...