What is the .new file extension and how do I stop it?

[Foggy]

For the last couple of days I've been doing a lot of random stuff in LMMS with samples and switching between projects, and something curious has been happening to my project files: instead of saving in the .mmpz file format ("example.mmpz"), they suddenly become .mmpz.new files ("example.mmpz.new"), which I can't open from the sidebar launcher- I keep having to go into my file manager and deleting the ".new" bit in order to open the files up and continue working on them.

I'm using version 1.1.3 (apparently the 32 bit version, which is odd because I'm pretty sure I used the 64 bit installer). I've been using LMMS on this system for several months now and I haven't really changed the way I operate it, but this .new problem started yesterday and happened three more times in the last hour. Any idea what might be going on here?

[musikbear]

That must be something you did in windows. I guess it is a setting in files and folders, that will prevent windows from overwriting, and instead makes a '.new' file.
Is that the case. Examine your folder, and make some experiments.
afaik, there is no options to add a permanent extension in lmms at all. It must be windows

[zonkmachine]

When we save project files they start their life with the .new extension which is later removed. This means that LMMS fails to complete the last part of the file write process. It doesn't sound like a permission thing because then it would probably not have written the .new file in the first place.

@Foggy Try and change the setting for the "Create backup file when saving a project" option in the Setup window.
If that doesn't do anything for you, try and rename the .lmmsrc.xml file to .lmmsrc.xmlBACKUP and then start LMMS again to get a fresh setup and see if the problem remains. Then you'll know the problem is in LMMS and not your OS... what OS do you run?

If you start LMMS from a termial/comand line, do you get any messages when you save a project?

[Foggy]

Sorry it took me so long to reply to this.

It happened one more time, don't know why, and in the weeks following I haven't been able to get it to happen again. I haven't really been doing anything different (aside from checking my project list obsessively for .new files), so I still don't really know what the cause was. I've bookmarked this thread in case it starts happening again so I can try out some of your suggestions... until then I'm willing to chalk it up to Windows 10 just being an unstable problem child.