With the help of skymen we managed to track the issue. It seems the engine generated the same value for different objects imageSpriteId. So looks like we just got unluck for the engine to roll a number that were the same in different branches. IIRC this has been fixed and shouldn't happen in recent c3 versions.

Thanks everyone!

Jase00

Some reasons why we stick with r225:

- We would need to adapt many plugins to work in r226+ version because of a change in how structure for plugin in JS works

- We work on a big project, so updating C3 version would ocasionally create bugs in the project that were hard to track

- It makes life of third party company we work with easier

We try to be very carefull when merging and when we have issues the console usually outputs a error that helps finding out what exactly is the issue, but this time we got this "Error: id already in use" wich sounds a bit generic.

For the c3 version, yeah, we still use r225. At this point we need to stick with it for multiple project related reasons.

Hello, first of all I wanted to start saying that this is not a bug.

I'm working on a project and at some point in time I had to use git and work in different branches.

Now that I tried merging both branches and open the project, I get this error:

[Project] Exception opening: Error: id already in use

at va.h2c (projectResources.js:1008:26)

at new g (projectResources.js:31:329)

at d.l (main.js:292:207)

at n.Mta (projectResources.js:193:3)

at n.hja (projectResources.js:202:448)

at async Promise.all (/r225/index 11)

at async Promise.all (/r225/index 0)

at async n.cpd (projectResources.js:134:402)

at async Promise.all (/r225/index 1264)

at async e.mbc (projectResources.js:139:120)

I'm here hoping Ashley, another scirra staff or a experienced user could point out what could be causing this type of error, so I can try finding the problem on the project.

Thanks in advance!

Will do, thanks for the tip. I did had some freeze in the editor some moments after I posted here yesterday, but it was not like the other freezes I had before, this time the editor became responsive again after a while (maybe after waiting 1 minute).

I'll try doing more tests to be sure if this is really working as I believed and then update things in the report.

Ashley I opened a report for chromium team regarding this issue: bugs.chromium.org/p/chromium/issues/detail

I'm not sure how to tag Ashley in the report, I can do it if someone tell me how.

Thanks Ashley, I was relutanct about posting it in the issues tracker as I didn't know if this would be considered a bug, so I felt like discussing this in the forum first.

I will open an issue there.

Pretty much the tittle. I'm working on a big project (as in it have lot's of files) in C3 and today after we got the release 221 it took me about 3~4 minutes to be able to save the project using the folder project option.

In some of the tries I even got an error (wich I used go get before anyway, seemingly at random) that says:

"Unable to save project. Try checking you have permission to save in the chosen location. Alternatively, try saving a different way."

As I said, I used to get this same error before this releasy anyway, but now getting it is even more frustrating since I lose a considerable amount of time for each time I try to save the project.

It's also worh noticing that I'm only editing a few layouts and sheets before trying to save, but even in this situation it takes a lot of time for the save process to finish.

Working with folder project is a very important feature for projects that uses version control softwares, but using this this option has been very frustrating the last few releases. Is there something Scirra could do about this situation?

Did we lose the ability to hide the window frame with fullscreen mode on nwjs apps?

I'm trying to request fullscreen with both the brownser and nwjs plugin at start of the layout but I can't get to "true" fullscreen, the window frame is always there.

I started a thread here but I got no answer: construct.net/en/forum/construct-3/general-discussion-7/lose-ability-hide-window-153049

I'm on windows 10, NWJs 0.46.1 and C3 r197-2