Arguing a point does not say anything about your views on other things. I am saying in this case, it does not make sense to all of a sudden rapidly change things that, at the end of the day, are not actually hindering use of the asset. And FYI I’m well aware of the state of the marketplace, how content creators feel about it, and how I feel about it (imagine that). Again - commenting on a single issue does not then mean I am happy about all the other things. Sometimes, believe it or not, people can address a specific thing as that specific thing But go for it - shout from the rooftops all you like. I’m out of this one.
Just because I’m saying the suggested structure isn’t a proper one it doesn’t mean I want to shout. :rolleyes:
There’s no way to fix such an issue slowly over time. It’s either this or that structure.
Here’s a list of people who I could get their opinions on the current structure:
Chuckles @ the concern about the directory hierarchy, this is subjective as all get out. One man’s trash is another man’s treasure. Personally I would like to see the assets for a static mesh, and it’s associated material interface and ALL assests that comprise the material, and all decals that are to go on the static mesh, to be in the same folder, so that it’s one stop shopping. Instead of, oh we need to go to this folder, and then that folder, and gosh, how about we need to go to a texture folder, and whoooooopie dingo, now we need to go to another folder.
Chasing down assets, is the most infuriating (and no I don’t care if there is a little magnifying glass icon, I don’t want to have change my train of thought, I just want the stuff there in one directory) thing. Ok, it’s not as bad as how structures are dealt with in Blueprints, but it’s just right below it. Oh wait the symbol table in blueprints sucks too. Ok, so it’s below both of those blueprint things. Nope, forgot one thing, that of the blueprint editor, kindly breaking the wires between the nodes, that always makes my day. I mean what else should a compiler do, when it finds errors with structures? Well of course, break the wires for the nodes dealing with that structure!!! Why didn’t I think of that?
Never let it be said, that a compiler cannot undo in milliseconds, what it will take the programmer 2 hours to put back together…
As a user, I wish all Packages from the Marketplace were off of a top level Packages Folder. (Could be off Content)
Each package would be in a subdirectory of the Packages top-level folder.
They could even have version numbers in the name!
When you have alot of packages, the current folder structure is just awful.
It is impossible to differentiate between your own stuff and package stuff.
Just like Plugins are in the project directory.
Please don’t call it a waste of time when people are asking for improvements that helps them save time.
A lot more people share the same thoughts if we actually ask for their input publicly.
Either way, see you in other threads.