[U78 Alpha 1] Extreme FPS Drops Whilst Using The Arm Swinger Movement With A Gun With Many Attachments (Video Included)

[Mac Diddy]

Sorry for the really long title but bear with me here, basically this bug is like activating slow mo whenever you're walking with a heavily customized gun, however as soon as you stop walking the frame rate returns to normal.

https://youtu.be/atJLNrGDuhI

[[RUST]Grumplestiltskin]

This is not a bug. This is how expensive that gun in on the CPU. May I ask, for reference, what CPU is in your machine?

[Mac Diddy]

Originally posted by RUSTGrumplestiltskin:

This is not a bug. This is how expensive that gun in on the CPU. May I ask, for reference, what CPU is in your machine?

I have an Intel i9 9900k, so in theory it should have no problem at all with this.

[[RUST]Grumplestiltskin]

Could I see your SteamVR performance graph on screen in a recording (so I can see the CPU graph)?

I can't actually see frame drops in that video that are perceptible to you.

Also, what FPS is your HMD running at?

[Mac Diddy]

Originally posted by RUSTGrumplestiltskin:

Could I see your SteamVR performance graph on screen in a recording (so I can see the CPU graph)?

I can't actually see frame drops in that video that are perceptible to you.

Also, what FPS is your HMD running at?

The FPS is steady at 90 until I start moving with that or any other gun with a lot of attachments.

Here's the video you wanted:
https://youtu.be/ndk9JCY1BW8

[[RUST]Grumplestiltskin]

1. How... many attachments were on that gun? Can you give me an exact configuration. I'd like to replicate this.
2. What did you have in your quickbelt at the time?
3. Can I have your full system hardware spec?

[Mac Diddy]

Originally posted by RUSTGrumplestiltskin:

1. How... many attachments were on that gun? Can you give me an exact configuration. I'd like to replicate this.
2. What did you have in your quickbelt at the time?
3. Can I have your full system hardware spec?

Attachments:
Number of attachments: 13

Top rail:
-Backup iron sights, with the front sight oriented backwards so it folds towards the muzzle.
-Two short rail extenders clipping into each other to create the effect of one rail riser
-MTI reflex sight on top of the makeshift rail riser
-Tactical flashlight in front of the rail riser and behind the front sight

Bottom rail:
-Foregrip angled (black)

Left rail:
-Handstop QC9
-Two short rail covers

Right rail:
-Tactical laser 1
-Two short rail covers clipping into each other to make one slightly longer rail cover


Notes:
-Here's some screenshots of that gun for some visual reference. https://imgur.com/a/k1MrU1P

-I only had a spawn locked ACP9 magazine in my quickbelt filled with regular FMJ ammo.

-An important thing to note is that it appears this bug only occurs on the Arizona map (both the daytime and the nighttime).


Computer specs:
OS: Windows 10
CPU: Intel i9 9900k @ 5ghz on all cores
GPU: RTX 2080 ti
RAM: 16GB of DDR4 @ 3200mhz
Storage: Samsung 860 evo 2TB SSD (H3VR is installed on this drive)
Boot drive: Intel 660p 1TB NVME SSD

[[RUST]Grumplestiltskin]

Also, do this. Open your options, look for 'Object To Hand Connection Mode'

Set it from 'Direct' to 'FLOATING' instead.

Tell me how things work for you.

[[RUST]Grumplestiltskin]

Wait... did you say you ONLY get this spike in the Arizona map, and nowhere else?

1. How many maps did you try this gun in.

2. Can you right click the game, go to properties, local files, verify integrity of game files. Then, retry the test. I want to know if that map's files were somehow corrupted for you.

[Mac Diddy]

Originally posted by RUSTGrumplestiltskin:

Wait... did you say you ONLY get this spike in the Arizona map, and nowhere else?

1. How many maps did you try this gun in.

2. Can you right click the game, go to properties, local files, verify integrity of game files. Then, retry the test. I want to know if that map's files were somehow corrupted for you.

So changing the hand connection mode to floating did work.

However after validating the files and with the hand connection mode set to direct it still spikes like before.

Here are the maps I tried this on:
(direct hand mode and the same gun as before was used for all these tests)
-Indoor firing range
-Proving ground
-Friendly 45 range
-Sniper range
-Meatmas snowglobe
-Warehouse range (performance was a little choppy here, but less choppy than Arizona)
-Meat fortress
-Take and hold
-The sampler platter (performance was very choppy here, similar to Arizona)
-Breaching proto
-Arena proto
-Arcade proto
-The gunnasium
-Mini arena

All these maps performed as normal, except for Warehouse and Sampler Platter, so that makes me think this is related to physics based objects in the world but that wouldn't really explain how Friendly 45 and Breaching Proto were unaffected.

[[RUST]Grumplestiltskin]

This is super confusing.... I will examine those maps and see if I can figure out what might be causing it. It might be the physics complexity of the ground, and what is treated as colliding or 'an object of concern' for the collision calculation.

BTW, if you're using Armswinger, you might as well keep that setting on 'floating'. It's higher performance, and you don't need the placement precision.

[Mac Diddy]

Originally posted by RUSTGrumplestiltskin:

This is super confusing.... I will examine those maps and see if I can figure out what might be causing it. It might be the physics complexity of the ground, and what is treated as colliding or 'an object of concern' for the collision calculation.

BTW, if you're using Armswinger, you might as well keep that setting on 'floating'. It's higher performance, and you don't need the placement precision.

Alrighty I'll keep it on floating, good luck on finding out whats causing it, let me know if you find the cause.