@Geez hi 👋

Reported previously for all vehicles - closing as duplicate.

I did some further testing on this by putting in my old 4070Ti and booted up the game, everything ran perfectly fine, so on that basis I would say it's isolated to the 5080 GPU, however, I initially ran the 5080 with my i9 for some weeks before I upgraded the motherboard / CPU / RAM too, so it seems it's a combination of the 9800x3d along with the 5080 which causes the issue.

Resolved for 1.3.0.87 and higher

I'm writing to confirm similar issues with almost identical setup: 5080, 9800X3D, 32GB DDR5, 2TB m2 SSD, X670E. The issue might not be limited to loading textures, when firing a weapon the firing sound can be played a second after the shot was taken. Occasionally the game freezes totally looking like a crash, but recovers after some seconds.

I really like the possibility of destructing the towers but capture point should dissapear after destruction (similar with the command truck where message appears to the teams that entre deux tower destroyed).

Keep the destruction but make it so, when tower is destroyed then this point will dissapear and not provide connections anymore (when it is destroyed then similar message appears like with command truck when it is destroyed)

In T187409#2745954, @aldworth33 wrote:

Can this please be added especially now when every server if pretty much full with a 30+ queue on an evening, I'm about to launch my own server and don't want to be locked out of my own server if I need to get on to make some changes etc

Relates to T189525

good idea

Another option on how to do this:

This only applies to Everon. On Arland, the transmitter is very firmly installed and cannot be destroyed.

relates to T189257

And another Crash on Exp. 1.3.0.84 from yesterday

I am sharing a screen recording to show you how significant the problem is. This issue occurs not only at the moment I first spawn but also at various points in the game. For example, when I drive to a combat area and exit the vehicle, the weapon in my hand and its scope fail to render. This makes it impossible to play the game in situations requiring quick reactions. Since the scope does not render, I cannot see elements like the red dot, etc., associated with the scope. As a result, the game essentially comes to a halt for me for 10-20 seconds. Additionally, while driving, the roads sometimes fail to render, giving the impression that I am moving on a flat gray surface. There are many other similar issues that I cannot fully list here.

Still getting this error.

Yes. your logs basically look like mine. Must be the same issue. For me it crashes very quick. Can’t really play multiplayer. I get kitted and dropped at the front line. Then it freezes for a second or 2 and the windows pops up. I struggle with it since weeks and I tried every experimental version since then. Only thing that worked was deleting the ReforgerEngineSettings or how it was called. It didn’t crash for an hour after that but when it crashed it got more regular again.

Same challenge here. Thx for the hint. Will check next time and keep you posted. Any plans or timeline when you will fix this?

Same here... can be combined with: https://feedback.bistudio.com/T187941

In T187294#2725187, @kawalec wrote:

@Technicolourmatador
Even now, when defending base is so easy, very few people spawn on attacked bases.
90% of players don't like driving, don't care about driving, don't know how to do it. So they don't drive to attacked bases.
99,99% of players love flying and can't do it.
So if you sum this up, for most player it will change the game into 30-minute long fight with AI and then loosing/wining without even experiencing any highlight of Conflict.
Why? Because a team of 2-4 people with Willys can drive around every enemy base and capture one by one. Not to mention heli.
In the first week over 50000 copies of PS version were sold. It marks a huge change for Reforger and Arma franchise. We're just stepping out of dark burrow of very niche game into the wast world of casual players.
Such mechanics as this new one may be too hardcore for them. They will still be playing the game, but they will be purposefully omitting it's core features. Exactly as it happens now with supplies, spawning AIs, making self-defensive layouts of bases, using radio spawns, proper communication etc. I'm not even mentioning teamwork, because at the moment it's nearly non-existent.
I can manage with any new mechanics, you can also and many other more experienced players. But I'm worried that such changes may slowly kill the idea of Conflict.

In T187294#2725495, @byNautiic wrote:

Well, we won't be dealing with this:

That was the best decision to turn off this function. I was tired of fighting the Freshspaws with spawn protection. If you don't defend your base, you're out of luck. Fair play for all. Spawning on bases that are under conquest is unfair! I don't need opponents spawning in front or behind me and happily killing me. And I have to guess when to fire. Yes! They have protection running. THAT is unfair. PLE
ASE KEEP THAT IN BI.