GROUND BRANCH

GROUND BRANCH

Le sigh...settings and loadout glitch
Saw a patch and decided to try it.

First thing everything looked crap - game reset my video settings with no warning or notice.

Second thing tried a mission, reloaded, could not shoot. This was a real WTF moment given I had only expended a single mag and my entire chest rig is primary. Get back to the loadout and it shows my gun with no mag and gives me a warning I have no primary ammunition despite my chest rig, again, being nothing BUT!

REMOVED

At the little loadout summary at the bottom it says I have 6 frags and nothing else. Amusing given my rig clearly shows 6 double stacked pouches and editing the rig also shows every slot assigned to primary. I have removed all the items from the chest rig and replaced them, no change, shows no ammo.

As a bonus I was on Depot and the inside of the railcars look to have a rock texture. I didn't snap a pic but can if you really need confirmation.
Last edited by Game? More like Grift.; Apr 9, 2023 @ 3:50pm
< >
Showing 1-15 of 19 comments
JohnJ  [developer] Mar 16, 2023 @ 7:58pm 
Obviously that all doesn't sound good and is unexpected. Were you on 1033 then updated to 1033.1 and this started happening?

You can try to delete your config files to see if that will help. It's possible they are not updating when you start the game and causing some conflicts.
I have been on 1033 for some time (I would gladly roll back to 32 hint hint) and I had recently deleted my settings to deal with one of the updates making the textures look like an N64 game threw up. I can try again but at this point I might as write a delete setting launcher. I know this is EA but it seems all I do is delete my settings, redo all my weapons and gear just to lose it all again since you guys mainlined 33.
Last edited by Game? More like Grift.; Mar 16, 2023 @ 8:08pm
JohnJ  [developer] Mar 16, 2023 @ 8:30pm 
Something isn't right and that is not the typical behavior of course. I'm just not sure what makes your system do that.
KrisRedbeard  [developer] Mar 16, 2023 @ 9:56pm 
Whenever item class naming issues are found and fixed, any kit/loadout relying on the previous name will break. Very frustrating internally as well, since there are lots of .kit and .bot files to update. Actually made a note about it in the last changelist that had a name change, suggesting we develop something that automatically redirects old names to the new ones.

Working on a hot fix that adjusts when AA and SSR should be changed, due to DLSS/DLAA usage. Aside from that, rest should be pretty solid.

Did restarting help with any of the video setting changes?
Not sure what you mean about restarting? I just turned AA off again and tried a mission. It did give me the nag I'd need a restart for the changes to take effect but it didn't. With AA off and shadows set to low again things are ugly but the best option for my tastes. After I realized my loadout was gibbed I never restarted or tried the game again. Just fired up Tarkov.

Name changes? That's why you tie them to a reference ID. ;p (I know some things are better human readable) I skimmed the change notes but I'd never have tied this to a name change.

Anyhoo I just figured I'd see if the patch silently addressed any of the previous issues I had reported but alas it just added to the list.
Last edited by Game? More like Grift.; Mar 17, 2023 @ 2:55am
KrisRedbeard  [developer] Mar 17, 2023 @ 3:31am 
Restarting the game
Was looking like some variables that should change at runtime didn't, so restarting was in order. Made a change for the hotfix that *hopefully* sorts that for good.
Very much over UE4 and its "Do it this way" only to find out there should have been a "But remember to do this afterwards.".
Ah gotcha. Yeah I didn't restart, figured there was no point to continue bashing my head on the game. I do enough debugging through the day I just wanted a fun game for a few. Perhaps I'll try it again after the next patch.
Last edited by Game? More like Grift.; Mar 17, 2023 @ 4:10am
Saw todays patch, updated, started the game...no dice. Magwell is empty, chest rig is full of ammo, says no ammo. Removing and reapplying ammo to the chest rig does not reset or fix the issue.

I decided to jump into a round anyhow and while in the loadout it shows the rifle without mag i.e. no ammo once I load in I do have a mag in the gun and can dump it. However reloading it then reloads but the new mag is empty. A few more mag change attempts and finally it won't even try to change mags and just says no ammo with a red mag icon.

Upon starting after checking kit files my character was wrong, set to default but all my other stuff was still there complete with "brokeness."

Figured I'd check affected kit files : see anything fishy?

{
"Ver": 11,
"BuildName": "MCR Pri",
"Item": "Platform:BP_Platform_ChestRig_MCR",
"Children": [
{
"Item": "Pouch:BP_Pouch_PrimaryAmmo",
"Comp": "PlatformMeshComponent0",
"Socket": "POUCH_1_5"
},
{
"Item": "Pouch:BP_Pouch_PrimaryAmmo",
"Comp": "PlatformMeshComponent0",
"Socket": "POUCH_1_4"
},
{
"Item": "Pouch:BP_Pouch_PrimaryAmmo",
"Comp": "PlatformMeshComponent0",
"Socket": "POUCH_1_3"
},
{
"Item": "Pouch:BP_Pouch_PrimaryAmmo",
"Comp": "PlatformMeshComponent0",
"Socket": "POUCH_1_2"
},
{
"Item": "Pouch:BP_Pouch_PrimaryAmmo",
"Comp": "PlatformMeshComponent0",
"Socket": "POUCH_1_1"
},
{
"Item": "Pouch:BP_Pouch_PrimaryAmmo",
"Comp": "PlatformMeshComponent0",
"Socket": "POUCH_1_6"
}
]
}

{
"Ver": 11,
"BuildName": "MK17DMR SD G33+EXPS3",
"Item": "PrimaryFirearm:BP_Mk17_DMR",
"Children": [
{
"Item": "Magazine:BP_SCAR_H_Magazine",
"Well": "MagWell",
"Skin": "Black" <-- This is the only difference I see from the original to a new "redo" of the item.
},
{
"Item": "Sight:BP_Magnifier_Black",
"Rail": "RearSightRail",
"Slot": 3
},
{
"Item": "Sight:BP_EXP3_HoloGraphic_Black",
"Rail": "RearSightRail",
"Slot": 8
},
{
"Item": "RailAttachment:BP_RVG_VertGrip",
"Rail": "BottomRail",
"Slot": 4
},
{
"Item": "RailAttachment:BP_TacLight_M300c",
"Rail": "BottomRail",
"Slot": 27
},
{
"Item": "MuzzleDevice:BP_Suppressor_FN_QD702_BLK",
"Comp": "Mk17_Barrel"
}
]
}
Last edited by Game? More like Grift.; Mar 17, 2023 @ 11:21pm
KrisRedbeard  [developer] Mar 17, 2023 @ 11:55pm 
Change:
Magazine:BP_SCAR_H_Magazine

To one of these:
Magazine:BP_SCAR_H_Magazine_Black Magazine:BP_SCAR_H_Magazine_FDE

There is a skin system in place for items, but there is no UI element that allows you to select the skin for an attachment, magazine or anything that is attached to another item.

At some point, people wanted different colour PEQ's, mags etc, so variants matching those colours were added since there was no way to change the skin via the UI.
I know when I redid the chest rig and dragged primary ammo on it was black and there was no UI for selecting color/pattern. However when I saved it and it showed me the whole character again it defaulted to match the color selection of the parent item. So no clown car loadouts.

I suppose the remaining question is how did my kit file end up retaining the depreciated Skin: line?
Last edited by Game? More like Grift.; Mar 18, 2023 @ 12:29am
KrisRedbeard  [developer] Mar 18, 2023 @ 2:32am 
The item Blueprint probably has "SkinMaterialPrefix" set, despite not needing it.
If there is only one skin (i.e. black), it shouldn't actually do anything.
JohnJ  [developer] Mar 18, 2023 @ 7:34am 
Also try disabling Cloud sync as well. It is used for GeForceNow, but is user controlled. It is most likely bringing in your old and no longer valid kit files.
Cloud sync is always disabled globally and I play exclusively offline. The only time I allow Steam online is for relevant patches or updates.
Last edited by Game? More like Grift.; Mar 18, 2023 @ 1:29pm
JohnJ  [developer] Mar 18, 2023 @ 3:48pm 
Originally posted by √®¡|) ©ƒ |_¡ƒ∑:
Cloud sync is always disabled globally and I play exclusively offline. The only time I allow Steam online is for relevant patches or updates.
Ok.
It's odd how the old kit file is still around and causing issues.
Indeed. However also not surprising as the 1033 release has been pretty brutal on my end. Comically before you guys shut down CTE I was always on it, no issues other than a few small things here and there. 1032 was good, 1033 has been like a crash landing that hasn't started skidding and might burst into flame at any moment heh.

It's just frustrating because I spend all day coding and debugging. Shift gear to clear my mind with some pew pew and end up still debugging and no pew pew. Still ticks me off with all this cloud sync bs you can't roll things back to working versions, only get dragged along.
Last edited by Game? More like Grift.; Mar 18, 2023 @ 6:15pm
< >
Showing 1-15 of 19 comments
Per page: 1530 50

Date Posted: Mar 16, 2023 @ 6:25pm
Posts: 19