Greetings!
We have made Beta 1-Z4 available.
General Overview:
Caveats:
Here’s what’s new since the last update:
- Elemental 1Z Update #5 Change Log -
* New Features *
+ Added and implemented the new quest screen (Work In Progress)
+ Hooked up very basic lore book wnd, will serve as a way to get details about a bunch of stuff in Elemental, but for now it is just a screen that pops up in place of the unitequipment wnd when you click on the center medallion for a unit that doesn't belong to you
+ Unit Details Wnd: hooked up new backstory section that Paul added to the screen.
+ instead of unhiding a simple message box when you press the recruit button for a selected NPC, it will now bring up the conversation wnd
* Bug Fixes *
+ Fixed distance fog on characters in unit scene view windows + Fixed missing heads on units used in quests (damsel, son, daughter, etc) + The camera should now properly focus on the center of a tile when positioned by tile. + Fixed bug where changing the race or gender of a sovereign you are customizing in the customize sovereign screen would not refund the item cost of any equipment that ended up being removed + Fixed a crash that would occur in CTerrainGraphic::ReleaseTerrainEffects( ) when attempting to exit the game.
+ Fixed a problem in CWaterGraphic that was preventing the water from rendering off the north edge of the map.
+ Made the changes I made to allow setting a destination during a unit's movement between turns only apply when the unit is using the new auto patrol along path directive, instead of any directive, in case there is a reason why those might need to skip moves that I didn't see when scanning the code, making it less likely to get a stuck turn button if I did miss something.
+ Changed the check I added to Move and CheckNextTile to handle skipping leftover moves differently only if the directive the object has is the patrol along path directive
+ Limited the delta times on character graphics to cut back on animation blending wierdnesses (ie, swords sticking in and out of unfortunate places)
+ Fixed bug where using the "Unit Scale" option would cause clothing and items to scale in wierd ways on a unit's gfx
+ Fixed an issue with quest-related goodie huts and quest locations not disappearing if they were cleared during the auto-turn phase.
+ Removed call to CWorld:laceResourceHoardsInClumps( ) in CIsReadyToStartProcess::OnUpdate( ), which was placing extra resources on the map after generation and the player locations had been chosen.
+ Fixed a problem where a dialog on encountering neutral cities was popping up twice. The problem was that the unit wasn't losing its movement after the first encounter.
+ Fixed ref-counting errors in cheat key and key callback code
+ Creature race skips expensive calculation in CalcResearchPointsPerTurn and automatically returns 0 + Creature race skips expensive calculation in GetPopulation and automatically returns 1 (so other parts of code do not think race has died out) + Fixed ref-count error in Portrait Generator + Added more debug data to error message in SetDXSASEffectUIParameterValue
+ Fixed bug where clicking on a city with multiple units stationed would cause the units to unstation on top of the city and not return, from calls to get the city battle rank for the UI that would gather the unit defenders but not replace them - To fix this, I added a function to CCity to just calculate the battle rank, and when the city gathers its defense army now, it doesn't unstation the subunits - Also, it doesn't bother recreating graphics, refreshing UI, or setting destinations while gathering this army, making the assembly of forces quicker - This also happens to fix a bug where the subunits of the city defense army were not getting any of the city's defense bonuses, only the leader got them, because they were no longer considered stationed in the city
+ Fixed crash where unit was deleted at wrong time + This was caused by an extra release call in the ::AutoResolveBattle function
+ Fixed several other reference-related errors
+ Fixed bug where destroyed units were added to population in CPlayer::GetPopulation
+ Fixed bug where destroyed units were added to research in CPlayer::CalcResearchPointsPerTurn
+ when loading a gamesave, now stopping the xml file loading thread, in case it's still running as is the case when you've just started up the game and immediately tried to load a gamesave from the main menu. Previously, it would wait for the load xml file thread to finish before loading the gamesave. The load code clears and then loads in xml data directly from the gamesave, so waiting for the xml file loading to complete is a waste of time. + added some output messages throughout loading of the gamesave, so I could see that the game was not frozen
+ Fixed ref count bug in GetCityDefenders
+ Fixed bug where equipment on pewter pieces did not scale correctly (ShowStopper #3) + Fixed bug where blank designs showed up in the unit design lists (ShowStopper #5) + Fixed bug where if you play as a race with a custom sovereign, then delete that sovereign and play against that race, that race would not get a sovereign - It now randomly picks a sovereign unit if it is unable to find the sovereign that is specified in the race XML
+ Units don't remove themselves from their player list in SetDestroyed anymore, player removes destroyed units itself at the end of a turn (which apparently it was already doing, its just that the units were removing themselves first) + Added health regen stat for unit, and since now it can be negative, units can die between turns, hence the reason why players need to wait to remove units now + Sovereigns still won't die if they lose all their HP from a disease or something, will go back to nearest city with some different msg + Fixed some UI and graphics bugs with killing and removing units from armies + When a subunit dies, they remove themselves from their army now + Fixed bug where UnlockImprovement modifiers wouldn't work if attached to a sovereign talent, since player modifiers from that aren't applied, now checks the sovereign + Fixed bug where the same modifier instance would be applied to units at the same tile, so durations would get decremented too many times + Added spell effects to the unit stat breakdown tooltip, and a place for modifier appliers to set this info when creating an instance to support that + Fixed wonkyness when unstationing units by setting a destination outside of the city perimeter, now will still teleport the unit outside of the perimeter and have them form armies correctly, but will reset the destination so it doesn't get cancelled out of the blue
+ Fixed crash in city wall code where index was out of bounds of array
+ Fixed the city build list not going to scroll mode when it gets too tall.
+ Fixed a buffer overrun in CCliffGraphic::GenerateCliffTiles( ) that could occur when running the game in basic mode.
+ Fixed a crash when upgrading a lot of city improvements at once; this was due to the walls getting regenerated after every deletion and construction. + Altered the upgrading code to, instead of deleting the current improvement and making a new one, simply pointed the improvement at the new improvement type and reset the improvement data. This makes upgrading MUCH faster now.
+ when recruiting a unit, it was pointed out on the forums that he would not provide non-FOW around him until you move him once, making it possible to lose him under FOW. I added code to fix this when a unit is traded from one player to another.
+ fixed a typo that was reported on the forums, "Rouge Scholar" should be "Rogue Scholar"
+ if a city capital is taken, the player will automatically pick a new capital + CPlayer::GetCapitalCity() now actually loops through the player's cities and finds the capital (before it would assume the first city in the array was the capital) + made UIRefreshEmpireTree() that initalizes and refreshes the list of the player's capital is taken + if a player dosent have a city and takes one, it becomes it's capital
* Gameplay Tweaks *
+ Increased distance between cities requirement from 4 to 5. + Changed Relias backstory and info. + Changed backstory of Altar and Pariden
+ Created new unique sovereign armor
+ Added shop values to various equipment + Removed extra shard improvements that were causing duplicate game modifier bonuses
+ Changed the unique resources text to make it more apparent that they must be part of a town to receive the bonus. + Removed normal armor from Sovereign Customization + Moved AI Data to bottom of Study Improvement XML
+ Added a new spell (Freeze Enemy). + Added the correct icon to Burn Enemy. + Added a new modifier type (ZeroTargetMoves) that will have some value driven chance to remove all moves left on some unit
+ Tooltip for city shield displays combat rating for city.
+ commented out most tech prereqs for existing NPCs. Brad wants the npcs to show up at game start. Now they will since they don't require a tech in order to spawn. I did leave the tech prereq for the two NPC types that lead a party. They require "Heros" be researched in order to spawn.
+ City Details button displayed for AI cities as well + Wages now displayed as a float instead of integer + Granaries require at least a village to be built + Brad has officially started working on the AI. ? + CoreAIDefs created (new file coreAIdefs.xml) + AI Personality “AI_General” defined + AI definitions for how to build up cities created + AI definitions on what technologies should be researched created + AI attributes added to CoreTechs.xml + AI attributes added to improvements + Market requires at least a village to build + Elder Council requires at least a village to be built + Monastaries require a village to be built + Warehouse requires at least a town + Arcane Insitution requires at least a town + Barracks now requires at least a town + Adjustment to costs of weapons + Magical Equipment Crystal costs adjusted (to 1 crystal) + Unit wages increased to 0.20 per turn. + AI: More intelligently targets cities (should eliminate obvious “train of death”) + Markets no longer cost gold to build but take longer and require more materials + Further Technology tree cleanup
+ Added Disease Enemy spell
+ Modified the base kingdom tech tree + Changed Unit Grouping Type prereqs + Modified health stat game modifier for Unit Types
+ Adjusted weapon preqreqs for new tech tree + Changed various improvement prereqs + Removed Old Palace and Inn improvements + Altered the formula for computing the combat rating that should make it more realistic.
+ Boots are now located in CoreAccessories.xml + New Armor and Weapon types created
+ Removed Kraxis gloves from Sovereign Creation screen
Screenshots from build:
What’s Next:
If this build seems reasonably stable, then we are going to proceed to beta 2 which is the multiplayer beta. We expect the MP specific beta to only last 1 or 2 weeks (we’ll be testing multiplayer throughout the process) but basically beta 2 is primarily the cue for us to make the multiplayer code available to you guys and then move forward from there.
Beta 3 will be the first “beta” that conforms to what most people consider as a beta as opposed to what we’ve done here which is essentially get players involved at the alpha stage. I cannot even begin to express how instrumental the beta group has been to changing the gameplay for the better.
Since Beta 1, the economic, research, and spell system has been completely reimagined based on feedback, debates and discussions by beta testers on the forums. Even when we don’t participate in a given discussion, we read them with great interest. Based on how well the Elemental project has gone, we are considering having the next game bring players in even earlier in the process (i.e. at the prototype level – pre-alpha).
I think when we hit Beta 3, users will find that the gameplay is very mature for what is a new IP. There is still some wiggle room based on player feedback but Beta 3 will mark the roughly (give or take a week or two) the 90 day countdown from release. However, we’re not promising Beta 3 at a specific date since we have to make sure we’re satisfied with the game mechanics and basic stability sufficiently enough to proceed.
Beta 1Z4 also marks the last public build without AI. Subsequent releases will begin to have intelligent computer AI that will continue to get better between now and release and then further beyond after release.
Let us know what you think.
Cheers and good luck!
I just played a game for well over a 1000 turns...seems stable.
I'd love to be able to agree with all you guys about the stability, but I'm 0 for 2 on completing games without crashing. For me it's the out of memory error that does it. I'm on Windows 7 64 bit, in case that is relevant.
I crashed once because of "out of memory" error, but could load autosave well and finish the game very stable in my opinion
So basically I won't be able to do any serious studying during the summer semester.
Just worked on a 500+ game, re-loaded it 2X to get that far. Posted a Debug after an DX error. I was playing vs 3 Factions with all graphic items on. Full window, anti-aliasing 4X, Lighting one, etc. etc.
I will turn some stuff down and see if it holds up better.
Stability gets a thumbs up from me.
Started a new game. Turned it down to 2 factions, no AA, Windowed mode, Lighting off and got a Conquest Victory. 3 reloads needed. Almost 800+ Turns.
I think this is ready for multiplayer. It's fairly stable, and the bugs that remain are not too huge.
I was able to go almost 1000 turns before it crashed on WinXp so the stability is improving.
XP user here and every previous 1Z build has had me crashing every 10-20 turns. 1Z4 is a vast improvement, I've played two long games to completion with zero crashes so far, definitely ready for Beta 2 from my perspective. Wish I could get it to last 1000 turns before killing the AIs, it's just too easy..
XP user here, and I'm still crashing like wildfire on 4Z. Don't know why, sent in my bug reports, have the latest drivers, etc etc.
XP user - played a couple of games to completion, no crashes (though I also had relatively few crashes with the previous versions of 1Z too.)
The only major problem i've noted so far is the game still crashes if I check the full screen box. However unchecked I have yet to crash with 1z4.
I vote that they should wait longer. I haven't had any crashes but I would just like to see the game more complete before beta 2.
Win 7 user here.. 1Z4 is fairly stable, i agree with that. Nice improovment in game even from 1Z3.. But my 1Z3 i playd several times, and it never CTD.. It just froze.. 1Z4 actually had a CTD after several 100 turns.. Improovment for the better. And I also think we can start working on the Multiplayer beta.. The stability will be fixed along those other betas too i think.. Great job as usual Stardock.
Did an update just come through?
What's a reasonable standard for 'stable enough', from a single players perspective? (serious question).
I just made it to turn 501 with no reloading/restarting before a game-ending problem (froze up) -- is that 'good enough'? Or is 1000 turns? Or...?
Once that's determined, what % of the testers should meet that standard?
I just noticed the update too. Can't find any mention of it here (I'm guessing they're too busy working -- on Mother's Day sunday night no less -- to post about it yet).
Well then you have not been paying any attention to the criteria that STARDOCK (you know, the guys making the game?) wants as a determination of whether to move forward. They are not going to "complete" the game any more in beta 1 either way, it is ALL about stability. And they have already made it clear that their internal; builds that we don;t see, the game is MUCH further developed than what we are seeing. So if you are wanting to see a more complete game, you should be voting FOR beta 2 so that we can get to beta three and then you can start to see the REAL state of the game.
With beta, devs only want to know if players can connect, play a bit, finish a game, that kind of things. So you're not even obliged to finish a game to test multiplayer plumbing.
At the moment the game is fairly stable (500+ turns without hanging, fast turns, fast movement, a lot less glitches) and save game work as intended .. when it's manual saves. Auto saves sometimes mess things up.
All in all I would vote for beta 2.
This version is by far the most stable of the 1Z beta releases on my Windows XP machine. I'd been unable to go more than 10 or so turns with the last two updates, but this one can easily go into the hundreds of turns without any real issues. For me it's definitely solid enough to move into beta 2, so great job!
One (reported) CTD, no other problems in however many hundreds of turns. It's a go from me
Yep. Probably some minor bug fixes? I don't know, but "View History" offers no new informations.
Unfortunately, it crashes for me every time in the world build stage so Im totally stymied.
tom
There are many great features available to you once you register, including:
Sign in or Create Account
