Week 0 - Please give us OPTIONAL diagnostics for the game (network, GPU, CPU, audio, memory, world, etc)
Hello,
Players do not have the necessary information needed to diagnose issues with the game. Error codes are useless for many of the issues they are supposed to relate to. Here are the data that the game should be able to OPTIONALLY display through an in-game setting or command line argument:
1. Frame Details (Diagnosing stuttering and other issues related to CPU, GPU, and physics frames)
- CPU frame count/time + graph option + min/max/avg option
- GPU frame count/time + graph option + min/max/avg option
2. Network Stats (Diagnosing network-related things)
- Transmit (tx) and Receive (rx) packet counters and bandwidth
- Current Steam UDR endpoint/port and latency/jitter/packet loss metrics (ie."Los Angeles - 162.254.195.72:27018, L: 12ms, J: < 1 ms, PL: 0%")
- Replicate the current NAT type and ports to this view as well
- Latency/Packet Loss to the current Activity Host Bungie controls
- Latency/Packet Loss to other players (rendered in a list in a debug overlay or displayed in roster like D1 had)
3. World Debug (Providing specifics when reporting in-game issues)
- Current XYZ position and direction faced
- Current activity name
- Number of loaded entities, number of rendered entities, etc
- Active status effects (buffs/debuffs applied to you)
4. Memory Debug (Checking for leaks and other memory-related issues)
- Number of allocations to heap/stack
- System memory used
5. Disk Debug (Checking to see if there are disk problems or something with how the game interacts with the disk)
- I/O operations count
- Data written/read
6. Audio Debug (Diagnosing audio problems)
- Number of sounds playing
- Audio level
7. Misc. Data (Diagnosing other things)
- Client version
- CVars list (local) - What the game loaded and has for your client-side variables
- Remote variables list (to compare what the server has for things like mouse sensitivity versus what client has as some variables on the client side do not properly save to cvars (Mouse Smoothing)
This data would be useful in reporting issues with content to Bungie (using location data), diagnosing performance issues related to frames, networking, and audio, and finally empower players with the ability to verify things they can't current verify. These items are likely already in the developer build of the client, but stripped during building for the public release.
Without this data, you can't properly use the report function for network manipulation or poor connection as an example. You don't have the data to know if maybe the issue is just to that player, other players, your own connection, or Bungie's end.
This is data you can get in other games such as COD, Apex, Minecraft, Valorant, Battlefield, etc. Some show more data than others, but every one has more detail than just.... FPS, which can be obtained from currently allowed overlays. Destiny 1 even had the ping meter, but that was removed in Destiny 2. If players feel it would introduce toxicity, then they can always block a player and/or use the report function. Blocking helpful functions due to toxic people only gives them more power.
I moderatori possono proibire a questo utente di inviare messaggi (saltando la coda delle segnalazioni) selezionando una punizione adeguata.
Ban di 7 giorni
Ban di 7 giorni
Ban di 30 giorni
Ban permanente
Questo sito utilizza cookie per fornire un migliore servizio agli utenti. Cliccando su "Accetto", accetti le politiche esposte su Politica sui cookie e Politica sulla privacy.
Accetto
Questo sito utilizza cookie per fornire un migliore servizio agli utenti. Continuando a navigare su questo sito, accetti le politiche esposte su Politica sui cookie e Politica sulla privacy.
Di recente, le nostre politiche sono cambiate. Continuando a navigare su questo sito, accetti le ultime politiche esposte su Politica sui cookie e Politica sulla privacy.