Anyone know what this is
Why doesn’t Unity gives something like what their errors mean
Seems like are making it harder with these errors not easier
The thing is it happens after it’s been made and played not like right away like an error on a script these are like hidden treasure found but are they really a treasure or a curse
1 Like
Maybe post the full error? Rather than just some rambling, cryptic message doesn’t give any meaningful details.
There u go
no type of reference
So what does it mean
Any clue
Hello
Do u know
It would be good if u know what it means
1 Like
Nice dirty screen. It’s 2023, it’s not hard to take a screenshot these days.
Well, is your own code causing this? A package (Asset store or otherwise)? Does it happen on a fresh project?
It should be pretty straight forward to eliminate the causes and figure out what’s throwing this error.
Ya we smoke a lot I live in Denver, co
Bla bla
Anyway I had the project pretty much done
With no errors the day before yesterday didn’t do anything different than the error pops up all of a sudden yesterday
And I don’t use Unity web site on my pc
So why start now
back and forth from unity to the web is a wait time so I avoid it
And we have more than just a pc to take a photo like most people
So how do I find the asset causing it
But ya could be an asset I have enter exit with the racing game starter kit with damage scripts
To the opponent ai with the asset simple turret, and homing Missle asset , and npc script from urban city by I think Alex mobile ragdoll to run them over
And FPS weapons from 3D Mason but is deprecated
Maybe to much
But thanks for asking with the errors I get there ain’t to many responses
3 Likes
I noticed getting the same error starting with 2022.2.15f in a scene that was finished already. Now when I return to the scene this error appears in the console without any reference to where it comes from. It seems to be an editor only thing, if I restart Unity it disappears and randomly appears again after reloading the scene a few times
4 Likes
Happens to me randomly. I did edit some prefabs, but no idea if related.
Definitely not easy to eliminate since there’s absolutely no other information about the error.
Using Unity 2022.2.18
Just text:
“Calling EndWrite before BeginWrite”
1 Like
Same happening here, after updating our project from 2021 to 2022.2 .
This “Calling EndWrite before BeginWrite” message is also appearing in Unity 2021.3.25. It did not appear in 2021.3.24 or earlier. There are no stacktraces or other indication about what the issue is. It seems to be more frequent when editing prefabs.
Bug report: CASE IN-41273
I noticed that inspector “Range” was not working. I changed values in the inspector using the range-slider thing but my changes were lost once I clicked away from the object.
[Range(0, 100)]
public float testValue;
I removed these from my code.
…and today I have not encountered this bug.
absolutely no idea if related or not.
I’ll report back if I start getting those errors again.
Another shoutout that after removing “[Range(0, 100)]” type of code from inspector, I have not experienced "Calling EndWrite before BeginWrite". This is Unity 2022.2.18f1.
So in case somebody happens to google their way here, this is one trick to try. No idea if it actually works for you.
1 Like
bumping this, as its quite annoying:
This happens after upgrading to 2022.3.0 LTS and just selecting different prefabs
1 Like
Hey guys, I have the same problem and I didn’t write a single line of code yet in the project. I couldn’t find the solution yet but it happens only if I choose one particular asset, which I purchased from a reputable seller on asset store and never had problems with the same asset before.
1 Like
I have not touched unity in years, but this could be related to compute buffers. This was a new gfx api a few yrs back and requires call order…we used to wait 3 frames or so to be save…instead of checking with asyncgpureadback….
1 Like
Unity just closed my case as they cannot repro this issue. If anyone here can file a bug or repro project to help out that would be appreciated. I have been referencing this thread and my bug report is Case IN-41273 if you want to reference it in your bug report.
3 Likes
Got the same issue… Seems to appear randomly until I restart the editor…
To build on this idea, the language is the same as is found in the Compute Buffers source:
I see it when running demo scenes from More Mountains’ Top-Down Engine, the Loft3D scene in Unity 2021.3.25f1.git.6876972 (2021.3/staging 68ef2c4f8861) on MacOS Editor.
Calling BeginWrite before EndWrite
Calling EndWrite before BeginWrite
Any update on this? It just randomly appears with no context. The editor will also crash some times when saving in Shader Graph or even when deleting objects. I get no crash logs either. Super frustrating.
No, my case was closed and I reopened it. Unity QA weren’t very interested until someone can submit a stack trace or something. I don’t have one, can’t reliably repro the issue, and I’m using VS Code so I don’t have a debugger I can easily attach at the moment. If you can trap the issue then please submit a bug report and reference my case number.