Stutter on HE impact - ANYONE ELSE SEEING THIS - GOPHUR

[haupt]

Only happens in higher population areas. It's a half second stop just as the shell impacts. Then back to normal.

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140706-1506)

Language: English (Regional Setting: English)

System Manufacturer: Gigabyte Technology Co., Ltd.

System Model: GA-78LMT-S2P

BIOS: Award Modular BIOS v6.00PG

Processor: AMD FX-6100 Six-Core Processor (6 CPUs), ~3.3GHz

Memory: 8192MB RAM

Available OS Memory: 8190MB RAM

Page File: 2219MB used, 14157MB available

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 64bit Unicode

Display Devices

---------------

Card name: NVIDIA GeForce GTX 660

Manufacturer: NVIDIA

Chip type: GeForce GTX 660

DAC type: Integrated RAMDAC

Device Key: Enum\PCI\VEN_10DE&DEV_11C0&SUBSYS_26623842&REV_A1

Display Memory: 4038 MB

Dedicated Memory: 1989 MB

Shared Memory: 2048 MB

Current Mode: 1920 x 1080 (32 bit) (60Hz)

Monitor Name: ViewSonic VG2427wm

Monitor Model: VG2427WM

Monitor Id: VSCF522

Native Mode: 1920 x 1080(p) (60.000Hz)

Output Type: DVI

Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

Driver File Version: 9.18.0013.4052 (English)

Driver Version: 9.18.13.4052

DDI Version: 11

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 8/19/2014 22:14:48, 17555104 bytes

Sound Devices

-------------

Description: Speakers (SB Audigy)

Default Sound Playback: Yes

Default Voice Playback: Yes

Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_100A1102&REV_00

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: P17.sys

Driver Version: 5.12.0001.2020 (English)

Driver Attributes: Final Retail

WHQL Logo'd: n/a

Date and Size: 10/16/2009 06:44:56, 1309696 bytes

Other Files:

Driver Provider: CREATIVE

HW Accel Level: Basic

Cap Flags: 0x0

Min/Max Sample Rate: 0, 0

Static/Strm HW Mix Bufs: 0, 0

Static/Strm HW 3D Bufs: 0, 0

HW Memory: 0

Voice Management: No

EAX 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

Edited December 15, 2014 by haupt

[GOPHUR]

I honestly have no idea. Anyone else seeing this?

Are you having another issue from another thread?

[gsc]

Noticed this when the first BETA w the new HE came out already - using old Core 2 Quad 8200 CPU at that time and ATI 5750 card - large caliber HE impact (75-88) resulted in frame drop for say 1/4-1/2 second - figured its the larger # of fragments being calculated and old rig - just testing offline now 88mm HE into ground short range very slight 1/10sec stutter w FX6300@4.3 and GTX660 - need to test later w BETA patch on server w 88mm and population if more pronounced there

[tomppeli2k]

i havent noticed fps drops??

[gsc]

didnt notice "noticeable" stutter on server w beta patch using 88mm HE so far - need test again in high pop area w tiger, not pushing / towing 88 into hostile environment, not that bored...

[gsc]

i havent noticed fps drops??

Its more of a short "stutter" when the HE impacts/explodes - not a huge FPS drop per se, like a micro-stutter

[gsc]

Micro-Stutter about say 50-80ms upon HE impact occurs w 75mm HE when firing at objects / houses / bunkers et all - didnt notice it firing HE at longer ranges ie >1k so far

[GOPHUR]

gsc what CPU/GPU are you running?

[haupt]

Micro-Stutter about say 50-80ms upon HE impact occurs w 75mm HE when firing at objects / houses / bunkers et all - didnt notice it firing HE at longer ranges ie >1k so far

Thanks, you explained it better than I was.

[gsc]

AMD FX-6300 @ 4.3

nVidia GTX660 2MB

8MB

The Micro stutters already occured w first beta 2 years back when i had Intel E8200 Quad @ 2.7 & AMD 5750

Seems to be just the nature of the beast ie increased # of shrapnell & associated trajectory / hit calculations

[GOPHUR]

Yeah guys here the deal. It's on or off on this feature. No changes are likely short term. So we ship it and see or we pull it out.

For now I am voting ship it because I'm not seeing 100 people complain about it.

Thoughts?

[axis0]

As it is no deal / game breaker its fine - just noticable if you have an otherwise rather "stutter" free gaming experience so its no big deal basically

- GSC *waiting on stuff from billing@playnet.com

[GOPHUR]

Our thoughts too. But we can adjust it says BLOO after release if this becomes a more wide spread issue.

[Scotsman]

Shouldn't be an issue on any modern rig. I did a cycle test in native C way back when and the hit should be invisible on any modern rig. Depends on how your code is implanted internally on tracing the frags but agree on ship. Should not be an issue on anything like a modern rig.

It could be more of a drag with large numbers of players in one spot...but a wouldn't think any kind of microstutter at death would be a big deal.

Not sure what numbers you ended up with vs those calculated..

[haupt]

Ok did some more testing. Seems to only effect the Pz4G.

[gsc]

Try Tiger 88mm HE into something - report back - lol

[blipoop]

I got this as well. Here's what it looks like:

I'll try this out more tomorrow, see what tanks, guns, ranges etc are affected

Edited January 8, 2015 by blipoop

[haupt]

Try Tiger 88mm HE into something - report back - lol

Not an issue with the towed 88. Will try the tiger when I can.

[Scotsman]

Thanks for posting .. Don't see this as much of an issue. In the future if the rats really want to go multicore this would be easy to move to a separate thread on another processor. Then the only game overhead is the call and returning the results. Would be zero impact on graphics.

I think we get more out of functional HE than we are lose here. I can work with Bloo on optmization if he wants.

Also think this might be CPU related. Anyone want to bet the Intel cores won't display this as much as the AMD? AMD cores tend to be weaker on the math side.

Edited January 8, 2015 by scotsman

[dm79]

Had it once that i have noticed, i happened to be quite close to what i was shooting as well.

[company0]

Confirm I'm seeing this, firing the 88mm on the tiger. Fire, FPS drops to 2, comes back up.

[OLDZEKE]

Confirm I'm seeing this' date=' firing the 88mm on the tiger. Fire, FPS drops to 2, comes back up.[/quote']

CPU?

Vid card?

Need info to check for commonality.

I'm kinda figuring AMD cpu.

[company0]

CPU?

Vid card?

Need info to check for commonality.

I'm kinda figuring AMD cpu.

Intel Core i7 Q740 (Miracle in a way that I can run the game).

ATI Mobility Radeon HD 5800

[blipoop]

running an i7 920 @4.5ghz

6gb Ram

ATI 5850

Did a little bit of testing on this today. The stutter didn't happen when firing at the ground, trees or church tower. But did happen shooting other various buildings around a town. Found that population in the town had no effect on the stutter as did orientation of the gun ie. even if the turret is facing to the rear, left, right or anywhere in between the effect still happens.

I did this after playing the game for about an hour. I then logged off (pc was left running) and when I came back I decided I'd try again but before that I closed all non essential running programs. Started game again and couldn't reproduce the stutter.

At that point I thought well maybe it's something I did in game to trigger the stutter, I went and flew a planes, drove a few tanks and eh walked a few infantry? Everything I'd normally do in game. But again I couldn't reproduce the effect.

I'm off for the night, after I boot up the pc again and all the non essential programs start up tomorrow, I'll post up if it comes back again.

[GOPHUR]

Thanks Blip good testing.

We can dial the HE back some if needed but wanted to get more reports before pulling the trigger.