Hi! "working on my own solution instead, which already works much better" I'd argue that if you rolled out your own solution in a few days and it's working better than Obi for your use case, a full-blown particle based fluid simulation like Obi wasn't what you needed to begin with. Let me know if I can process a refund for you in that case! :) There's relatively few cases where a full-blown fluid simulation is needed, as it's the nuclear option: very flexible, but *very* expensive. In many cases you can get away with heightmap/2D based simulation, simpler analytical stuff (eg. gerstner/tessendorf waves) or no simulation whatsoever (just a scrolling texture). "But if you want to use custom metallic materials with emission and long lasting large flows (like lava from a volcano) this isn't going to be a good solution" I'm not sure why using custom materials would be a pain point? While the asset does include its own fluid shader with many features (reflection/refraction/absorption/scattering/triplanar texture mapping, dual rest field advection, etc) you can use any custom material/shader with Obi: all it does is perform simulation and output a mesh to represent a fluid surface. See: https://obi.virtualmethodstudio.com/manual/7.1/fluidrendering.html The "long lasting flow" bit is strange as well: you can set the lifetime of emitted fluid particles to any value you'd like, even infinite. "I haven't needed to use a forums page for anything for so many years now" Unity's main support community (Unity Discussions) is a forum... "Any good asset developer needs a discord so they can provide quick support for their assets" Not sure what support speediness has to do with Discord, to be honest. You can get quick support regardless of the format. Personally I've received zero support on certain Discord servers in the past, I don't attribute that to Discord but to the people running the server. "it's so strange seeing a forum be the only form of support for something like this. It makes the community feel out of reach." Note you can also write an email directly to us, forums aren't the only way to get support. We used Discord for a while and even though we had few users in the server, information was scattered all around and the same questions were asked repeatedly which made us think users weren't able to find existing information. Forums seem to organize information far better imho. This is just personal preference of course, we fully understand and respect you may be more comfortable using Discord. "Many game developers have some kind of social disorder like Autism or OCD [...] the OCD makes a need for things to all be in one place." I'm sorry. We strive to have an in-depth, comprehensive and fully up to date manual(https://obi.virtualmethodstudio.com/manual/7.1/index.html) so that you can find information all in one place, available at any time without the need to scan multiple places searching for it, but seems we have failed you in this regard. I have (mild) OCD myself and having to sit trough multiple videos searching for the specific bit of information I'm interested in is something I personally find frustrating and extremely inefficient. We've also had similar feedback from users in the past, video is a good format for short tips but not as a main form of documentation. It's one of the reasons why documentation for all our assets is in written form: it's easy to search, it's easy to categorize, easy to keep up to date and easy to correct when needed. "[...] which means watching tutorials and learning by themselves is how they do things" I'm fully self taught so I deeply resonate with this. However it's possible to learn by yourself either by watching videos or reading documents, neither autism nor OCD should be obstacles in this case? "This is why this is so important. Your main demographic uses discord and YouTube." Numbers say quite the opposite. As I mentioned, we had a Discord server for quite a while and it was mostly empty (20-something users after a couple months, if I recall correctly), most support requests came in via email so we ended up closing the server. Our videos had very few visits compared to our online manual and they required a great deal more effort to maintain, so we shifted most of our attention towards the manual. The videos we do have linked in our webpage (https://obi.virtualmethodstudio.com/videos.html) are still useable since the differences in asset workflow over versions are very minor. I understand no solution fits everyone's taste, so we ended up using what seemed to work best in practice for the majority of our users. This said, we're more than eager to help with any issues you might encounter while using the asset. You just need to contact us (as far as I can tell, you haven't so far). In certain cases we've even recorded custom videos for some users, guiding them past specific hurdles. "You basically don't even exist on those platforms. I really want to like this asset, but it feels abandoned." Well if you look for lions in the north pole you won't find any, but that doesn't mean they don't exist. I'd say you're simply looking in the wrong place: our forums are quite active (more than 4000 users and 16000 posts), and we receive and answer emails daily. The asset's description clearly states support is offered via forums and email. If you're looking for a Discord server instead, then it stands to reason the asset will feel abandoned. kind regards

Hi! Well, it's hard to tell without profiling your game. It could be anything, from fillrate issues to expensive shading. It also depends on what your initial FPS were (dropping 30 fps down from 250 fps is a really small hit in terms of ms/frame, dropping 30 from 60 fps is a lot more). Please write to our support email so that we can help you. Thanks!

Thanks a lot Craig! we're glad you got a positive support experience. Let us know if we can help in any way.

Thank you for your words! thanks to kind hearted users I've been able to support the asset for so long. Hopefully I'll have your back for many more years to come! Let me know if I can be of any help.

Hi, "I was quite disappointed that there was no demo showcasing the interaction between the character and the liquid." A character is just a collection of colliders, no different from any other object. There's plenty of sample scenes included that feature collisions against both static and moving colliders: meshes, capsules, boxes, spheres, etc. "Additionally, the liquid rendering is a major issue. When using URP (Universal Render Pipeline), all liquids appear like lumps of clay—completely lacking transparency or reflections. " Please read the manual on how to setup fluid rendering in URP: https://obi.virtualmethodstudio.com/manual/7.0/fluidrendering.html You need to add a ObiFluidRendererFeature to your URP renderer asset as explained there, then add your fluid rendering passes to it. Otherwise transparent fluids won't show any reflection or refraction. "I believe that if the product does not yet support all rendering pipelines, or if the rendering compatibility is not fully prepared, it should be clearly stated in the product description that URP rendering is not supported. " URP rendering is fully supported as stated in the render pipeline compatibility tab. You just need to set it up. "As for support, I browsed your discussion forum and felt that a proper product should include a manual." It does include a very in-depth manual. There's links to it in the included quickstart guide, the forum, the "about" window, etc: https://obi.virtualmethodstudio.com/manual/7.0/index.html "This should detail how to configure features like Burst Count, rather than leaving users to figure it out themselves after purchasing by analyzing your scripts to understand the settings." There's no "Burst Count" setting in Obi that I'm aware of. Maybe you're referring to the emitter's "Burst" emission mode? For details regarding emitters, see: https://obi.virtualmethodstudio.com/manual/7.0/emitters.html ------- "By the way, the URP rendering settings screen might need an update. It was only after looking at it a second time that I realized the format was different" Turns out you were confusing URP's renderer asset inspector with URP's pipeline asset inspector. They're different things, the one shown in our manual is the renderer. kind regards

Hi, We're unable to reproduce this. Could you please write to support@virtualmethodstudio.com and give some more details? (render pipeline being used, renderer type, target platform you're building for, etc). As a side note, this is more a support request than a review. The problem with posting support requests in the reviews section is that: 1.- It will take longer for you to get any help, since your question may go unnoticed for a long time (publishers don't get a notification everytime a review gets posted). You got lucky we checked the publisher portal for an unrelated reason and noticed your review. 2.- It's not possible to attach files for extra information information like screenshots or crash dumps. 3.- Quite an awkward format for followup questions or conversation. 4.- Doesn't help other users in any way, since your problem may be unique to your situation. For these reasons using the provided support channels is best for everyone involved. "I also tried to reach out on the Obi forums multiple times. But I do not get registration codes on two email addresses. So I am sadly locked out of support." Have you tried writing to any of our support email addresses? "The issue can be easily reproduced. I created an empty project with Unity6 in-built render pipeline to test this. Imported only Obi7 and pressed build." There's an issue with ShaderGraph that results in a similar problem to what you're having, described in our troubleshooting guide (http://obi.virtualmethodstudio.com/manual/7.0/troubleshooting.html). The culprit is having unused render pipelines in the active targets lists of the graph, this will cause the shader to be compiled for a render pipeline that's not currently installed, and will result in compilation errors. The solution is to simply remove the unused pipeline(s) from the graph.

Hi There's no "OniColliderWorld" or "OniSolverImpl" included with any of the Obi assets in version 7. By the looks of it, you've imported ObiFluid 7 together with a much older version of ObiRope, this will break both assets since you can't mix different versions together as explained in the manual: https://obi.virtualmethodstudio.com/manual/7.0/setup.html "If you own several Obi assets, you can just import them all one after another as long as they have the *same version*. Do not mix and match packages with different versions, this might break your Obi installation. " If you wish to use Obi 7, you'll need to update Obi Rope as well. Btw, the reviews section in the store is not the way to ask for support. There's a support forum and several contact emails, including support@virtualmethodstudio.com, we'll be more than glad to answer your support questions there :) kind regards

Hi, Thanks for your review! The documentation is quite detailed, or at least we'd like to think so. It goes step by step over how to set up an emitter(https://obi.virtualmethodstudio.com/manual/7.0/emitters.html), explains all fluid parameters with small animations to illustrate each one (https://obi.virtualmethodstudio.com/manual/7.0/emittermaterials.html), fluid rendering (https://obi.virtualmethodstudio.com/manual/7.0/fluidrendering.html), collisions (https://obi.virtualmethodstudio.com/manual/7.0/collisions.html), same for all solver parameters:(https://obi.virtualmethodstudio.com/manual/7.0/obisolver.html) Also goes into minute detail about how the asset works internally (https://obi.virtualmethodstudio.com/manual/7.0/convergence.html) and how it integrates with Unity (https://obi.virtualmethodstudio.com/manual/7.0/updateloop.html) If you have any ideas on how this could be improved please reach out to us! "p.s please add some way to have your scene respond to a click of button with obi collider. like do a tool that says add obi collider to scene objects " It's a one-liner , here you go: var colliders = FindObjectsOfType<Collider>(); foreach (var c in colliders) c.gameObject.AddComponent<Obi.ObiCollider>(); Keep in mind though that assigning ObiColliders to *everything* in a scene indiscriminately will negatively affect performance, so you shouldn't typically do this. "can you also add someway for the emitter effect not to be parented to the solver." Not possible, emitters need to be under a solver (at any nesting level) to work. Just like UI buttons need to be under a Canvas to work, or joints be under a SkinnedMeshRenderer. "if that solver is child of ai and if animated death or ragdoll that solver and emitter is going with it." You should take the solver higher up the hierarchy, so that simulation is performed in world space instead of your character's local space.