New SDK Beta (World Builder, etc.)

Awesome. Been wanting to try out some custom maps in the worldbuilder, great to have an update.
 
I just got an update for the SDK and the list of my mods have disappeared from it, when I click publish to Steam workshop.

Anyone know how to fix this?

Edit:

It fixed itself no worries.
 
Okay, just to confirm some things, I just stripped the map of all features and Start Locations, meaning it was just landmasses and in the scenario data specific custom civs (no start locations so just spawning at random), and there are still no barbarians. It seems it is not linked to start locations, but simply anything with scenario data. If you must click Load Scenario, you do not get barbarians :(
 
I made a mod with SDK (Sinusgamma's Balanced Earth / Steam Workshop). I have barbarians, so the solution works for me, but I have a new problem:
- When I choose production in a city, the production doesn't show up in the city-banner that turn. Next turn I see it. And the same is true with the city-state relations. When I improve the relation with gold, the game know it, but the city-state banner doesn't upgrade that turn.

Is it because of the SDK beta, or I made some mistake?

(I have custom city-states.)
 
If we update to the beta right now, will the world builder automatically update to the new version once it's released?

And speaking of the full release, any ETA on the new version of the world builder?
 
Via SamBC over at the 2k Forums -

The barb issue has a workaround - make sure your major civs are all on teams below 22 (0-21), and CS on teams 23-61

This did work for me, and it sounds similar to tedoll78's explanation

Okay.. after another half-day of experimentation with World Builder and different game setup configurations, I think I have discovered something else about our barbarian situation that has me pretty hopeful about a solution.

The pivotal moment came when I decided to make a huge map with designated starting points for each player. Raging barbarians was selected as an option. As usual, I used 18 city-states and 18 civilizations.. but this time, I decided to place the city-states on Teams 1 through 18, with the civilizations being placed on Teams 19 through 36. When I began the game, barbarians wouldn't spawn, as usual, but I noticed on the score list on the right side of the screen that there was a unique entry for Team #22.

So I went back into World Builder, added a Team #37 (the same civilization as Team #22) - and then erased Team #22. There was no longer a Team #22 in the game. (While there, I also gave myself just enough culture so that I could immediately adopt the barbarian-revealing Honor policy on Turn 1, and then gave myself a starting unit with ultra-vision and hovering status so that he could climb up a mountain to reveal a huge chunk of the map before returning to level ground).

When I began the next attempt, I could see that there was no longer an odd designation/indentation for Team #22 on the score list. On Turn #1, I have my uber-vision unit climb up and down a mountain to reveal a huge chunk of the map. On Turn #2, the honor policy showed that a handful of barbarians generated around the revealed areas of the map. On Turns #3 and thereon, more barbarians generated. Success!?

I have since replicated this success with several maps, with and without various mods enabled. We might be remarkably close to this being a decent workaround for the issue. It would allow placement of each player on the map, separate teams for everyone so that normal diplomatic gameplay is restored, full barbarian generation, etc.. but I'd like to see some folks from the forums try to duplicate the results on their own.

Here's hoping that this helps.. cheers.

I guess I just didn't understand tedoll's explanation as well as I did SamBC's!

but hooray! Barbarians are back on my map!
 
I can load the loading screen but when I click world builder it crashes immediately since the recent beta was released. It's also sad that I can't use the older version because that one was running fine.
http://www.flickr.com/photos/77519782@N02/9352540588/
9352540588


Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: WorldBuilder.exe
Application Version: 1.0.4931.20465
Application Timestamp: 51d2fe33
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: e0434f4d
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105

--------------------------------------------------------------------------
Also details about my comp if they help
- Windows 7 64bit
- 6GB RAM
- HP Pavilion dv7 Notebook PC
- AMD A8-3500M APU with Radeon(tm) HD Graphics 1.50 GHz
 
I can load the loading screen but when I click world builder it crashes immediately since the recent beta was released. It's also sad that I can't use the older version because that one was running fine.
http://www.flickr.com/photos/77519782@N02/9352540588/
9352540588


Description:
Stopped working

Hello there, same problem.

Since installing BNW - World Builder simply does not launch, but I get the same problem as you have experienced. Running Windows 7, 64 Bit.

Looked around for various "fixes". but have not yet found a thing that worked.

:cry:
 
We have a build up behind a new beta if you would like to see if it addresses your problem.

1. Right-click on the "Sid Meier's Civilization V SDK" link in Steam, and select "Properties".
2. Select the "Betas" tab
3. Enter the password "worldbuilder", and click "Verify".
4. If the password is accepted, then select "worldbuilder" from the pull-down list, and click "close".
5. Restart your steam client.

The new build should download. Start it up, and start World Builder. To verify that you have the correct version of World Builder, you should see yesterdays date (7/23) in the title bar when it launches.

Let me know
 
We have a build up behind a new beta if you would like to see if it addresses your problem.

1. Right-click on the "Sid Meier's Civilization V SDK" link in Steam, and select "Properties".
2. Select the "Betas" tab
3. Enter the password "worldbuilder", and click "Verify".
4. If the password is accepted, then select "worldbuilder" from the pull-down list, and click "close".
5. Restart your steam client.

The new build should download. Start it up, and start World Builder. To verify that you have the correct version of World Builder, you should see yesterdays date (7/23) in the title bar when it launches.

Let me know



This works.
 
So far so good...Worldbuilder launched from Steam (thank god!) but still waiting to see if my maps will spawn barbarians now.
 
So far so good...Worldbuilder launched from Steam (thank god!) but still waiting to see if my maps will spawn barbarians now.

The barb issue has a workaround - make sure your major civs are all on teams below 22 (0-21), and CS on teams 23-61

and of course you wouldn't have to fill all 1-21 slots with major civs, for example my map has 13 majors and 24 CSs, I put the majors on teams 1-13 and the CSs on teams 23-46 and barbarians are spawning just fine now!
 
I'm still having to use the -PromptForGamePath workaround posted back in March on the 7/23 beta.

However, It does load much faster than the older builds (usually within 10 seconds instead of 2 minutes). If you need anymore information, or if there's a better place to report this I'd be more than happy to comply.

Edit: I'm also getting the Old Faithful bug bmullins0118 brought up. Never had it before.


Ok, WorldBuilder was hanging because I had "\dx11" in my launch options for the game under Steam. I removed that launch option from the game under Steam, which lets WorldBuilder launch without issue.

I then made a new shortcut, for the game itself, with the following target:
Code:
C:\Games\Steam\Steam.exe -applaunch 8930 \dx11

I fully expect the next Steam update to break my shortcut (again) :lol: but WorldBuilder and the game's shortcut are both working properly (for now). :crazyeye:

I'll report back on whether or not this fixes the Old Faithful bug for me after I've done some more testing (I do know that with my previous setup, the DX11.exe was running with WB, where now the default .exe is running when I launch WB).

Edit: Still getting the Old Faithful bug.
 
So, in the new patch today the Farm Crash was fixed, and the DLL was updated, but the SDK has not received an update. Is the SDK (and specifically, the DLL source) going to be updated sometime soon?
 
Back
Top Bottom