Hello Omar,

Normally, when I click on the menu, it brings up the full list of all materials being used in the scene. In this case, it only went to the names beginning with D and ended there. All the rest werent accessable in that list.

My humble apologies. I failed to mention in the steps to reproduce this, that you would click on the 'Select by Material' button (down arrow symbol) in Materials section, right hand control panel, as shown in the photo. I have edited the first post of this task for 'recreation' of how to see this happen.

In T97390#1356042, @Omar Emara (OmarSquircleArt) wrote:

Can you attach some screenshots to what you are describing? Is it the case that you expect the normal of the plane to be flipped instead of facing the same direction as the original plane?

As it turns out, I cannot test 3.3. Something in the new Blender 3.3 Materials system will not allow some of the materials to export properly into Micrsoft Flight Simulator (MSFS). 3.2 Alpha (latest build) is exporting quite well, but 3.3 for some reason exports the materials in a flat color, no reflections.

A friend of mine found out what it was. I thought you might be interested. He and I both noticed that N key wasnt bringing up the Tools slideout vertical window on right side in this scene (recent file saves). N key worked otherwise with new files. He investigated the Console and found that Window view 1 was malfunctioning. Perhaps oddly the files became corrupt, or the series of builds 'might' have had a issue with the tools window and that may have blocked my exporter from working, causing a crash.
We found that an earlier version of exporter worked in Blender 3.1. There, in the file, my friend did an Amend of all Containers of the scene to a new file, and Voila, it exported fine in Blender 3.2 and 3.3. :) I can now test 3.3.

I found the crash logs! They were named from the scene with crash at the end. Thats why I couldnt find them.

I tried cross testing this on a new gaming laptop. Fresh installs of Blender 3.2 and 3.3. It to crashed. And the file, Blender version, and exporter worked fine on my main computer a week ago.
When testing with one of the older versions of SDK's, I got this window;

Hello Germano,

Photos of the project. She is a polygon monster. But I am sure others make far more massive scenes. But this gives you an idea of the size of the scene. The exterior has far less polygons. Average map size is 4K, 3 maps per texture average on some that have PBR.

It appears that if you 'paint' the Curve (not create it, but to paint from the curve object onto the part you have made that you are painting), Blender crashes also. This is in yesterdays Blender 3.2 March 31st Build.
I got mine to paint the Curve onto the object, but after 2 seconds, it did a CTD.

I just tested this in yesterdays Blender 3.2 build and it works fine. So it appears to only be in todays April 1st build.

Hello Germano,

Hello Omar,

I used the Minus key to delete the former material, clicked plus to add New Material, then setup a new PBR, added Albedo, and the blurry texture appeared on the part. Very odd. Never seen that before.

Roger that. Will do.

Hello Pratik,

Roger that. Many thanks Pratik.

The Normals shoudl be normal, pardon the pun, but reflections are all over.

As requested. I hope they show up ok. I couldnt remember the first part that had this issue, so I included several. The screenshot shows the newest issue that popped up via this report. A strip that goes around the wing, top and bottom. It appears to have 'shrapnel' where the faces look like a puzzle. This was happening last year on another Beta launch. I forget what it was linked to, but was eventually fixed. I forget what it ended up being related to was.

I could send a adjusted file with most of the parts deleted and only the parts having issues sent over. Would that help?

Hello Pratik,

So it must just be the model mesh. It must have something in it that is causing this.

My humble apologies. This appears to be an issue with an Addon; Machin3 tools. :S

Congrats on release of new 3.2 Alpha. Installed! Going to enjoy testing it and running it through its paces.

I am getting a lot of these popups now with other parts, so I am quitting use of JAN 27th and going back to Jan 25th for now.

This popped up a bit ago after applying some materials to a part and then going from Edit mode to Object mode. Just to test, I went back into Edit (Faces) mode and right back out to Object mode (using Tab key) and the same warning window popped up again.

Hello Evan,

I redownloaded the package, thinking it was a bad download. Exact same thing. I open the same file in Jan 25th build, its normal, as it was saved. Different in Build Jan 26th.

Hello Team,

I made a small mistake on the above report.

A slight correction on my email above. We will have 50 to 200 animations on scenes, they show up in the NLA Editor as they are animated, but in the conversion to glTF and then importing to Blender, the animations are all renamed to a generic animation, such as node235Action, etc. So looking for the animation name doesnt work. Finding it by object name is the route we need.

Hello Philip Oeser,

Works excellent. Issue repaired. A thousand thanks, Team Blender.

Downloading now.

Many thanks, @Aditiya Afrizal.

Normally the rotation has notches where the object lands on set increments of degrees of rotation when holding down Control key. Now it does not. Perhaps this was removed? I used it all the time when rotating new objects 90 degress, 180 degrees, etc.

Just tried AO map rendering on Oct 7th Build of Blender 3.0 and it works Marvelous.... :) Thank you Team Blender.

Hey guys,

This gives you an idea of the complexity of the model. Sometimes the only way I can find parts is to go into Wireframe mode, then use Isolate to work on them, but I was not working in Isolate tonight when these several crashes and errors occured. It was mostly in renaming parts and setting animations, and crashes occurred in 'selecting parts' in the scene, in Wireframe mode.

My apologies, you might wish to have this part in there;