sorry to hear, what exactly was the step that gave you the most headaches? there are usually 4 ways to do stuff in OSA: 1. OSA wizard (create the listview as if you'd create a normal scrollview, then build on top of it) 2. right-click on your scrollview in inspector and "Optimize with OSA" 3a. copy an entire demo scene that best suits your use-case and chop stuff out of it until it resembles a basic version of what you want -> then build on top of that to really get to the final result 3b. copy just parts of a demo (and follows the same as 3a) 4. create everything by yourself, the scrollview, the scrollbar, the listview script etc. all of these can be approached depending on your use case. there are manuals linked in the description -- main manual, demos-related manual and in some cases per-specific-demo manuals. there are also a few yt vids that explain the fundamental concepts, it's crucial to watch them. one is about osa wizard, the other one (though older) is a step by step how to create a listview in unity without OSA, then optimizing it with OSA I hope you can give it a try sometime soon, and reach me on discord if you need help with your specific case! -- Lucian

thank you! this means a lot, and it's the second time someone mentions that unity should've integrated i, hehe. OSA is indispensable in my own projects as well. cheers!

hey, sure. but it's a bit trickier as you have to have all the different prefabs as disabled children of the item and enable them conditionally. it's not like in the listview where you can literally replace the whole root item. I've found this to not be a performance issue. you do have some readings to do though, check the grid demo's manual and hopefully you've also checked the main manual (linked in the description above) to connect the dots

hey! the issue with being easy to use is that there is an huge variation space, and it's practically impossible to have a wizard builder that can incrementally help you build your specific variation. this was found after years of "on-field" experience. so through trial and error, the most practical solution for everyone was to create many demos that are as disjunct as possible so as to cover an acceptable portion of that variation space after that, I've found some devs prefer a barebones approach where they're given a minimal functioning OSA List/Grid/Table and they build on top of that, so I came up with OSA Wizard: https://www.youtube.com/watch?v=BnA32GV13ws in case you've approached both and neither feels right, here's my angle: you might be in a situation where visually a demo is so close to what you need, that you expect the additional code to integrate it into the project is also minimal, but we all know sometimes that correlation doesn't hold. obviously there's always room for improv, perhaps making that specific demo (I don't know which one exactly you're referring to) more modular so you can just plug and play. there was also a misconception in the past that people need that "Entry" object in the demo, I tried my best to clarify that that's not the case in the manuals (which I highly recommend going through: the main one, the demos overview one, then perhaps the one for your specific demo, if it exists) anyway, let me know if you have any specific, actionable suggestions 👍