# PSA: 2025.1 Super bug thats fixed in 2025.1.1 **URL:** \ **Category:** Between Renders\ **Created:** [August 30, 2024, 1:14pm UTC](https://forum.logik.tv/t/psa-2025-1-super-bug-thats-fixed-in-2025-1-1/11326 "2024-08-30T13:14:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\ **Post date:** [August 30, 2024, 1:14pm UTC](https://forum.logik.tv/t/psa-2025-1-super-bug-thats-fixed-in-2025-1-1/11326/1 "2024-08-30T13:14:59Z")
We had a massive issue here with 2025.1 where if you copy segements between timelines of different resolution the resolution would totally error out and render broken frames on output super bad. I would really urge you to upgrade to the 2025.1.1 release, this bug is not part of the changelog, we where about to start a support case until we tried the latest version and we can replicate the issue everytime on 2025.1 but we cant get the bug to appear on 2025.1.1 we spent quiet a bit of time hunting this down, as it was really putting sweat on everyone as rendering out was a gamble … glad its fixed… @hildebrandtbernd was the one that found it, and replicated it so adding him for visibillity ---
**Author:** ![krystenr](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/krystenr/32/7272_2.png) [@krystenr](https://forum.logik.tv/u/krystenr)\ **Post date:** [August 30, 2024, 9:55pm UTC](https://forum.logik.tv/t/psa-2025-1-super-bug-thats-fixed-in-2025-1-1/11326/2 "2024-08-30T21:55:42Z")
This bug has been the bane of my existence, so I feel you! ---
**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\ **Post date:** [August 31, 2024, 8:53am UTC](https://forum.logik.tv/t/psa-2025-1-super-bug-thats-fixed-in-2025-1-1/11326/3 "2024-08-31T08:53:38Z")
sadly it does not fix the long standing importing of xmls - broken actions everywhere bug 😕 I cna get 1 click conforms of hundrets of xmls if this bug wasnt a thing… i have nailed down the proxy and premiere workflow to make this happen its all solid. just the flame bug requiring us to redo all scales/transforms for every timeline … ---
**Author:** ![fredwarren](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fredwarren/32/158_2.png) [@fredwarren](https://forum.logik.tv/u/fredwarren)\ **Post date:** [September 3, 2024, 12:07pm UTC](https://forum.logik.tv/t/psa-2025-1-super-bug-thats-fixed-in-2025-1-1/11326/4 "2024-09-03T12:07:03Z")
I don’t want to be a downer, but I wouldn’t be 100% sure the defect you are describing is fixed. From experience, there might be one small variable that was not the same between 2025.1 and 2025.1.1 in your test and that small difference didn’t trigger the defect. That being said, it is also possible the problem was fixed “by accident” when we fixed something else, but nothing in the fixed defects list of 2025.1.1 makes us think so. ---
**Author:** ![finnjaeger](https://avatars.discourse-cdn.com/v4/letter/f/e99b99/32.png) [@finnjaeger](https://forum.logik.tv/u/finnjaeger)\ **Post date:** [September 3, 2024, 2:49pm UTC](https://forum.logik.tv/t/psa-2025-1-super-bug-thats-fixed-in-2025-1-1/11326/5 "2024-09-03T14:49:20Z")
yes the main defect isnt fixed, but one of the things we had where it would just die instately when copy pasting segments across, that we can repeately say got fixed even if it was on accident 😃 We did a whole video showing the defect and how to reproduce it on multiple machines. we put some work into this to make sure its a reproduceable bug. Then we switched to 2025.1.1 and we cant reproduce that particular behaviour