- User Since
- Oct 26 2005, 7:41 AM (629 w, 6 d)
- Updating D2889: Grease Pencil Branch (greasepencil-object) #
Changes since last patch:
- Refactored the code as per https://developer.blender.org/D2889#68153
- GP Objects store their data in ob->data instead of ob->gpd
- Refactored modifier code for GP modifiers by adding 3 new callbacks to ModifierTypeInfo (i.e. deformStrokes, generateStrokes, and bakeModifierGP).
- Use depsgraph-based relations/tagging in places of the bad BKE_gpencil_batch_cache_alldirty() calls Most remaining calls to this don't do anything by default (they only run when debug_value = 66), and can eventually be removed.
Mon, Nov 20
In the User Prefs -> System tab, try changing the "Selection" field to "OpenGL Occlusion Queries" instead.
Sun, Nov 19
Fixed in rBa819ef65c07.
Confirmed and fixed now.
@Bastien Montagne (mont29) Unless you want to keep this report open to deal with any FBX export issues for camera stuff, I suggest closing this report now?
Following the instructions provided, I couldn't reproduce any problems here.
Fri, Nov 17
Interesting... we're certainly not the worst here, but there's also cleary some room for improvement too :)
Not a bug.
Thu, Nov 16
Wed, Nov 15
Not a bug.
Tue, Nov 14
Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
@Sergey Sharybin (sergey) Whatever you do here, I just hope we get the gp branch merged before you do it :P
@Brecht Van Lommel (brecht) makes a good point here about involving the depsgraph more here. With the batch_cache_dirty() stuff that a lot of datablocks now have to do to get selections redrawn in the 3D view, it makes sense to consider just having all that type of tagging being done via the depsgraph instead of having everything doing this manually. Furthermore, IMO it makes sense to give the depsgraph dedicated opcodes for this (e.g. a DEG_OPCODE_GEOMETRY_BATCHCACHE_UPDATE for general full update, and/or DEG_OPCODE_GEOMETRY_SELECT_UPDATE) since we've currently got a bunch of different datatypes doing these updates in the geometry ubereval.
Thank you for your report. Unfortunately, it's highly likely that this bug is specific to your hardware/driver configuration.
Sat, Nov 11
Ok, to clarify, I'm going to make sure there is a way to bake camera focus (and basically, anything that isn't transforms on an object or bone).
Fri, Nov 10
Thu, Nov 9
While investigating this yesterday, I realised that there is a workaround. Instead of selecting all the points covering the range you want to sample, just select the first and last keyframes of that range (e.g. the first and last keyframe, leaving out anything in between).
Ah, I see. In that case, it's probably easier to fix the Sample Keyframes operator instead :P
Wed, Nov 8
Another option - What addon are you using to do the export? Perhaps a quicker fix in your case would be to patch it to handle the point-sample output from "Bake Curve" instead :)
As the other guys have mentioned, it sounds like what you probably want is the "Sample Keyframes" operator.