I'm pretty sure there are a lot more than that but I guess most people only want to play and not contribute in any form or they aren't using Steam for that matter and therefore can't test, just like me.
I've been eagerly awaiting 2.6 for quite some time now but seeing Beamdog responding to and working on all the different feedback/reported bugs, I actually don't mind if they take a little longer and in return fix more bugs.
I'm pretty sure there are a lot more than that but I guess most people only want to play and not contribute in any form or they aren't using Steam for that matter and therefore can't test, just like me.
I've been eagerly awaiting 2.6 for quite some time now but seeing Beamdog responding to and working on all the different feedback/reported bugs, I actually don't mind if they take a little longer and in return fix more bugs.
Implying that they are obligated to be QA's/beta testers is straight forward wrong. This is not a free source community project where contribution is critical. We all paid for the game. Are we thankful they continue to improve it? For sure, but there is a line between that and doing the job of their QA team (if they have any at all tbh) and play it a beta tester.
Regadless, I have all of the games/addons for android and ios... so sadly I have no build to test really.
Neither was I implying that we are obligated to test nor is Beamdog trying to make us do their job, come on.
There's a reason that no software is without errors because no matter how big a QA team is, they won't be able to reproduce all possible constellations that could lead to bugs and therefore asking the community is just the right step.
If you just want to play the game and not report bugs or beta test, it's all good, do so.
We have 4 beta tests going at the same time, for each of these games. So we don't expect everyone will test everything. Actually, we don't have any expectation regarding numbers. The only thing we expect is that while the beta is available, there will be some players who would want to play 2.6 before it's released and report problems.
If you participate in the beta test, this is just great and we really appreciate it. If you don't participate in the beta test, this is perfectly valid and fine. Just play the game and have fun.
This thread is for BG2 and more people (I think) play BG1 during this (or any other simultaneous beta). We have more votes for the BG1 survey than the BG2 survey.
We also have people commenting on the Steam forum and making votes there, we'll add those to this forum's numbers if needed. But the numbers are not a self-target. The actual feedback is.
When players say: I don't agree with how X works, it should work this way instead, this is when we find out what the players want.
That is the way this forum has always been, from 2011. We're extremely grateful to all the people who value these games and continue to be enthusiasts when it comes to all the myriad of aspects of them.
I'm pretty sure there are a lot more than that but I guess most people only want to play and not contribute in any form or they aren't using Steam for that matter and therefore can't test, just like me.
I wouldn't mind testing and giving feedback either, but not really willing to open a separate steam account for it. I have the world's biggest backlog of games to play before returning to the IE games yet again anyway, so no rush as far as I'm concerned.
SPCL232 is inquisitor True Sight, actually. Priests of Helm get SPCL732 (named True Sight), which casts SPPR505D (named True Seeing) as its secondary spell. So both kits need versions of this cosmetic fix.
Both Inquisitors and Priests of Helm cast "True Sight" according to their kit descriptions. SPCL732.spl will now use "True Sight" SPPR950.spl once per round in all games. Should be fixed.
is there any way to test the brazilian portuguese translation? it has not yet been completed, but I would like to know if it is possible to test this new patch
16 more testers huh. Are there even that many people left in the forum community these days? Regardless, nice to see this finally getting closer
There are way more people than that. I'm one of them. Just have zero interest in testing; many people like me are using a heavily modded install that wouldn't work if we updated to 2.6.
Monitoring the situation until release to see if it's worth starting fresh. Eventually most people will switch once they know their mods will work. BTW, of course I didn't vote in the original post.
@tl1942 One little thought for you and other "let others do the testing" people. The slower the uptake of testing, the longer before a "stable patch" is released.
@TarotRedhand You missed the part where I said that I wouldn't be able to use patch 2.6 when it's released, and considering mod dependencies (I have over 42,000 files in my override folder), it's not 100% clear I'd ever to be able to use it. I'm actively working on testing and tweaking mods right now, that's where my testing time is spent.
I appreciate Beamdog's work continuing to update the game. They're awesome developers. I also deeply appreciate the testers. Just wanted to chime in that there are many people like me who play with very heavily modded installs who are monitoring the situation and won't be able to update any time soon.
FWIW I can't test this patch either as it's only available via steam and my copies of IE games are all on GOG. Having also got the original games as well, I am not going to buy them a third time.
There are many reasons not to test this patch besides modding issues. I for one hesitated then decided not to.
First, one might not know what to do exactly. Testing is not just playing the game, it's paying attention to the right technical details, being able to report them in an intelligible manner and possibly explain them. That isn't obvious to everyone.
Worse, it's easy to get discouraged. You may not realize this but reading some of the messages first page feels like double Dutch to some people. It really makes you feel like you don't belong. Of course this is not intentional and we're VERY lucky to have those people aboard, but some questions remain : what can you do next to these savvy folks when you barely know how to open an .ini file? What are the chances you'll spot anything that those people haven't already? What if you waste everyone's time by reporting things that aren't wrong? If you become available for testing like, today, isn't it a bit late? What is left to find out for someone like you when you show up so late at the party?
Of course these are rhetorical questions and I'm just describing the possible thought process of someone with good intentions but no certainties. Knowing the game by reading the official rules and knowing which are correctly implemented are two different things. You may be great at the former but lousy at the latter. I've seen many people in the past - especially before EEs - give excellent advice based on the official set of rules but fail because the game isn't following them in practice.
So laziness isn't the only reason to let others do the job. These forums tend to get nerdy so it's easy to forget. It'd be completely different if there were a precise request to reproduce a specific action in the game in order to collect feedback. I would help out in this case. But going blind today? Uh-oh!
Second, some people like to stop playing the game for a few months or even a few years so they can start again somewhat fresh. Of course you'll remember the biggest parts of the game but you'll rediscover other parts. In this context, testing is basically spoiling the fun for your next game if you're not committed to wait even longer before a new game. I'd have been MUCH MORE inclined to test if I hadn't already waited almost two years to play a new game. This is a big sacrifice when you're looking forward to playing again and you'll be even less likely to give it up if you't don't feel particularly useful doing so. Testing is ideal right after you beat up the game and this isn't the case for everyone.
Hopefully, this will never turn into a show of pointing fingers to explain why it's taking long.
Tried 2.6 on a desktop PC and laptop, both running Windows 10 Pro 64bit.
Fails to launch in Steam on both systems. No errors reported, just does nothing.
Tried uninstalling and deleting any left-over files, then re-installing. Same problem.
That is enough of this discussion of whether or not people want to help test or not. Let us focus on the actual testing and stop derailing this discussion. If you want to discuss this, do so elsewhere on the forums.
Tried 2.6 on a desktop PC and laptop, both running Windows 10 Pro 64bit.
Fails to launch in Steam on both systems. No errors reported, just does nothing.
Tried uninstalling and deleting any left-over files, then re-installing. Same problem.
Disable your antivirus.. yes, it sound silly. But i've had this exact issue with Steam before.
Could be something else but worth a try.
We've suggested some corrections for the English BG II strings within the Translation Tool. Hopefully somebody can approve them before the release of 2.6.
Comments
I've been eagerly awaiting 2.6 for quite some time now but seeing Beamdog responding to and working on all the different feedback/reported bugs, I actually don't mind if they take a little longer and in return fix more bugs.
Regadless, I have all of the games/addons for android and ios... so sadly I have no build to test really.
There's a reason that no software is without errors because no matter how big a QA team is, they won't be able to reproduce all possible constellations that could lead to bugs and therefore asking the community is just the right step.
If you just want to play the game and not report bugs or beta test, it's all good, do so.
We have 4 beta tests going at the same time, for each of these games. So we don't expect everyone will test everything. Actually, we don't have any expectation regarding numbers. The only thing we expect is that while the beta is available, there will be some players who would want to play 2.6 before it's released and report problems.
If you participate in the beta test, this is just great and we really appreciate it. If you don't participate in the beta test, this is perfectly valid and fine. Just play the game and have fun.
This thread is for BG2 and more people (I think) play BG1 during this (or any other simultaneous beta). We have more votes for the BG1 survey than the BG2 survey.
We also have people commenting on the Steam forum and making votes there, we'll add those to this forum's numbers if needed. But the numbers are not a self-target. The actual feedback is.
When players say: I don't agree with how X works, it should work this way instead, this is when we find out what the players want.
That is the way this forum has always been, from 2011. We're extremely grateful to all the people who value these games and continue to be enthusiasts when it comes to all the myriad of aspects of them.
I wouldn't mind testing and giving feedback either, but not really willing to open a separate steam account for it. I have the world's biggest backlog of games to play before returning to the IE games yet again anyway, so no rush as far as I'm concerned.
Both Inquisitors and Priests of Helm cast "True Sight" according to their kit descriptions. SPCL732.spl will now use "True Sight" SPPR950.spl once per round in all games. Should be fixed.
Unfortunately I can't reproduce the error. I've played for a couple of hours more and all went well. Perhaps is was simply a one-time glitch.
There are way more people than that. I'm one of them. Just have zero interest in testing; many people like me are using a heavily modded install that wouldn't work if we updated to 2.6.
Monitoring the situation until release to see if it's worth starting fresh. Eventually most people will switch once they know their mods will work. BTW, of course I didn't vote in the original post.
TR
I appreciate Beamdog's work continuing to update the game. They're awesome developers. I also deeply appreciate the testers. Just wanted to chime in that there are many people like me who play with very heavily modded installs who are monitoring the situation and won't be able to update any time soon.
TR
First, one might not know what to do exactly. Testing is not just playing the game, it's paying attention to the right technical details, being able to report them in an intelligible manner and possibly explain them. That isn't obvious to everyone.
Worse, it's easy to get discouraged. You may not realize this but reading some of the messages first page feels like double Dutch to some people. It really makes you feel like you don't belong. Of course this is not intentional and we're VERY lucky to have those people aboard, but some questions remain : what can you do next to these savvy folks when you barely know how to open an .ini file? What are the chances you'll spot anything that those people haven't already? What if you waste everyone's time by reporting things that aren't wrong? If you become available for testing like, today, isn't it a bit late? What is left to find out for someone like you when you show up so late at the party?
Of course these are rhetorical questions and I'm just describing the possible thought process of someone with good intentions but no certainties. Knowing the game by reading the official rules and knowing which are correctly implemented are two different things. You may be great at the former but lousy at the latter. I've seen many people in the past - especially before EEs - give excellent advice based on the official set of rules but fail because the game isn't following them in practice.
So laziness isn't the only reason to let others do the job. These forums tend to get nerdy so it's easy to forget. It'd be completely different if there were a precise request to reproduce a specific action in the game in order to collect feedback. I would help out in this case. But going blind today? Uh-oh!
Second, some people like to stop playing the game for a few months or even a few years so they can start again somewhat fresh. Of course you'll remember the biggest parts of the game but you'll rediscover other parts. In this context, testing is basically spoiling the fun for your next game if you're not committed to wait even longer before a new game. I'd have been MUCH MORE inclined to test if I hadn't already waited almost two years to play a new game. This is a big sacrifice when you're looking forward to playing again and you'll be even less likely to give it up if you't don't feel particularly useful doing so. Testing is ideal right after you beat up the game and this isn't the case for everyone.
Hopefully, this will never turn into a show of pointing fingers to explain why it's taking long.
Fails to launch in Steam on both systems. No errors reported, just does nothing.
Tried uninstalling and deleting any left-over files, then re-installing. Same problem.
Disable your antivirus.. yes, it sound silly. But i've had this exact issue with Steam before.
Could be something else but worth a try.