Ghost tiles spawned when painting on a tilemap in prefab mode

Hi everyone,

When painting in prefab mode on a tilemap, the brush tool spawns ghost tiles right after painting.
If I click and move my cursor immediately after releasing the click, ghost tiles are spawned over the course of the cursor.

Those ghost tiles disappear when I hover over them with the brush tool and only the brush tool.
If I hover over those with the eraser (or any other tool than the brush), it won't do anything.
And obviously, I can't erase them as they don't exist.

 

Here's the bug report :
1117888

 

Note that posting the link to fogbugz allows everyone to see all of your bug reports.

I generally don't care that people can, but the mods tend to assume that you messed up when you post the link, so ymmw. You can just post the ID of the bug report (1117888 in your case), and Unity staff will be able to find it.

 

Ah ok. Thanks, I didn't know that.

 

Sure thing, I hope it helps.
If you need anything else, don't hesitate to ask.
(Don't forget to activate the subtitles, I'm commenting along the video)

 

Hi, just wanted to know if there were any news on this tile issue.
Thanks.

 

Thanks

 

I don't know if it's related, but I also have some major graphic bugs on the game view when I edit a tilemap in prefab mode.
It can display tiles that are not even related to the one I'm painting.
I reckon it might be related to the bug you fixed, but I wanted to give you the info in case it's not.
Thanks again !

 

I would like to say that I love the fact that us users are able to talk to you guys and have such fast feedback (not only for that particular case).
I know it's what forums are for, but I really do appreciate it.
I don't see that comment a lot, and I assume that's obvious to think but I wanted to say it

 

Here's a video with some bugs I could reproduce.

 

A little bit off topic but there's something that's bothering me for quit some time.
In the tile palette, if I click on a tile, it automatically uses the eyedropper (to pick the tile) and get back to the tool previously selected. Which is fine when I have the brush tool selected.
But when I have the eraser tool active, I think it would be better to switch to the brush tool when I click on a tile.
I never found myself wanting to have the eraser tool selected when I click on a tile. I always want to paint the given tile.
What do you think ?

 

Here's a video to explain better what I meant.

Thanks again for being around
(don't forget to activate caption)

 

That's fine, thanks again for taking the time.
Do you have a rough estimate of the Unity version those features will be implemented in ?

 

Thanks

 

Hi ChuanXin,

First of all, thanks again. I just updated my project on 2019.1 and the tilemap issue is gone for good. That's great
But I stumbled upon a couple of weird issues.
The most annoying one is that my project is now limited to 30fps in build. I tried in a blank project and the problem remains. No matter what Vsync count parameter I pick, it's still limited at 30fps in build.

EDIT:

The changes you made are great, unfortunately we'll not be able to use them. 2019.1 is way too buggy.

There is this framerate problem, but there is also a sound problem (AudioSource.PlayOneShot seems to skip part of sound sometime).

I also have methods using Time.DeltaTime before that worked fine and now it's super slow in game.

For all those reasons I'm forced to go back to 2018.3
I hope those are little things to fix because the others upgrades are cool.

EDIT²:

I found out what was wrong about the framerate issue. In 2019.1 when I have an additional monitor plugged in (HDMI) and I duplicate my display, the framerate of my builds is limited at 30fps. (in 2018.3 it worked fine. I used to playtest on my secondary monitor).

I also found out about the sound issue. It seems that in 2019.1, AudioSource.PlayOneShot is not as efficient as in 2018.3. The more gameobjects (sprite with animator) there is in the scene, the more buggy the sound becomes.
I found that using AudioSource.Play works better. But still, it worked fine in 2018.3.

 

I've filed bug reports for both issues. Someone emailed me back that they managed to reproduce the audiosource bug. But nothing about the framerate issue caused by the secondary monitor, although it's reproducible on any computer.
I'll wait, but I'm still not able to use the 2019.1 update until this is fixed. I'm looking forward using the new tilemaps tools you corrected.

 

Hi Chuan Xin,

I'm testing 2019.3 beta and I've got a couple of issues with the tilemap feature.
I actually wanted to record a video to show you a bug where the cursor freezes at the end of a stroke, but I found another one where the tile is never displayed on screen, but still exists (can be selected).

Case 1181256

 

The bug about tile not displaying isn't a bug. I forgot to set the pixel per unit of the image to 1, so it looked tool small to be seen. Sorry for that.

About the actual bug I was talking about before, I could reproduce it.
As you can see, the more I paint tiles, the longer there is to wait after each stroke.

Case 1181342

I work on 2018.3 and I have huge tilemaps and everything is fine. This actually is how I found out about this, I just opened up my project in 2019.3 and started to paint, and there were massive lags. Which was not the case in 2018.3.

I remember testing the same project in 2019.1 and the painting was great. No lag, no graphic bugs.

Thanks again Chuan

 

The thing is, it works fine in 2018.3. It just doesn't refresh properly (this is what this thread was initially about). Auto-save is a very useful feature and I use it all the time.

 

In 2019.3, I turned auto-save off and it does remove the little loading time at the end of the stroke.

We also tested to turn off auto-save in our 2018.3 project and it actually removed the problem we initially had (the ghost tiles spawned at the end of strokes). But we never experienced any slow down while working on tilemaps (even huge ones) in 2018.3.

I tested with the same project and the same tilemap with 2018.3 and 2019.3 and with auto-save turned on:
2018.3 is fine and 2019.3 lags at the end of a stroke (as in the video from my earlier port).

Thanks Chuan.

 

Hi Chuan,

Does my last post ring any bells ? Auto-save seems faulty from the begining.

 

Hi Chuan,

Thank you for taking the time. I appreciate it !
Here's a video comparing 2018.3 and 2019.3 in the same project on the same tilemap.
I hope it will help.

To answer your question, no, I don't see anything next to the AutoSave checkbox after each stroke, neither in 2018.3 nor in 2019.3.

EDIT: Don't forget to turn on the caption, I comment along what's going on.

 

Thanks a lot Chuan

 

I just checked and found out that all the editing tools of the tile palette have the same laggy behavior.

If I move a selection of tiles.
If I paint.
If I paint a filled box.
If I erase.
If I fill with the bucket.

All of these actions lag.

 

In all the tests I ran, I actually always edited the prefab directly from the project window. There were no prefab in the main scene. So to answer your question, no, there were no changes in the prefab before editing.

Here are the profiler screenshots. I hope it shows everything you need. Ask me back if it doesn't.


Here's the profiler data file in case you'd need it.
https://srv-file7.gofile.io/download/HBK54p/profiler_data.data

Cheers !

 

@ChuanXin here it is.
Out of curiosity, how could I send a file to a case after having send the report ?

 

Hi Chuan,

I was looking for the case adressed here (1181342) in the issue tracker page to check its status, and couldn't find it.
Could you tell me how to access it please ?

Regards,