You can test either 3.3 or 3.4 version. You should always test with development versions. Older releases other than LTS will not receive bugfixes.

In D14412#424815, @Sergey Sharybin (sergey) wrote:

For overshooting, I am not exactly sure what was requested, but gain is now limited, so I assume this is resolved.

See how the "Auto Clamped" interponation works for F-Curves.

Basically, curve should not go above the control point. This is not the case between the 2 left-most CVs on the picture.

Most problematic for me is amount of data provided. Limiting dataset to least necessary items simplifies tessting a lot at least for us developers.

Thanks for clarification, I will check if I can reproduce crash when marking object as asset, but not sure how should I do it.

Just heads up, until @Marcos Perez (pistolario) returns from vacation, I will take on this patch

Rebase

Thanks for checking.
I wasn't able to reproduce either, so assume the issue was resolved.

I am a bit confused still too, so I don't think I am in position to give advice. Namely I am not sure what do you refer to as "markers".

Have you tried to debug the return value of os.path.islink()? Does it actually return True on your machine?

Did not check this. Do you suggest that files are deleted by Python itself or Blender script? If it's done by script, can you identify where file is deleted exactly?

Glad I was able to help.

Checked with Blender 3.4.0 and Intel(R) HD Graphics 500, 4.5.0 - Build 27.20.100.8681.
Everything seems to work well.

I think I understand now.

In T98946#1400172, @Pawal (BelCGFree) wrote:

I checked the corrected archive, it loaded normally, the old archive crashed.

Thanks for data. Which one is old one?
I see this file here too:

Can you upload .crash.txt file with version 3.4.0? I suspect there may be different issue since I got no crash this time...

This report does not contain all the requested information, which is required for us to investigate the issue.

Can you provide .blend file with simple setup for blending so we can check?

Looking at code, this is expected behavior. There is also comment Local-view can become invalid during undo/redo steps, so we exit it when no could be found.. Considering that tweaking operator property produces undo/redo steps, this code is triggered, but it is useful for "real" undo/redo.

Thread hangs on:

I am able to reproduce 2 undo steps, but path select seems to work well here.

This report does not contain all the requested information, which is required for us to investigate the issue.

Can confirm crash in version 3.2.1, but not in 3.3 and higher, so this seems to be resolved already. You can download latest builds from https://builder.blender.org/download/daily/

Gif file format is not supported in Blender. From what I can see nor for reading or writing. Since this is not implemented, it's not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

Also please check if this happens with Blender version 3.3 - it should handle movie seeking better than previous versions assuming that is the core of the issue.

Can you provide mp4 file and .blend file if possible?

Reminds me of T95916, even though there 3.0.0 is listed as broken version.

While I think your point is valid, the node input works exactly as intended and therefore this is not a bug. Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Your laptop uses Intel GPU, which is not possible to use with Cycles. You can always use CPU rendering, no need to set up anything for that.

Please check if this issue happens with latest alpha build from https://builder.blender.org/download/daily/

This seems to be a bug, but node tree causing it is quite complex. Is it possible to simplify it?

@Andrew Smith (andresmi) can you provide sample .blend file? Without file we can't reproduce the issue.

@Bill P (bpszenny) can you check if this happens when you download latest alpha build from https://builder.blender.org/download/daily/?

@Martin (Hahua) I was unable to reproduce this issue.

Thanks for crash file. I was able to reproduce this issue with version 3.2.1, but 3.3 or 3.4 does not crash, so it has been already resolved, so I will close this report.

Now checking bit more, faces are not only split, but also duplicated. Can you provide cleaned up file for testing?

Thanks for report.

Not sure if this would be a bug - face orientation is flipped on parts of mesh:

Please update GPU driver and check if issues persist. Version 27.20.100.8984 is quite old from what I can see.

Please upload file C:\Users\Mohamed\AppData\Local\Temp\Destruction.crash.txt

Don't have means to test now, and I don't see any relevant commit that could have caused issue like this. Tried random online fbx viewer and that seems to work fine as far as speed goes.

This report does not contain all the requested information, which is required for us to investigate the issue.

CC @Joerg Mueller (nexyon)

Unfortunately, such video formats are not supported. Blender assumes static image size. Will close since this is not a bug.

I was able to reproduce now, but I had to do a few attempts. So no need for recording.

Current Frame is purely informative value which is calculated from strip and current frame position. This has nothing to do with content start - if you move strip handle it still counts from 0.

It's not a bug, because in VSE strips are visualized by area, in timeline editor you mostly look at points (keyframes). This means that strip starting on frame 250 must end at least on frame 251. Or in other words, try to set range so that 1 frame is rendered (range from 1 to 1) - this looks correct in VSE, but not in timeline editor. With bigger frame ranges this looks off.

I was not able to reproduce - is this reproducible every time for you?

And can you check if this happens when you disable it?

Just a note, looking at exported keyboard, I am not sure if my steps are same issue as reported originally - in my case any event is used in keymap and in keymap press event is used.

@Yelyzaveta (bigbosschantp) do you use any anti-malware software? Can you check if this happens when you disable it?

On a crash, a file named blender.crash.txt should be written in /tmp directory. Please upload this file.
I think, we don't handle bugs in experimental branches here. But I think @Omar Emara (OmarSquircleArt) should tell if and where he wants to handle existing bugs.

Unfortunately when I render image, I see no hair. If I add new cube and particle system, it works, but can't reproduce the issue. @Marvin Wärzner (MarvinW) can you double check hair rendering works with provided file?

In 3.3 you can resize strip by moving handle, but that is by accident actually.

unfortunately my asan build terminates before I can check anything, so will have to manually configure this for specific area.

I can not reproduce, sounds like unsanitized/uninitialized memory access, will try to check with ASAN.

Don't think bisecting is necessary, will fix today.

Thank you all for info. Will close this report, since this is not bug in Blender.

Thanks for patch, gradients look fine, I have left mostly nitpicks, but texture size limitation needs to be resolved.

Using linear colorspace is probably not what you would want to do in this case, but changing transformation filter to "Nearest" or enabling Convert To Float in color properties should work without affecting color (within limitation of float/byte spaces).

@Didier TRESSE (MagicDid) Thanks for detailed analysis.

@Hongyu Fu (HF) Thanks for info, I can reproduce this issue when running as admin too. Don't think this could be considered as bug in Blender though. You can follow guide at https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command to resolve this issue.

Works well here, thanks for taking this over. I assume you write own commit message since description of patch is outdated.

In rB302b04a5a3fc0e767ac784424f78ce2edf5d2844#346756, @Constantine Vojik (costavojik) wrote:

Alright Thanks @Richard Antalik (ISS) for the fast reply!
I saw that variable frame rate support was added made me wonder if moving a sound strip not on a frame snapping (for example +2ms) is in the plans?
Thanks<3

In rB302b04a5a3fc0e767ac784424f78ce2edf5d2844#346754, @Constantine Vojik (costavojik) wrote:

Sound strips now use speed factor instead of pitch. This means, that
strips will change length to match usable length. In addition, it is
possible to group movie and sound strip and change speed of meta strip.

Does this mean changing the pitch the old way is not possible?

Don't think this is the same issue - when using transform operator, cache is invalidated, so this perhaps needs only tag depsgraph to do updates

Checking with 3.3, can't reproduce any regression here.

CC @Ivan Cappiello (icappiello), @Alexander Gavrilov (angavrilov)

Can't reproduce here (Windows build). Also can't find duplicate task.

I am not familiar with tablets, I assumed that only applying certain pressure would register as left click. Not sure if this would be considered as a bug, personally I wouldn't expect to be able to run operator after clicking with tool chosen.

Thanks for update. There are some similar reports already, but can't tell exactly just from description.

EDIT: and it's crashing again. My guess is Windows was still updating drivers in the background.

Thanks for info. I see that NAS does support samba sharing, which I assume you would then configure it as network drive like this:

In D15333#415010, @Sebastian Parborg (zeddb) wrote:

The intent of the original patch was to have ALL drag and drop actions insert at the mouse cursor position.
So if this reverses that, we have to have bigger discussion about this.