Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
error report: sometimes when I open the .ccb file I see copies of some objects in the scene and I need to delete the copies. |
||||
|
This happens to me too if I use the "clone" node or the "delete" node in the "Before first draw" or "on restart". I think it's only meant to happen at runtime of the test.exe but I noticed cloned nodes and deleted nodes appear in the scene graph editor when loading a project. Pretty sure it shouldn't happen - it's a complete deal-breaker if you save by accident and don't have a backup. I lost quite a few projects to this (and other niggly bugs which are hard to pin-point/explain). The only way I found to fix this particular one is to not use clone (or delete) with the "before first draw" or "also on restart". In fact, quite a few inconsistencies can be solved in the same manner...... Instead, you can add a variable to the game such as "Game Started"=1 Then while the game is running, do something like: If "Game Started"=1, clone node. https://www.ambiera.com/forum.ph... If you're not using the "before first draw" or "also on reload", then not sure how to fix it - a lot of errors can be down to individual work flow and are sometimes hard to explain or reproduce or are not actually bugs at all. I had similar issues with "do something later", "animate scale" and "fade screen" plugins creating all sorts of problems with variables and nodes and non-stop repeating of events if I used them in conjunction with the "before first draw" or "also on reload". If this isn't the fix for you, hopefully someone else can help with it if you explain in a little more detail. |
||||
|
yes, it's tedious to delete the copied objects every time I open the .ccb file. Thanks for your explanations. I am deleting the copied objects. I save the ccb file. When I enter later, I have to delete the copied objects again. |
||||
|
I hope this bug and similar ones will be fixed in future versions. |
||||
|
Me too, there's a variable that keeps disappearing for me when I open my project's ccb file - I have to keep typing it in. It just happened now, and almost every day I can remember. Each time I open the project in the morning, the player gets stuck on the floor, I notice that the .colsmalldistance = 0.001 variable is gone again. *Actually, a thought just came to me right now - it could be something to do with windows system hybernate - it makes an image of the entire RAM, then reloads it on boot-time. I think I'll turn hybernate off and shut-down properly, in case it's not restoring the session perfectly. Coppercube is almost always the last program running in my session before hibernating and the bug occurs during my first session, almost as if the ccb file is a hybrid of various states - some older bits missing, some newer bits saved and restored. Are you using the RAM hybernate feature? Maybe windows doesn't make a perfect image of the RAM, maybe it's only updating the snapshot with certain changes, rather than the entire dump, maybe coppercube accesses parts of the system that are ignored during hybernate? Hopefully this will explain a few things for me and possibly fix our issues. I'll test it for a few weeks and see if it helps. I had an unrelated issue with a Linux distro once (can't remember which one) and didn't realise that the entire operating system was booting RAM, rather than streaming from SSD - so none of my system changes were being saved, it was a clean OS every time it booted so everything ran super smooth and quickly with no problems - other than not being able to save/restore the session. Could be a similar deal with windows. |
||||
|
I had a lot of problems with windows hibernate (sleep) over the last 2 days actually. My pc failed to restart after waiting a long time and seemed to corrupt the open visual studio code I had open (CC source) as had to shut down the pc and restart. I'm not going to use hibernate again - perhaps its my power supply playing up but it caused a lot of problems.. |
||||
|
Nice one Robbo - Agreed, I'm not using hibernate any more and the problems appear to have gone. It does seem to take quite a while to shutdown without it, but it's a small price to pay for a more stable machine. |
||||
|
I'm happy to report that I fixed my pc - was indeed the power supply playing up. I don't recommend hibernating for long periods - definitely not overnight... I took it apart and found one the the 2 large capacitors had failed pretty much completely and so wouldn't start with just one. Tell tale signs of faulty capacitors are a bulging top or signs of leaking capacitor fluid at the top or bottom. This one had both and seemed clear it was faulty. Luckily I had a capacitance tester to confirm true. Normally this unit has 820 uF but the faulty one had only 50 uF or so...when an old one would still be ok at around 700+ uF. I also had some spare capacitors around from years of fixing pc power supplies....is a very common problem. I put in a spare one with 700 uF and soldered it in. Switch on and badda boom - all good again.... In hindsight, maybe adding in too many older hard drives didn't help as only 4 months ago put in another SATA 2 2TB drive for total backup of all files. I had decided to unclip the power socket to this until one I need it again then just reconnect and restart as don't need it for day to day running...only for backup. Cheers! |
||||
|
|
){kind=link}