can someone please teach me how to fix it? this is Translator++ version 4.7.30
i turned on the file as usual. the last time i used it, it still work but now it suddenly happen.
Related
I started a new project and after closing and reopening it the next day, all progress was gone. It didn't crash and there weren't any abnormalities. I didn't touch any files in file explorer so it's not like I could've reverted the project or something. And yes I saved, I always save. Recycling bin is empty so it wasn't deleted. So I haven't much idea what the cause could've been, or what else to put really.
But is there any explanation for what could have caused this so next time in the future I can prepare for all my progress being erased out of the blue. And is there any way I can retrieve the files back somehow too?
Using version 2020.3.2f1
Have you tried looking through temp files? Because I had this problem too a while ago and was able to retrieve the data which was hidden in the files somewhere. I had a backup and it didn't help because it didn't save to the backup obviously. I don't know why Unity still has this problem and there's not a lot of help on the internet regarding it either
I am trying to upload my app however I keep having this error pop up. I'm not sure what caused it as I didn't really change anything but I can't seem to fix it. It looks like a file is missing. I've tried reinstalling Xcode but that did not resolve anything. Any help is appreciated.
Okay, I found a fix. It was actually really simple. I just deleted the file /Library/Caches/com.apple.amp.itmstransporter and the files and all of its components were regenerated correctly when uploading to App Store Connect.
I've been using the ESM module with VSCode and my Mocha unit tests for a long time now, a couple of years at least. Recently when I launch an individual test file in VSCode and set a breakpoint in the test file, it no longer breaks in the original file, but rather breaks in the "ESM compiled" file. I don't really know how ESM works enough to talk about it very well, but the file is compiled/transpiled/transformed in some way with all the imports converted to non-ESModule code. I'm able to step through, and it continues to step through other files as well, but each new file opened is this newly "ESM compiled" version instead of the original file, like it used to be. I only just noticed this recently. So I decided to install and older version of VSCode and see if it still happened, and it turns out it doesn't. With version 1.45.x it works as usual, but with anything newer, I get all these "ESM compiled" files opening up when I step through code.
Does anyone know why this is happening? Is there any new setting I can set in the newer VSCode versions that would cause this to not happen? It's really more of an annoyance than anything. I can still get my work done, but it's not as streamlined as it used to be. I will probably end up just downgrading permanently until I can find a way to make it not occur in the new version.
So, if anyone has experienced this, or knows of something new in VSCode that would cause this, I'd really appreciate some help. Thanks.
I dont know why but now (it worked fine yesterday) when building my scripts is says Build successful every time even whern there are mistakes. I tried deleting the files in : C:\Users\user\AppData\Roaming\Monodevelop and even reinstall unity.
Nothing worked.
I dont know if this is related but since installing monodevelop I didnt have autocomplete, I saw an answer which said to resync the project but I dont know how.
Anyone knows how to fix this?
Thank you!
I closed Eclipse because I had a feeling my PC was gonna crash (been acting funny today), and it said it saved my workspace and closed normally.
But when I went back in after reboot, my workspace wasn't loading - even after selecting the right one my projects wouldn't show and the layout was reverted to default....not such a big deal, just re-imported.
But... One of the source files I was working on seems to have been corrupted, replaced with one continuous line of squares, which is kind of a big deal :/
Any thoughts on what caused this? I know there's probably no chance of getting that file back, but if anyone has had a similar experience or knows what the jaysus happened that'd be cool! Ideally I'd like if this never happened again...
Problem was related to my SSD: Weird bug where after 5184 hours of use it would shutdown.
Firmware update fixes the problem.
More here: http://www.tomshardware.com/news/Crucial-m4-Firmware-BSOD,14544.html