Is it just me or does it seem like there are still a lot of bugs for a game being released in a few weeks?
- 16
- 2
- 1
the last stream they published
- Thread starter lpdpig139
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
What are you implying? That they should postpone the release? You're not going to be liked by many here... 
- 24
1. It is a nightly build, so it is buggier than the actual 'current' build.
2. They are using one save file over multiple builds, which only increases incompatibility issues and bugs.
3. There will be some bugs in any case in the finished product, which Paradox will lovingly patch within days.
2. They are using one save file over multiple builds, which only increases incompatibility issues and bugs.
3. There will be some bugs in any case in the finished product, which Paradox will lovingly patch within days.
- 12
- 10
Gotcha. I was actually worried. I'm not well-versed in development, but it just seemed like a butt load of little bugs here and there for a finished product to be coming out in a mere three weeks.
Wiz even said that it wasn't the stable build that they had, it was the most recent and why the QA team watches the stream. While the stream is there to keep the peasant from revolting, I'm sure it is an excellent way to troubleshoot the various builds they work on.
- 4
- 3
Every bug they found they had recorded video of what they did to trigger it. Cannot get a more favorable environment for bug squashing than that.
- 21
- 1
Is Wiz the kind of guy who would broadcast an unstable build just to simultaneously work on improving the game during business hours?
.png){kind=avatar}
Every bug they found they had recorded video of what they did to trigger it. Cannot get a more favorable environment for bug squashing than that.
Sure you can; you can be running the code within an ide, with debugger attached.
- 1
a couple weeks before release is one of the buggiest times in a game's development, as it is when you stop implementing new features and start on bug squashing. not much point in doing too much debugging earlier when everything is going to change anyway.
- 2
- 1
They should really program in a random event that can trigger where they more or less imply new information on a video game is released and you get the strength of a random faction reduced.
Everytime the dev stream the game on the Paradox channel at least it's a development build. The last EU4 MP match they had a buggy Cossack build. Seeing as Stellaris is still in development I doubt any build remains stable for long.
- 1
The fact that they didn't CTD once on a save-game they're re-using across multiple builds is a miracle.
I don't really care if there's 01_EMBASSY_PROPOSE and other such problems. The game looks functional to me.
I don't really care if there's 01_EMBASSY_PROPOSE and other such problems. The game looks functional to me.
- 11
I'd be interested to know how stable the stable build is. I saw someone mention that their change log was rather amusing.
Well, Paradox' games and DLCs are often buggy, because they are simply pretty complex.
Stellaris will likely be the same but a lot of the bugs from the Stream will be gone. They also already made changed because people pointed out some things during the stream.
- 1
Technically correct, but in reality all the bugs present in the nightly build need to be fixed before pushing to the 'develop' or 'qa' (idk PDS' terminology) build, so it is fair to look at bugs in the nightly build (which are generally going to be integration issues) as they will need to be addressed before the stable build is updated.
SO TRUE. Apart from having to make things IE8 compliant, having to make anything work with legacy code/db rows/management systems is my least favorite work to do. We literally just spent like 3 weeks 'fixing' a section of the DB that had out of date references before we could update the code we actually wanted to update. Legacy stuff sucks.
I've generally found PDS games to have very few bugs compared to most A-AAA releases. They have quite a good quality control system.
In addition-
4. Bug fixes are almost always much faster than pure development. Literally most bugs are 2-3 line changes that fix huge, glaring issues.
The Tax Form stuff I was working on today was completely broken, and deleting 3 out of date references and adding in 2 new lines fixed it completely. Bugs can be a useful measure of quality, however they can be incredibly deceptive as well, as a single thing wrong can break 12 different features.
All in all I'm not worried, PDS has proven worthy of my faith time and again
- 1
- 2
I think a big reason why they're releasing the game on a Monday instead of a Friday is so that they can issue any emergency bug patches. People don't generally want to work over the weekend.
- 3
Depending on the complexity of the code. If you are able to modularize the code well and have time to refactor periodically then it gets easier.Hunting for logic bugs in complex code can take weeks
Ah, yes, also a good way to spend a few weeks. Only for all the other systems you rely on to get changed by someone upstream with no notice
EDIT: Granted, the situation I have in mind is unlikely to happen in a small sized company where all the devs sit in neighboring cubicles.
- 2