Hum, yeah there is some data wrangling when opening files but never noticed this isn’t triggered also on appending, maybe that’s a bug ?
Anyway, @RickyBlender , with blender you can always open old files and get something, obviously when the internal render isn’t there anymore when opening old files you loose part of shader definition.
But everything else might be there…
But I think the issue is say, to open a 4.0 file in 3.4/3.5, this isn’t going to work.
But it’s very likely that you can open a 3.4 file in 4.0 and probably even very old 2.49 style .blend in 4.0 and get a result.
In 4.0, if appending from an older version doesn’t work, that is most likely a bug, and can be reported. That’s backward compatibility, and it meant to work almost completely for Blender in general. It’s forward compatibility is different, where the intermediate step of saving with 3.6 is necessary to get meshes from 4.0 into older versions.
Ok I have found out what is going on, I can select single objects and append them without problems.
But in the append dialog, If I select all the objects with the A key and click append I get a popup error message with the file path and “nothing indicated”.
If I first select one object from the list (making sure that the objects name shows in the “file name” box at the bottom) and then select all the other objects with the A key, I can append all objects with no error.
So it is just a case of making sure at least one object’s name shows up in the “file name” box.