Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
3 
Report this post
> Operations is still stupid enough to do some "sync" operations for mods while offline...
There are still some issues here it seems, but when you start an operation, a mod sync is done to make sure all mods are unmounted/disabled. Mod sync basically means we only turn on what needs turning on, and vice versa for turning off. Working as planned, basically.
For other things, everything is still very much a work in progress. You are seeing things change from build to build in the community test. Some things may have to wait for a point release, and some things may have to wait for a later release. AI, for example, is being continuously iterated on.
We are just working away getting stuff fixed up. Sarcasm about the continuing existence of bugs is not terribly helpful but you do you.
I'm fully aware that it's a beta branch of an EA game that last I saw was still in ALPHA...Which if you read my original 1035 note thread along with many other things I note it's questionable to report anything at all given the games state. Everything will be changed, everything *hopefully* will be fixed so why report...just wait.
As for mod sync I found a number of silly incomplete logic issues where if you are offline it will warn about kicking players and various other "online only" relevant things. Again though it's Alpha so does reporting it matter? Maybe in another 10 years we can expect to finally have bug reports matter, I mean then the game will be in development for over 20 years right? Ah wait sorry it will be pushing 30 years by then, it's already at 18 years. 2007-2025. Right I'll quell my expectations a few more notches. (That was sarcasm.)
While I wish there was some basic features added for keeping Ai on either side silent, an option to disable team Ai completely and perhaps fixing the games insane race condition in menus this is why as noted in my original 1035 notes the GB motto is "Try it again next year" for a reason.
I guess the feedback and bug report request was rhetorical.
When I thanked you for your feedback, I was sincere. We will take these points into consideration, though for us it is easier to work with bugs submitted using the in-game reporter where appropriate. I am not sure I follow your logic about it not being worth submitting bug reports, but let me clarify that the explicit purpose of this build is to gather bug reports from the community.
Thank you again for your assistance.
The in game reporter is not an option for me as I play Lone Wolf and ACTUALLY offline only. Since your in game reporter does not save then queue reports for when it is able to send them, any report I might try to file goes to /dev/null.
As for the logic of why submit bug reports is simply because things are too early on. If you released the game on the first day you decided to make it, maybe had a project file, some notes about tool kits etc you'd be flooded with bug reports about there being "no game at all." The situation isn't that dissimilar right now. In theory all these obnoxious issues with voice lines will be remedied in time so why report it? The logic issues with workshop items being added and removed...will be worked out...so why report it when we all know it's broken and incomplete? The obvious "in between" answer is because you are offering the game as a product despite the state and it would be nice to play without an onslaught of obnoxious repeating voice lines being blasted in your ear the whole time. Or the game trying to set you machine on fire because you are in the menu...
In theme with the fact I can't use the in game bug reporter this is also why I link screen shots on my server. With the game and Steam offline I can't upload screen shots so I take them with my normal system tool and toss on my server as proof of the issue. I've done this when I've found issues in maps with LOD issues or objects with incorrect normals.
As for my post being edited, I often go back and revise things or correct spelling issues I catch after the fact.
I take your point about things changing a lot. Stuff inevitably needs rework after other changes. But we can't move on with anything if things aren't working. Enough of the stuff that gets fixed stays fixed. Fixing big things creates ripples that break smaller things. Fixing smaller things creates ripples that break even smaller things. Eventually you get there, and not trying to fix anything doesn't make any sense.
I still think menus are ignoring frame limits, when workshop is back up for 1035 I'm sure I will have a ton of logic issues to point out but again kinda silly to complain half a game isn't a whole game...just frustrating. Just before 1035 was up for testing I reported some nasty logic issues with the workshop items and the kit/gear/loadout system being very underbaked to deal with workshop items.
Same with the Ai stuff. The Ai even with the middle ware it is still some of the worst I've seen but the vocalization spamming is brutal. I suggested to Chris to just implement a simple db key pair system to shut them the hell up. If a Team Ai spots something the target ID gets logged, that Ai says it's useless little "Target Spotted" schpeel but if the other Team Members see that target they do a table look up before they run their suck holes, see it's been logged and keep their damned mouths shut. When the target is killed the entry in the db is cleared and we move on. This is simple, keeps them from saying the same crap over and over and shouldn't have a ton of overhead even if they poll db frequently...unless the tick rate is tied to the frame rate.
Despite this I gave 1035 a try...maybe I'll try again when it's mainlined but I'll probably just "Try again in a year." Perhaps "Semper Gumby" arms will at least be fixed by then. ;p
It's not clear. There doesn't seem to be anything particular going on with our stuff in the main menu.
What do you mean by 'menus' plural - all main menu stuff, or something else?
I had not noticed this issue with 1034 but after trying 1035 I went back to 1034 and tested it. 1034 did it but this then begged the question was this perhaps caused by some incorrectly migrated setting when 1035 does the initial conversions. (This is all in my initial 1035 thread) So I went to make sure the FPS cap was still set and it was but upon enabling the show FPS feature I noticed it wouldn't show FPS on/in various menus or sections of the game.
I did a bit more fiddling and saw FPS only showed when in a match/round so I then capped the FPS at 30 just to see if drastically reducing it would quell things. It did iirc and I jumped into a match to confirm 30 was the target limit. After that I set things back to 60 and tried again. After that some things were better, the initial 1035 release had my CPU/GPU erratically ramping up and down, however menu's still ramp everything to the 9's.
All this prompted the joke when the title screen is more demanding than the game something is wrong heh. However this still skims the "just wait...surely it will be sorted out some day." I had initially discussed the menu issue with Chris (RedBeard) as we're on similar setups.
Well Gall Dang, I just went to test something and I got the crash on exit...
Here is a quick low FPS vid (to keep file size down) showing when on the menu including the operation menu/setup my GPU is pinned. Map.png must be hella sick to require such GPU power hehe. However once I'm in the briefing room i.e. actually rendering the game it drops down to a sane level and stays that way while playing.
(I'll delete the vid in a day or two.)
https://m0dw3rks.com/trans/GroundBranch/GB-Menu-Short.webm
Anyhoo there are tons of issues like the Ai going defunct, no pathing through valid areas of the map to do missions, the import/conversion logic that's broken for kits/settings. All the dialogs and logic that ignore network status. Broken workshop item handling logic, missing female voices, voice line spamming. Missing UI/UX logic for things like detonation...the fact timed gives zero feed back about how long it is and it displays the success message despite never actually detonating...are they bugs? Just incomplete bits? Kinda both but again, reporting this early walks that line between silly and mayhaps you should...mayhaps wait...