Is it time to raise the minimum version requirements?

[tngreene]

Blender 2.80 was released in 2019-07-29, Blender 2.90 was released August 31st, 2020

Daring users who have tried Blender 2.90+ have found that something isn't working for them and it won't export,

• [ ] What is the issue in 2.90?
• [ ] Ask the x-plane.org forum what they're using now
• [ ] Are there any breaking differences between 2.80, 2.83, and 2.90?
• [ ] Could we jump straight to 2.91?

[arb65912]

I would just stay with 2.83 until 2.91 until 2.93 becomes LTS

https://www.blender.org/download/lts/

[DWmFrancis]

Ted -

The first issue I saw was that nothing happened when I clicked on the X-Plane dropdown - except that the triangle rotated 90 degrees clockwise. Of course, that prevented me from modifying any of the settings.

I’ve fallen back to earlier versions of X-Plane2Blender and Blender in the mean time.

~ df

On Jan 19, 2021, at 2:07 PM, arb65912 [email protected] wrote:

I would just stay with 2.83 until 2.91 until 2.93 becomes LTS

https://www.blender.org/download/lts/ https://www.blender.org/download/lts/ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/X-Plane/XPlane2Blender/issues/633#issuecomment-763141888, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYAPEUUUCMW3O5EYU5KBZLS2XYCHANCNFSM4WJOSK3A.

[tngreene]

@DWmFrancis I've tried my copy of Blender 2.90 and was able to export a basic cube just fine. Do you have a file that won't export or won't work properly?

I'll try 2.91 as well

[arb65912]

@tngreene did you read my post above about LTS?

I was using 2.91 and it lacked certain features, export was OK but Blender itself not.

[DWmFrancis]

Ted -

I haven’t tried the latest version since downgrading last week, but will go back and try again.

-df

http://thinkingofdesign.blogspot.com

On Jan 26, 2021, at 5:52 PM, arb65912 [email protected] wrote:

@tngreene did you read my post above about LTS?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[tngreene]

@arb65912 I did. I agree, but, other people asking for this don't want to wait that long. So I can at the very least give it a shot.

[arb65912]

Understand @tngreene I just hope that exporter will still work on 2.83 version

[tngreene]

Have no fear, that won't change without very very very good reasons.

[DWmFrancis]

Ted -

I still consider myself a novice Blender user, so there is always a chance that I haven’t set up the preferences in xplane2blender properly.

As I said previously, I was able to create a new a 1024 x 2048 surface and apply a texture image to it in Blender and export it using the previous version of xplane2blender.

That being said, with the rolling changes to Blender and xplane2blender I’m not sure I’ve set all the parameters correctly.

Is there a description of the current workflow and a checklist I could refer to?

Sometimes I feel like using Blender is like being asked to drive a nail and being let loose in Home Depot to find an appropriate tool, never having seen a hammer before.

-df

On Jan 27, 2021, at 6:53 AM, tngreene [email protected] wrote:

Have no fear, that won't change without very very very good reasons.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[tngreene]

Notes from the investigation today:

• Some have reported an issue with the Object Properties menu in 2.92
• I've found that going from a 2.80 (saving the axis_detent_case_01 in 2.83 then opening in 2.92) sets the Dataref Values to 0 for all frames.

I think this is a Blender bug which is a big problem.

• 2.92 made their interface kinda thin and weird
• 2.90.1 ran the unit test fine except for one issue with backing up and restoring the lights.txt file in test_light_repeatable_cases_parse in TestLightsParser which is not a correctness bug.
• I don't know if the 2.90.1 UI is crashing for anyone

So, a mix of good and bad.

[tngreene]

Okay, this is one of the most bizarre things I've ever seen. In test_creation_helpers, set_animation_data

This dataref_prop.value = kf_info.dataref_value, or wrapping it in a call to float or float(str(kf_info.dataref_value)) or first assigning the value to another variable and then doing that, anything involving that variable, makes it not change. Nor does returning it from a function or using copy.copy. Nor making a class.

It seems to me that in this case, XPlaneDataref.value is cursed in some way.

            dataref_prop.value = float(decimal.Decimal(kf_info.dataref_value) * 34) # doesn't change a thing, value is 0 for all frames
            dataref_prop.value = 123412341234 # value is this random int for all frames

How do you explain this? It appears that unless the number is hard coded, the setter runs extra times. I have no idea how this could possibly work, except maybe some kind of bug in the C code?

To try:

• Run this stuff in Blender itself

I don't know. Maybe a clear head will show I was missing the giant rainbow sparkled cow sitting on my senses.

hardcoded ints, floats, returning random numbers from random all make changes to the keyframe values.

[tngreene]

It just has to be a problem with Blender 2.92. It works in every other version.