peterigz
Forum Replies Created
-
Posts
-
Hi, so the new alpha version is a complete rewrite of the editor and is free and available now, you can just download it from the alpha page here: https://www.rigzsoft.co.uk/timelinefx-alpha-version/ there’s no restrictions on it’s use and at this point it’s got a lot more features then the old version and lots more coming.
The old version is more stable, however I don’t really support it now and it no longer runs on newer Mac OS versions as the language I originally wrote it in stopped being supported. I just left it available to buy to help support development of the new version. If you buy the old version then you’ll receive a license key to unlock it but it’s separate to the new version which is free.
I’d recommend trying the alpha version first and see if it does what you need.
Ok great, thanks for the help testing, it’s useful to delve more in to the rendering and make things more robust, different setups, driver versions etc., can be fiddly to say the least!
I guess I forgot to compile without the console window but it doesn’t really mean much you can safely ignore those errors it just means it will create extra pools of memory as some of them ran out.
So I think I managed to fix the issue that was happening on AMD cards so no longer need to write direct to the GPU which I think is the issue with your drivers, let’s see how this one goes! https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip
Yes it could well be, I did notice references to dell machines when I googled it. Thanks again for the logs.
I’m fairly certain that it’s to do with it “Creating local buffers for sprite/mesh other layers” which is something I started doing to fix a separate issue on AMD cards. The strange thing is that it’s trying to allocate that memory from the heap that has ~224mb but it’s only trying to allocate 4mb. My nvidia 1660 has almost the same logs but it works fine, it makes me feel like it’s a driver bug. However what I think I’ll do is just disable that on nvidia cards and hopefully that should do it.
Another version here: https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip
This should provide more hints in the logs and also a potential fix, but we’ll see. It would also be interesting if you could update your drivers to the latest version as it may well be a driver bug as well. I don’t recognise your driver version, they seem to be in a different format on the nvidia site when I try and search here: https://www.nvidia.com/Download/Find.aspx?lang=en-us where the version numbers are in the format 551.76. It would have been interesting to install your driver version to see if I could recreate the bug here. Thanks!
I uploaded a new version, thanks for helping to test, appreciate it! https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip
I added in a few more logs and changed how it picks the device. I thought that maybe if you have an integrated gpu on the motherboard that maybe it was picking that over the discrete GPU ie. the 3070. So this will prioritise the discrete GPU instead. But at least we’ll see what’s being picked and also more memory logging.
oh interesting, that is definitely not what I would have expected š
Ok thanks I can start pondering what might cause that, obviously your gpu has plenty of memory.
I have uploaded a new version with a potential fix but it’s kind of a guess. Either way, when you run this version it should save a zest_log.txt in the same folder so if it crashes then copy and paste that log here and I can get some more clues. Thanks!
Download: https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip
Thanks, I have an inkling as to what it could be, but either way will have more logging in the next version.
Thanks for the report, are you extracting zip first before running the Exe? And is the location writable? You could try running as administrator maybe.
Do you know what driver version you have? Unlikely to be the issue but you ever know. Oh and did previous versions work or is this the first version you tried?
In the next alpha Iāll have more logging for crashes like this to help track things down. I can test locally on amd and intel cpus with amd 6600, nvidia 1660 and a very cheap nvidia 710 gpus so in theory your system should be fine.
Ok, you can try again, download from the same link here.
I was able to recreate the error, I just wasn’t including all the appropriate files to load the drivers required for the renderer and didn’t notice here because of course I have all the SDKs installed so it was still able to find them.
I used my old macbook and completely removed the SDK from there to recreate issue. Now it’s working fine on there with the new version so fingers crossed it works for you now.
I think I’ve found what the issue probably is, not entirely sure why it works ok to start with on my macs, but hopefully can upload a new version with extra logging as well soon.
Ok thanks for the report, will see if I can figure out what’s going on, what Mac do you have? What I’ll probably do is try and get all the validation layer debugging to output to a text file and ask you to run that and then send me it to get more precise details.
It’s probably something stupid I’ve overlooked as I’m still not very familiar with the Mac build and release system, thanks for the help debugging though!
