So, for the motivation, I decided to make a dimension property available in BGE because I was programatically creating a tiled map with hexagons and to place the hexagons well obviously I needed to get have the dimensions. It seemed rather weird not to be able to get such a basic property from BGE. The workaround at the time for me was to create the hexagon at the proper dimensions and then apply the scaling and use the scale in BGE instead.
@sybren I meant storing the dimensions during conversion, because blender does take into account the object space, instead of a bb.
Then for what could change that in runtime... scaling an object? or if it is a softbody or cases that don't even come up to mind easily. So I foresee an easily broken property, without further motivation I'd say not to add.
thumbs up for the patch and thumbs up for sybren's review.
best to move that in before getting in fix-only mode tomorrow at the meeting.
Thank you for the quick response. I tried all possibilities but it's always the crash
Well, let's test a bit more before giving up ;)
Just tested with latest build, I cannot reproduce it either. Probably ressolved already?
@hadrien, re your comment in rBcb023ce0fd1a0cd0, I tried a few things but wasn't able to reproduce. Are you sure it does happen using latest master (please test with buildbot)? If so, please make sure the UserPref window is active while you try to scroll (although I doubt this to be the issue - just want to be sure).
Made requested changes, included license block.
Please don't open a new task/bug to discuss about an already existing report. This is a serious and professional bug tracker with strict policies and we have to make sure the rules are followed to keep the tracker organized.
If you have concerns regarding the merge of the two reports, you can mention this on one of the reports (as you already did). A developer will investigate this further then and make the decision if the merged task should be reopened or not. Furthermore, only because one bug is reproducible independent of the hardware, and one not, it doesn't mean that they may not have the same root. So again, you can help us by providing as much information as you can, but everything else should be done by us developers. We may make mistakes, but we're trying our best to prevent them or at least undo them afterwards ;)
@brita_ storing the bounding box during conversion only works when the object doesn't deform. I'm also curious for the motivation.
What is the motivation for this? Why would this be useful?
You are returning the dimensions of the bounding box, which is axis aligned and may not correspond to the actual dimensions.
It could be better to store the object's dimensions from Blender during the DataConversion step and try to make sure it doesn't change.
the model is ~0.4 cubed, which is normal for a character, also this sample is taken from a big environment, in which the character should be in place to act.