[Scenario Editor] Terrain appears black until other bugged terrain placed

Age of Empires II: DE II - Report a Bug
#1

:arrow_forward: GAME INFORMATION

  • BUILD #: 42848.0
  • PLATFORM: Steam
  • OS: Windows 10

:arrow_forward: ISSUE EXPERIENCED

Placing down certain terrains (A lot) they appear as if they were black terrain (besides the edge which merges with other terrain, those work). When placing other terrrain against it, it turns to normal terrain.

Edit: After a terrain has been ‘converted’ to normal, it stays that way. Only terrain that appears as black can reset the other terrain that was black before (as shown in the images below). Terrain that works properly does not reset the ‘blackness’.

Edit2: The bugged terrain (that’s placed last) doesn’t have to touch the current bugged terrain. It’s just the last placed bugged terrain that appears blacked.

Edit3: This is a purely visual bug, reloading the map or just play the game the terrain looks normal. It’s purely placing terrain in the editor

Edit4: Can’t seem to reproduce anymore.

:arrow_forward: FREQUENCY OF ISSUE

EDIT 4: After multiple restarts I’m unable to reproduce this. I think textures weren’t loaded properly.

  • 100% of the time, with ~90% of all terrain types

:arrow_forward: REPRODUCTION STEPS

:question: List the DETAILED STEPS we can take to reproduce the issue… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Create scenario
  2. Select terrain
  3. Drag and see black
  4. Select other terrain
  5. Drag against it

:arrow_forward: IMAGE & ATTACHMENTS

Before:
image

Selected Forst, Baobab and dragged it

image
image1386×701 308 KB

Now selected forest, bush and dragged the terrain against it.

image
image1584×717 464 KB

3 Likes
#2

Generate random maps a few times and the bug will appear

#3

Hi there! It looks like you are playing on a much older version of the game (37906) than is currently available (42848). If you have disabled updates, I would recommend ensuring that you’ve updated to the latest version to make sure you’re working with the latest changes.

1 Like
#4

Woops. I’m on the newest patch - I was reporting mulitple bugs and just copied the header. Must have copied it from an older patch. Sorry! It’s definitely happening on the newest patch :sweat:

Edit: Edited version of main thread

1 Like
#5

To confirm: you are NOT seeing the issue anymore? Did you verify the integrity of the game files or do something else to remedy the problem?

#6

No, what they said is that they ARE seeing the issue on the current patch and just reported the wrong game version.

1 Like
#7

I had this problem this patch. I didn’t do anything but restart the game. So it did happen this patch. That said, I haven’t had it happen again.

1 Like
#8

Problem still exists. A fix would be nice.

2 Likes
#9

This bug seems to be fixed in the latest pup_march build. If you have time, give it a try. I wasn’t able to reproduce this bug anymore.

1 Like
#10

After generating a hundred or so maps (In pup_march) from different RMS scripts and different sizes without running into the error, I assume it has been fixed indeed

1 Like
#11

Save map. And then leave. It’s fine. That’s how I fixed the issue anyway.

#12

Yeah, that’s the workaround. Although when working with maps, having to constantly reload the map isn’t very helpful. So really happy it appears to be fixed in pup_march :smiley: