In 2.3, you can greatly decrease lag problems in Multiplayer: - don't use any container on clients' characters - always let the host loot everything - don't save when a party member is dead - preferably, use party members 2-4, not 5-6 for clients
I have personally played 2.3 from Candlekeep to the Throne fight in Multiplayer, so you should be fine.
Thanx for all these tips. However, the beta should be ready for GOG also soon no? For me, slots 2-3 are the ones working without lag (slot 4 lags).... makes any sense?
No, my friend. I'm pretty sure that the beta will never be available on gog. I'm certain that you will get the final product on gog, but not the beta.
While IWD:EE 2.5 obviosly needs some love and work, there're potential unexpected bugs in BG:EE and BGII:EE as well, which need testing.
Just yesterday I reported a bug with the initial ambush scene with Dorn in BG:EE, which certainly was unexpected (and it was not a camera issue). I bet BG:EE and especially BGII:EE, as the game which is usually being tested by players less, still contain a lot of surprises.
Also, Multiplayer needs testing, as there're many potential MP-related issues not reported, and those issues are, most likely, not regressions.
So there're definitely more issues than only regressions in not only IWD:EE 2.5, but BG:EE and BGII:EE 2.5.
@JuliusBorisov What will happen to all bugs report posted on redmine a several month ago. Will these bugs ever be fixed? Do They plan to restore Catmull-Rom scaling algorithm and fix blurry issue (Feature #26800) (internal #30719) (Bug #32711)?
Full patch notes for each game will accompany the full release of the 2.5 Update
Worried about a fix or feature that didn’t make it into 2.5? Worry not! We’ve been listening to and recording your feedback this whole time, and we have some exciting plans for more Infinity Engine updates to come. Stay tuned!
After the holidays the team will review the feedback to this beta. They have been still adding to the list of fixed (in the full release) issues before the holidays.
After the holidays the team will review the feedback to this beta. They have been still adding to the list of fixed (in the full release) issues before the holidays.
Some features or bugs can wait for after 2.5 but I really think (and I'm not the only one @Adul@AndreaColombo@Parys@Pecca@Kilivitz ) that the scaling issues should be top priority and should be fixed for 2.5.
Anyway is any hope for redeem GOG version for Beamdog client? This should help in many cases. I mean somethings like your politic but in reverse way - buy on beamdog drm-free and request for steam key - so buy on gog or steam and request a beamdog client redeem. Is any hope?
Beamdog can verify that you have purchased the Beamdog version. They cannot verify that you have purchased the GoG version. So it's unlikely that that'll happen.
Even if you're not getting in the Beta, you'll get the proper patch once it's released.
After the holidays the team will review the feedback to this beta. They have been still adding to the list of fixed (in the full release) issues before the holidays.
Some features or bugs can wait for after 2.5 but I really think (and I'm not the only one @Adul@AndreaColombo@Parys@Pecca@Kilivitz ) that the scaling issues should be top priority and should be fixed for 2.5.
Agreed. And since the scaling problem has been in the game since the 2.0 update, it would be great to see all the amazing SoD backgrounds that the talented people at Beamdog created in-game without the blurriness for the first time.
so was that tob bug where after you beat the final boss, after the solar talks, she starts attacking you again and you have to loop the conversation again [ by talking to the solar again.] to make it go to the final choice fixed yet?
Guys, I've got UI issues here. UI backgrounds appearing with a time lag, flickering UI... is it just me (my BG1 EE SOD is heavily modded after all) or have others reported things like this as well? Sorry, cannot look closer this week,.. that's why I ask.
After the holidays the team will review the feedback to this beta. They have been still adding to the list of fixed (in the full release) issues before the holidays.
Today will most likely be the last day of the beta (I will know better later). Don't forget to share your impressions (or updated impressions) in the survey.
This is a rather rough count, but I've come to the following numbers based on redmine. These are submitted bugs only, which means that they are in the internal tracker and thus truly a bug (but also include some features). I've left out the open bugs/features as the devs first need to determine if those are truly bugs or just someone's apparatus being wonky or whatever other reason. I've looked at the 'created at' date to see if they could be related to 2.4/2.5 patches. Might be off by some.
BG: 241 submitted bugs (19 from 2.4/2.5, therefore 222 v2.3 and earlier) BG2: 110 submitted bugs (9 from 2.4/2.5, therefore 101 v2.3 and earlier) IE: 168 submitted bugs (51 from 2.4/2.5, therefore 157 v2.3 and earlier) IWD: 51 submitted bugs (39 from 2.4/2.5, therefore 12 v2.3 and earlier)
But it could very well be that stuff is already fixed but not marked so in Redmine. Bugs fixed in next update: 220.
I have two questions: Will the regressions introduced in the 2.5 update be fixed before the release? Will the background and sprite scaling issues be fixed for the 2.5 update?
End of the beta does not necessarily means the official v2.5 version will be released immediately. We will probably see some more fixing going on before the final release.
From the blog:
What’s next for the update? The team is currently going over all the feedback players have given in the Beamdog forums, Google Play, and through the 2.5 update beta survey. Developers are hard at work fixing issues found by the community and adding more fixes to what will become the 2.5 update final release. We’ll have more to share timeline-wise as we get closer to release.
Beamdog devs: please, please for the love of Helm bring back the full hotkey functionality we had pre-2.0. Please? There's no logic to limiting us to original BG hotkeys and its hell for lefties. Thank you for listening.
Comments
In the meantime, I'm working on my UI mods to make them compatible with 2.5
While IWD:EE 2.5 obviosly needs some love and work, there're potential unexpected bugs in BG:EE and BGII:EE as well, which need testing.
Just yesterday I reported a bug with the initial ambush scene with Dorn in BG:EE, which certainly was unexpected (and it was not a camera issue). I bet BG:EE and especially BGII:EE, as the game which is usually being tested by players less, still contain a lot of surprises.
Also, Multiplayer needs testing, as there're many potential MP-related issues not reported, and those issues are, most likely, not regressions.
So there're definitely more issues than only regressions in not only IWD:EE 2.5, but BG:EE and BGII:EE 2.5.
You all are helping greatly!
What will happen to all bugs report posted on redmine a several month ago. Will these bugs ever be fixed?
Do They plan to restore Catmull-Rom scaling algorithm and fix blurry issue (Feature #26800) (internal #30719) (Bug #32711)?
Still no beta for GOG?
Anyway is any hope for redeem GOG version for Beamdog client? This should help in many cases. I mean somethings like your politic but in reverse way - buy on beamdog drm-free and request for steam key - so buy on gog or steam and request a beamdog client redeem. Is any hope?
Even if you're not getting in the Beta, you'll get the proper patch once it's released.
Tempus thanks you.
These are submitted bugs only, which means that they are in the internal tracker and thus truly a bug (but also include some features). I've left out the open bugs/features as the devs first need to determine if those are truly bugs or just someone's apparatus being wonky or whatever other reason.
I've looked at the 'created at' date to see if they could be related to 2.4/2.5 patches. Might be off by some.
BG: 241 submitted bugs (19 from 2.4/2.5, therefore 222 v2.3 and earlier)
BG2: 110 submitted bugs (9 from 2.4/2.5, therefore 101 v2.3 and earlier)
IE: 168 submitted bugs (51 from 2.4/2.5, therefore 157 v2.3 and earlier)
IWD: 51 submitted bugs (39 from 2.4/2.5, therefore 12 v2.3 and earlier)
But it could very well be that stuff is already fixed but not marked so in Redmine.
Bugs fixed in next update: 220.
Will the regressions introduced in the 2.5 update be fixed before the release?
Will the background and sprite scaling issues be fixed for the 2.5 update?
From the blog: