Multiple issues

[McMuffin]

I've got a few issues I'm going to bundle together.

1) Really bad frames. The frames I got at last nights event were horrible, like 9-18 frames for extended periods of time, but the best it ever got was maybe 30, which I will say is not bad, but it usually went away after I was in the game for about two minutes. The frame count, on average, is considerably worse than previous builds. Please say if you also got the same experience or not, I'm interested to see if this is just an issue I have.

2) The tactical view was not working/multiple keys not working. Again during last night's event, after I would get onto the server and maybe ten or so minutes have elapsed my tactical view wouldn't show up if I pressed T, same goes for chat and pressing enter. I went into my graphics settings to see if maybe changing some graphics would 'refresh' the game, changed some stuff, the game refreshed, and I pressed escape only to find that not only was the escape button not working, the 'Main Menu' option was grayed out. Obviously, I was forced to ctrl-alt-delete close the game.

3) Regiment descriptions. Many of the regiment descriptions are cut off when choosing them as it appears they go on farther than the current UI allows (see below for example). Now you do not have to delete that 'overflow' section permanently, instead, you could copy the entire current text for each regiment to a google doc or something to use for the 'Encyclopedia' feature in the menu that is currently not available and then condense the descriptions to fit.

https://steamuserimages-a.akamaihd.net/ugc/966474717681106400/801D1EF8F22864598971922700D596391DD46ACF/
https://steamuserimages-a.akamaihd.net/ugc/966474717681093588/05D3220A3437C50D6AD9EC942EB92399F04498D7/

[Sox]

1. Have to say that my frame rates were fantastic all night, and I've had no problems at all with FPS in this build.
2. I had ALL of the same problems. I rarely get the 'briefing' screen at the start of a map, my T key was failing all night.
3. Same for me.

[TrustyJam]

Thank you for the report. :)

1) The performance will take a hit depending on the amount of players on the server (a 150 player match will run considerably worse on the client side than a 1 player match as there is a lot more of everything basically for both your GPU and especially CPU to handle). We recently increased the amount of data the clients log in order to investigate the mass player boots from the server - this again will cost more performance the more players are on. Lastly, the game is currently running its code in the profile solution (for more clues in regards to bugs and issues) and not its release solution and this comes with a performance cost as well.

2 & 3) We are aware of UI and HUD stability issues and lacking features and have recently stepped our newest team member, UI Engineer Mikael up to working full time on a rather big UI overhaul in order to fix these issues.

- Trusty

[McMuffin]

Thank you for the report. :)

1) The performance will take a hit depending on the amount of players on the server (a 150 player match will run considerably worse on the client side than a 1 player match as there is a lot more of everything basically for both your GPU and especially CPU to handle). We recently increased the amount of data the clients log in order to investigate the mass player boots from the server - this again will cost more performance the more players are on. Lastly, the game is currently running its code in the profile solution (for more clues in regards to bugs and issues) and not its release solution and this comes with a performance cost as well.

2 & 3) We are aware of UI and HUD stability issues and lacking features and have recently stepped our newest team member, UI Engineer Mikael up to working full time on a rather big UI overhaul in order to fix these issues.

- Trusty

Good to hear the UI is being reworked. And that makes sense for the performance to get worse with more players, but I remember before this build was put out, and although we had server instability issues, the frames didn't drop to 9-18 when the player count neared 150. However, you did say that the amount of data sent has been upped so maybe that did contribute some along with the profile solution you mentioned.

[C. Moser]

I agree with you McMuffin that my frames were worse with this build, compared to the past. And Ive been in big to almost full servers plenty of times.

[TrustyJam]

I agree with you McMuffin that my frames were worse with this build, compared to the past. And Ive been in big to almost full servers plenty of times.

Thanks for the report. :)

Apart from the above stuff I mentioned, the FPS is also dependant on what is on your screen. You will experience worse FPS when in a dense forest close to lots of players moving about, firing with lots of dead bodies, etc. than out alone in an empty field for instance.

- Trusty

[C. Moser]

I know what causes bad fps, and Ive played these maps and alpha long enough to know what "naturally" causes it. What Im experiencing feels unnatural. Thanks for the info though :)

[A. P. Hill]

IMHO, Everything on your screen is dependent on keeping your system drivers and o.s. updated.

Nvida just released a new update today. Win 10 issued new update a week ago.

[Maximus Decimus Meridius]

Thank you for the report. :)

1) The performance will take a hit depending on the amount of players on the server (a 150 player match will run considerably worse on the client side than a 1 player match as there is a lot more of everything basically for both your GPU and especially CPU to handle). We recently increased the amount of data the clients log in order to investigate the mass player boots from the server - this again will cost more performance the more players are on. Lastly, the game is currently running its code in the profile solution (for more clues in regards to bugs and issues) and not its release solution and this comes with a performance cost as well.

2 & 3) We are aware of UI and HUD stability issues and lacking features and have recently stepped our newest team member, UI Engineer Mikael up to working full time on a rather big UI overhaul in order to fix these issues.

- Trusty

Thanks for information. Always interesting and good to know whats going on in the background.

[Shiloh]

My frames were pretty bad on Sunday night particularly on Pry Grist Mill map. Worst I've had since playing this game but we were 140+. Last night (Monday) they were considerably better.

Those regiment descriptions have been cut off for as long as I can remember. It would be great if the regiments showed the proper uniforms as well when selecting.

A workaround I've found for the tactical view not working is to hit tab first to show sides, then hit T for tactical and it works. Not ideal but workarounds often aren't.

[TrustyJam]

Those regiment descriptions have been cut off for as long as I can remember. It would be great if the regiments showed the proper uniforms as well when selecting.


Both issues will be fixed in the UI overhaul.

- Trusty

[Redleader]

I've got a few issues I'm going to bundle together.

1) Really bad frames ...

2) The tactical view was not working/multiple keys not working ...

3) Regiment descriptions ...

1. The 150 full server event gave me some lag and I crashed about 5 times. (it was on an NA server, while I'm European)
2. Sometimes it comes back up when using 'T', sometimes it just freezes or disappears … I also had to play one entire map with 'you are about to desert 20' (I was a private) … makes it hard to aim :p
3. I'm sure it needs some rework, the little 'thumbnail overview' also doesn't the right uniforms (like Shiloh stated)...

P.s. : I did go back to 8gb RAM (ordered new faster ones) and stability was beter on 16gb it seems … could be just me ….

[Sox]

Gonna write this up here because I had multiple issues tonight (Sat NA Event)

Took over 45 mins to actually get in game. First I was getting hung up on the map loading screen, then when I got past that I hung up on the spawning in screen.
I also had problems with the server list. Most of the time it simply would not list the populated server, sometimes it was blank altogether.
Re-booting, veryfying files, re-starting the game, nothing worked basically.
Eventually I got in, but gave up after the third map when it started hanging on spawn in again.

[TrustyJam]

Gonna write this up here because I had multiple issues tonight (Sat NA Event)

Took over 45 mins to actually get in game. First I was getting hung up on the map loading screen, then when I got past that I hung up on the spawning in screen.
I also had problems with the server list. Most of the time it simply would not list the populated server, sometimes it was blank altogether.
Re-booting, veryfying files, re-starting the game, nothing worked basically.
Eventually I got in, but gave up after the third map when it started hanging on spawn in again.

Thank you for the report.

How many players were on the server when you hung up on the loading screen? (The loading screen will appear like it’s hung up once or twice during the loading process - it isn’t and will respond again within half or minute or so).

When you say hung up on the spawning screen do you mean crashed (unrespondsive) or not being able to spawn in after having pressed deploy?

- Trusty

[Sox]

When you say hung up on the spawning screen do you mean not being able to spawn in after having pressed deploy?

Yessir, I could still hear the battle and see players moving around, it just never actually spawned me into the game.


How many players were on the server when you hung up on the loading screen?

Between eighty and a hundred.

[TrustyJam]

Yessir, I could still hear the battle and see players moving around, it just never actually spawned me into the game.



Between eighty and a hundred.

Thanks, what regiment/class and what area was this on?

We've seen a few players report not spawning but we've not been able to replicate it ourselves yet.

- Trusty

[Sox]

Thanks, what regiment/class and what area was this on?

We've seen a few players report not spawning but we've not been able to replicate it ourselves yet.

- Trusty

I honestly can't remember Trusty because it happened on more than one map, next time I'll be sure to make a note of them. Sunday night was a lot better, but the time between clicking 'deploy' and actually spawning in was still much longer than usual, plus someone else in our Regiment did have the same issues on Sunday night, that I had experienced the night before i.e. he was unable to spawn in after hitting deploy.

[TrustyJam]

I honestly can't remember Trusty because it happened on more than one map, next time I'll be sure to make a note of them. Sunday night was a lot better, but the time between clicking 'deploy' and actually spawning in was still much longer than usual.

You spawn in waves so if you’ve clicked deploy the second after a wave has been spawned you will wait 29 seconds before spawning in on the next wave. Other times you may click deploy a second before a wave is spawned.

- Trusty