A/V [ WOOT ] -- *Snapcam NAVIGATION STUDIO - 2.1*

EDIT:

Going to look into something I think could be triggering this. Let me test it out.

 

@Lars-Steenhoff

Alright, so I've tested it with everything up to the latest 2018.2.0f2 version and it seems like there's some underlying backend changes Unity has made that doesn't like my window being dragged / docked without making it also remain persistent too.

The (current) workaround is to simply mark the window as "persistent" (with the respective button at the bottom of the "Grid Navigator" window) before dragging/docking it -- after that, it can be docked/undocked normally.


I'm looking into a more permanent fix for this issue. As soon as I find one, I'll post it here.

Sorry for the inconvenience.

 

Thanks for the heads up!

 

I had the exact same error but it turned out to be an editor window with the issue. Changing to a default editor layout fixed it. I reset the layouts to factory setting then recreated my custom layout just to be sure.

 

Just an update --

Unity reproduced the bug and is now looking into fixing this behavior on their end. I am still awaiting their bugfix to see what actions I need to take from my end to properly resolve this issue (hopefully without splitting it into two separate window types -- i.e. a popup and a regular window -- just so I won't crash the Editor... )

 

Hotdogs! This looks incredible, and I'm wondering how I haven't heard of it before. Came across it via a post you made in the support forums, this would seriously improve my workflow!

Is this still in active development? It's hard to gauge due to the lack of reviews, and discussion here. Was there any resolution to that last bug you were looking at in August?

Would seriously love to add this tool to my list, this should be in Unity out of the box if its still all working.

 

I just bought SnapCam for the ViewNavigator but it's not what I expected. I expected to be able to control the speed of Unity's FPS camera control (RClick + WASD) but it just support Forward-Backward on LeftShift button. Forward-Backward movements are useful for flying through the scene but not for inspecting small objects.

I use RClick + WASD to move around the scene a lot. It's the easiest to navigate throught he scene and please support camera speed options for the control.

Thanks.

 

Also, while in orbit mode, I can't change zoom speed as the mouse wheel is used for zoom in/out instead of chaning zoom speed. I think the better way to zoom in/out is to use W or S key and mouse wheel to zoom in/out speed to keep it consistent.

I primarily needed the SnapCam to work with small size objects since Unity camera moves too fast for small objecrts. It looks like you primarily designed the camera for large size map and to fly around, not inspecting small size object. I hope you add finer control for small size objects too.

Thanks.

ps. Also, while in orbiting, the movement is too sensitive to the mouse movement. I think it will be good if you can have some sort of setting menus for the parameter so that we can adjust them ourselves.

 

I bought the asset and I would also love to see a way to control the speed of the flythrough camera. I work with huge terrains and the scale of the Editor Camera is simply too small if not unintuitive.

 

Thank you! -- This means a lot!!

Sorry about not responding! -- Apparently I've not been receiving notifications for this thread... :/


So, to answer some outstanding questions from @GeekGonzo, @chrisk, and @maydragon :

1. Yes, I am still actively developing Snapcam! -- Design work can be a nightmare though!
   
   
   If you've noticed a lack of updates, there are currently 3 reasons:
   
   
   • Unity has started to implement some requested features of the View Navigator into 2019.1 (such as WASD camera speed using the mousewheel). I am waiting for the 2019.1 release to assess a potential new design for the View Navigator's controls (the new global shortcut features are likely to interfere, so I need to assess what's possible in-detail.)
     
     
   • I don't like bugs in my tools -- Unity has yet to "fix" the docking bug, claiming it is one of those "by design" "features" (that throw an error when you do something completely normal that it doesn't like), so I'm reassessing the Grid Navigator's "hybrid pop-up" design too. The new "UI Elements" _might_ work for these kinds of windows, but I can't really say for sure since it isn't a complete API design yet. It could have the same (or worse) bugs in that kind of redesign. I don't want to sacrifice the current design by making it "popup-only" or "static-only", so I am trying to consider all design options at my disposal.
     
     
   • Flythrough controls with WASD have been impossible to implement due to the inability to increase the key repetition rate for the standard letter keys in the editor (and fire continuous events based on these), so I am hoping that 2019.1 will solve this problem with its shortcut keys feature, though I'm not holding much hope for this due to the continuously "At Risk" state of the new input system. If anyone knows a way to increase the repeat rate of the letter keys (in the editor) to fire off events, I would definitely appreciate a tip! Otherwise, we will have to see what 2019.1 brings with its new scene view navigation controls and custom shortcuts...
     
     
     
2. @chrisk -- I totally wanted WASD speed control in Navigation Studio too, but Unity totally b0rk3d us on this by having a buggy Editor "event" system esp. for standard letter keys (and being unable to increase their repeat rates except through the OS, meaning the speed letter keys fire in the Windows Editor is too slow and inconsistent for camera controls). The 2019.1 release might help you here though, since they implement exactly what you asked for.
   Regarding orbit / zoom controls -- you have a point. I'll consider your advice.
   
   
3. @maydragon -- If by "Flythrough camera", you mean holding the Shift key to fly forward, then just roll your mousewheel to change the speed of the forward movement "on the fly" with that. ;P

TL;DR

-- Thanks to 2019's new approach to basically everything UI-related, I am currently regrouping my UI efforts.
My fancy UI design stuff is on hold until I can get a stable platform, which also holds up the progress on my Adventure Navigator too.

 

Just purchase a few days ago.
Noticing that the Grid Nav. Window does not accurately reflect the position of the "snap" !
Before I delve further..is this normal?
I can go to the precise point I snapped when I use the slider on the Snap nav window and go to it..
But clicking on the snap via the Grid Nav window takes me close but not accurate.
Can this be fixed? What might I be doing wrong?
Thanks. Otherwise I find this software terrific!

 

What version of Unity are you using?

This could be due to the way 2019 is handling fov and pivot of the camera.You
can now change the fov, but originally it was set to 60 and couldn't be changed without effecting the camera position and pivot too). It's possible these are set or referenced differently now. I'll have to look into it when I get a bit of time.

By any chance, are you using the default snaps to test this? I'm not positive the thumbnail is accurate on some of those. Can you verify that the position is actually different, or if it's just the thumbnail that's off? The snap and grid navigators should be grabbing and storing the same data.

Maybe a screenshot could help?

Either way, I'll look into this when I get a bit of time this weekend. There's been some stuff I've been meaning to look at anyway in regards to 2019 changes.

 

Thanks.
Using 2017.2 Windows10
It's on a simple scene I set up. Not your included scene. I have objects of various sizes and placed here and there.

Yes, it's the snap that's off.
The icon/picture in the Grid Nav window looks perfectly placed itself. But clicking on the icon/pic in the GridNav takes you some distance back Z and a little below Y. from the icon/picture it is displaying.
Not much but maybe half a metre or so to a metre..
As I said, results with the Snap Nav window are perfect.
Thanks.

 

Interesting. I will definitely look into this.

It really sounds like the Unity Editor is grabbing the pivot point of the scene camera - fov, not the camera position itself. What's odd is that this is functional for the Snap Navigator. Theoretically, they should both be grabbing the same data. D:

 

Well turn me over in the spit !
Suddenly I cannot duplicate this "fault" I was getting previously!!!!
Lots of exclamation points, sorry for that but your great little program is doing what it should.
Both the Grid and the Snap Nav are taking me to exactly the same spot.
How can this be? Don't know. But there you be.
I haven't done anything that I remember.
Got a Oculus update..maybe that? Maybe a W10 thing?
I guessed at adjusting aspect ratio settings in my project but that didn't help,
So it's all very pleasing but confusing...

One thing I must ask:

Where does one adjust the Camera settings on your program's Scene Camera that is used in the Scene window?
It was late last night so I may not have searched properly.
I'd like to make some adjustments to it.
I must say many thanks for your prompt answers. Love the ease of moving to strategic editing points without the hassle of the Unity method. Nice to "click" and get there!
Now, where is that camera

 

Lol -- That's interesting indeed. Did you by chance close the editor and reopen it? Unity can be wonky sometimes, and that tends to "fix" some issues, but if you're doing VR stuff, that could probably introduce some bizarre bugs to the scene camera. I've not got a VR setup to test Snapcam, so I couldn't help you there.

No worries! If you want to change the camera itself (such as the fov), I've not yet implemented the ability to do this due to having to manage the fov manually (to support the ability to zoom while in Ortho and 2d modes). Since I knew a lot of scene/camera changes were coming in 2019, I decided to hold-off on implementing more features such as changing fov until I could get a feel for what might be coming in terms of specific UI stuff.

That said --
If you just want to change some keys, you might want to check the "ViewNavigator.cs" script. There aren't many keys that can move the camera at a reliable speed (due to the key repeat delay kicking in). The only keys this delay doesn't happen on is Ctrl, (Left)Shift, and Alt (as of 2017 and 2018 -- I'm not yet sure about 2019 since the event system has been heavily modified under the hood, but I plan to test the 2019 changes soon.)

 

Thanks again.
The clipping on your scene camera seems to be set at 1000 0r less?
Makes it very difficult to see ahead in terrains etc.
Somewhere to adjust this?
The rest seems great.
Thanks again.

 

Sorry for the delay -- I've been doing some testing on 2019 this weekend for new/alternative UI / camera workflows.

Setting the clipping for scene cameras was another one of those scene-camera features that 2019 implemented so I held off on upgrading it or making any further changes to it.


To answer your question -- the "ViewNavigator.cs" script would have that in it (I can't remember where, or even if I ended up setting the clipping manually or not), so you'll have to dig into the script a bit. Fortunately that's just a single script, and if I remember correctly, it could be either near the start (around the input checking) or somewhere near where I set the fov back (do a search for "60" to find the portion where I handle the fov).

It's important to keep in mind that this clipping value might be modified internally (by Unity) in certain cases -- especially when you roll your mouse-wheel. There is no way I can prevent them from doing this pre-2019, and I'm not sure about preventing it in 2019+ just yet either, but I'm still doing my research. Though, in 2019, it appears they have changed to a dolly-style zoom, so this problem might not exist now.
That being said -- Unity's scene-camera's clipping setting can be weird. This is likely due to how they do their zoom pre-2019. Unity uses a "sniper-style" zoom, rather than a "dolly-style" zoom (like I do, but it looks like they changed this zoom style in 2019) -- To do the sniper-style zoom, they must change the field of view. I, however, keep that constant and change the camera's actual position, which avoids the weird clipping issues many users have reported with objects that are right in front of the camera after lots of zooming (probably a precision issue imo.)
Dolly-zoom doesn't break anything, and it does keep clipping more consistent at different scales or zoom levels (despite one not being able to see quite as far in some cases like yours).
That trade-off can be mitigated if it becomes too problematic by simply deleting the ViewNavigator.cs script, however you will lose the new scene-camera controls by doing this. This is unavoidable though, since the scene camera is a very special case and is not persistent in the scene (like regular scene cameras are), and as such, it does not work the way you might expect it to when changing its position or the way it sees the world. Unity doesn't like anybody messing with its internal stuff, so modify these settings at your own risk.

Hopefully that explains some things!

 

Just an update from here.
I find that translation of an object is very awkward when using Nav. Studio.
Create say a cube. Then try to scale an axis. That seems ok but when I then wish to scale another axis I find I must reclick before the scale tool will change to that axis.
The same with moving the object.
No problems if not using your software.
Any clues? Maybe it's related to 2017 versions?

 

Yes, this seems like a bug with drag not restoring interaction with gizmos.
I don't use drag at all for left clicks, so I'm not sure what Unity is expecting internally.

There _might_ be a workaround if you remove/comment-out the Left click mouse event checks in the View Navigator.cs script. I don't recall using this event anywhere, so that could fix your issue. I haven't removed it because I had some ideas in mind that would use it, but Unity might just be expecting me to use or release the control.

Either way, let me know if this works.

I've been looking at rewriting Navigation Studio for 2019, so I'm putting low priority on improving it for earlier versions.
Major user experience issues like yours I will still look into though, so no sweat on that front.
2019 has done a lot of stuff that makes the current View Navigator somewhat redundant. 2019 doesn't fix everything though. For example, I can't orbit objects easily, and zooming in on them is still a pain. The F key is not great for framing either. These are still issues I want to fix, but since they've revamped the entire scene camera system, including scene camera with nested prefabs, I've got my work cut out for me. Not to mention I still want to include the Adventure Navigator soon.

 

Hi,
Just bought SnapCam, but I'm using Unity 2019.1.5.

Obviously it was a mistake; if I had checked this forum I'd have known to wait. Still, the tool seems promising, and the reviews were great.

But I'm not looking for any fancy features at this point. ALL I WANT to do is to be able to fly around a scene at a reasonably high speed. Unity's WASD camera accelerates infinitely, so I have to stop completely, then accelerate (slowly) again, then stop and hope I've guessed where the camera is going to end up.

I've been using Unity since <2009, and I've tried a few scene camera plugins -- but they tend to be very unreliable.

If you have a suggestion, or a beta version, that could at least get me SOME usability (a free-flight camera with a speed control would meet 99% of my needs), I'd really appreciate it.

I'll wait to post a review for a while, but from what I can see, the camera doesn't navigate in 2019.

PS: Is there a manual or instructions anywhere? Thanks!

 

There are a few places things are scattered about, including the promo video on the Asset Store and some info in the text file included in the asset, but I really need to make a clear help file. I plan to do that once camera controls are finalized.

I can totally understand where you're coming from with this.

Sane camera control was one of the two original reasons I designed Snapcam (the other was that I wanted to snap to any position in the world I wanted to).



To be upfront, I don't make much on Snapcam already and Unity's cut hurts a lot. I have set the price low to purposefully offset for some of the pains new users like you may go through in waiting for me to get a good camera control design ready for 2019.1. That said, although Snapcam isn't my primary focus in life, I still do use Snapcam myself for game design and I take A LOT of pride in making it great since it is my first (and only) asset.
I am not satisfied with it being a pre-2019 plugin either, so as I have had time, I've been trying different methods of approaching camera control that will work in harmony with 2019.1 (now that it has been finalized).

Unity 2019.1 camera controls take A LOT of experimentation to get the right min/max camera speed values and are just fiddly in general. And as you change between scenes, these camera movement values tend to need to be changed -- a lot. This is another major issue I'd like to address with the new View Navigator.



I too hate the fact that there is no limit to the speed of the acceleration of the camera, so thanks for pointing that out. I will look to see if I can get Snapcam to limit that in 2019.1.


I'm aiming at a week before I can get deep into it, but I'll keep everyone posted here as soon as I am able.
Thanks for your patience on this.

 

That sounds excellent (awesome, in fact!).

A couple of quick comments/suggestions:

• Decent (in-editor) camera controllers are far more rare than I would have imagined! I've spent a lot of time searching the Asset Store (on more than one occasion over the years), and the vast majority of camera controllers focus on gameplay cams rather than in-editor controls.
• Because of that, I would definitely not fret about your pricing. I think a lot of regular Unity users have come to appreciate (and notice!) the sellers who support their products -- and it's clear that Unity's changes -- while mostly great and welcome -- are causing huge headaches to the vendors. I'd far rather pay extra for a good asset that's well-supported vs one that works in 2019.1.5 but can't install to 2019.1.6!
• In terms of sales, I'd strongly suggest posting a (very) feature-limited version, once you've stabilized the new products. (Perhaps you're already doing this!) Since Unity's editor-camera is universally seen as a royal pain, I think you'd make a splash (and a lot of friends) even if your free product did nothing more than address the endless acceleration!

 

Thanks for the feedback, @BlackManatee!


So, as promised, I've been looking heavily into finally getting a better camera setup for the 2019 editor camera -- especially in terms of limiting acceleration.

In short, limiting acceleration in 2019.1 would require a major rewrite of the entire SceneView camera controller under the newly-implemented (heavily undocumented) shortcut management system. However, Unity has locked down their in-scene camera controller (no way to override it), so the only option to fix the acceleration issue is to (again) rewrite yet _another_ version of it.. which totally sucks for both of us (because my project is also currently in 2019.1).

BUT! You are in luck.

https://unity3d.com/beta/2019.2
Editor: Added a toggle to the Scene Camera settings for infinite acceleration when navigating with flying mode.

Unity is making amends for this horrendous acceleration oversight in 2019.1 by fixing this specific acceleration issue in 2019.2! So for all practical purposes, you _will_ have your fix as soon as 2019.2 releases.
Sadly, 2019.1 is out (for the acceleration fix) because it will mean a potentially hack-y camera controller for you if I made my own again totally from scratch. I will have to (again) counteract the effects of the default camera controller (and make it work for 2d, 3d, and Iso modes too). This would include lots of hoop-jumping since Unity tends to do some out-there stuff with its shortcuts to get its "fly mode" to work. A big, error-prone rewrite of a system that has potential seems like overkill (now that the camera controller is being fixed!)



Please be aware that even with the acceleration fixed, this wont solve all issues with Unity's scene camera (just a very fundamentally broken one!)
My goal with Navigation Studio is to ensure editor navigation in general is a breeze. I will implement better camera control as part of this process. For example, Unity has yet to fix orbit, framing, or zoom controls in a fully satisfying way, so those will be my next task. I'm very much open to suggestions if there are more pressing pain points, but ultimately, I just want visualization in our scenes to be as simple, user-friendly, and instantaneous as possible. That's why the Snap and Grid Navigators were born, and why I took the time to rewrite Unity's scene camera controller the first time with the original View Navigator.

Even though I'm averse to rewriting the new scene camera controller from scratch again (it's currently impossible to do the same way using the new shortcut system), maybe I can still convince them to open up the scene camera controller!! For now, I can still at least supplement its functionality with better orbit, framing, etc., which I already plan to do. I also aim to add some other editor-specific stuff for large streaming worlds soon (no fancy features -- just downright _practical_ navigation stuff). I know you bought Navigation Studio for better editor camera controls, but please don't write Navigation Studio off just yet -- I've still got plans that will make editor life easier for anyone designing games!

This is generally good advice. Sadly, Unity has modified its algorithm so free (or very low-priced) assets are actually now frowned upon by the asset store search. They purposefully don't drive much traffic anymore due to how Unity has recently setup things.

Maybe good reviews will help more now? I don't know, but I can support one asset a lot better anyway.
I take a lot of pride in making my stuff great (and useful!), so it's okay if I can't drive that much traffic.
It's not about numbers for me -- I just want to make a good, well-designed, tool.

 

So just an update --

I've been doing some research into a redesign of my beloved Snapcam for 2019.3 and up, and one of the issues I faced with it was whether to scrap the ViewNavigator since the Unity Editor scene camera is now "usable" to some extent.

Are there any features you still use/enjoy in the ViewNavigator, or would you prefer to go mostly vanilla with Unity's camera?


I ask this because I think there are still a couple of reasons to keep the ViewNavigator (one is mainly for camera rotation / zoom around a selected gameobject, and another is the flythrough mode using shift, the mousewheel, and RMB actually being like "flying through" your levels), but many of these are still at odds with Unity's default controls and must counteract them to effectively disable them in order to function.

The simplest option would be to go forward without the ViewNavigator, focusing solely on Snapcam as a game visualization tool (rather than a camera control tool), but I've not yet decided.
NAVIGATION STUDIO's identity seems to revolve around its Snap Navigator, which offers a small-but-powerful method of scene camera control, but the View Navigator, especially, emphasizes this notion of "camera control" by literally allowing one to control the scene camera. However, this muddies the overall message of "game visualization" I had intended to convey with NAVIGATION STUDIO after including "scene camera control" as a core facet of its identity. Apparently "game visualization" becomes "scene visualization through the camera" now, and it is something I would like to get away from.

When I say "game visualization" -- I really mean it. For the entire game. Not just the scene camera's view of the game.

I've got a few tools in the pipeline that will show off what I mean more explicitly, but for now, I want to know your thoughts on nixing the ViewNavigator in favor of the 2019.x camera system (and a proper move toward game visualization).

 

Hi, there, I thought you abandoned the project. You mentioned that you have something really cool to show a really long time ago but there hasn't been any update. But I'm glad that you are back.

Don't get rid of camera control. 2019.3 camera control is somewhat useable but it's not perfect yet.
I really haven't been using it extensively and let's wait until 2019.3 and I'll let you know what's is lacking.
Until then, you can work on the scene camera. It would be nice if you can show what's in your mind.

Thanks.

 

I haven't used SnapCam utility in a long time, but seems I was having give it more time than I wanted and the saves weren't reliable. I cannot comment on your question, but will be watching further development.

 

Thanks for the feedback. I've been looking into a bit of a redesign of the base snaps system. This redesign should fix any of the issues with the saves that occurred in later versions of the Unity Editor.

Thanks for that! -- And no worries! I have lots of plans for this project. My absence has just been due to lack of time. Snapcam doesn't make much, but I still wouldn't abandon it without a word. I respect my customers more than that.

In short, the area of game visualization is definitely a much-needed area to fill, but that's also the very reason I haven't shown anything particularly cool yet. There aren't (yet) any tools like the ones I'm designing out there, so I've been keeping them close to my chest for now. I've had a few people rip off my designs with Snapcam, so I want to try to minimize that with any new tools. The Adventure Navigator is very useful for large game worlds, but it has gone through several iterations since I first mentioned it thanks to various real-world usage scenarios already. I plan to make use of some upcoming features of Unity that aren't polished enough yet, so I'm holding out for this too. In the meantime, I still have to make some soul-searching decisions about the Snap Navigator and View Navigator designs going forward, so there is no shortage of work. This has resulted in a bit of a delay due to life getting in the way, but developing these tools' designs holistically is still my goal, and I want to make sure I tackle that first.

That said -- do expect the Adventure Navigator to debut in the nearer term though. I'll reply here with details when I get it closer to its final design! -- In the meantime though, I'm really sorry for the suspense! I hope it will be worth the wait!

 

Snapcam 2.2 (and 3.0) - Updates!


Hey everyone! -- Sorry it's been so long. I've been expanding my horizons while taking a much-needed creative break from Snapcam! This has led to some good things! -- However, now that I'm back, I have plenty of news to share -- some good, some 'bad'.


'Bad' news first:

There have been some great developments in Unity over the last year -- but one of the _key_ developments I had been waiting on (in order to properly integrate the Adventure Navigator and other tools into a suite of tools) was Unity's ability to handle Shortcuts and Workspaces in a more "sane" way. Sadly, Unity has yet to deliver on this aspect (even in a 2021 release cycle it seems). This framework looks like it's about a year away from beta still. This means that Adventure Navigator is still considered very "alpha" as well right now, and its entire implementation is likely to change. So, in response to this, I am exploring other possible (future-proof) UI designs to combat this issue. I really don't want to water the experience down, but I might have no choice -- for a while at least.


Now for the GOOD news!

Firstly, I have resumed development on Snapcam's core features and am about to submit the latest version for review on the Asset Store. This means Snapcam is no longer 'broken' for the latest 2019.4 (LTS) version.

• Grid Navigator was given some love -- It didn't take into account the FOV when changing positions. This is fixed. It should now move to the "exact position" in the preview.
  
  
• There was an issue with playing audio in the editor (which is meant for feedback for when a new "snap" is either added/removed/loaded/etc.) -- but apparently Unity didn't like audio and prevented users from saving Snaps because of the error. So I told Unity to "sit on it" and made snaps save (and audio work again) anyway.
  
  
• The iconic "snap" sounds are functional again, so I've lowered the volume on the samples to make them much less "obtrusive".
  
  
• View Navigator is going to be reworked to complement the Unity SceneView camera controls (rather than fight them) -- so I am considering alternative options and controls for this. Please let me know what you love/hate about the current camera!

On to OTHER news!

Adventure Navigator is still coming! -- Right now, the one thing majorly preventing this tool's release is that I am quite heavily involved in influencing and "correcting" Unity's new Tool and Workspace workflows in order to ensure they are sufficient for a proper "suite" of game visualization tools.


Thanks to this hiatus with Snapcam, I've actually solidified the direction I want to go with it in the future.

So one thing that everyone has been asking for was a way to (more explicitly) control keyboard shortcuts and the basic camera motion. Since Unity is not likely to deliver a proper solution for this for a LONG time -- or at least for another year -- I thought, what if you could control pretty much _everything_ about Snapcam through Bolt (now that it's free?)
I am looking into this as a potential avenue for user-specific camera control modes (along with other possibilities), but I wanted to know what my current users think about this idea/direction. There are so many types of camera "modes" that this could have "modules" for (i.e. 2d, 2d Isometric, 2d layered, Topdown, FPS -- and these are just the standard ones). The current View Navigator doesn't take into account user control preferences on how to manipulate these (and shortcuts can only do so much).
With my lack of time, I am simply unable to implement them all (and all the new features I have planned). However, with a decent enough BASE system (provided through VS), I am sure I should be able to provide an easy-to-use (beginner-friendly) system to easily setup your own types of cameras / controls for the View Navigator.

Remember -- Unity VS is not a promise, just a direction I'm heavily exploring and looking for some feedback on.



LASTLY -- A couple of questions (in closing):

• How many of you use (or would like to use) the 2D features of the ViewNavigator?
  
  
• Should Unity's VS be part of Snapcam / NAVIGATION STUDIO or not?

Feedback would be much appreciated! ^___^

 

Is there a way to disable gear in scene view?

Maybe I can comment some lines to get rid of it?

 

When I make a snap a get this error and my preview images are really dark. Unity 2018.4.20



When I turn off this button and turn off scene light button. I don't get this error when I make snap

 

If you take feature request. I would love to have option to use my own images for snaps.

 

@awesomedata, there's aslso annoying bug, when I open new scene in Editor, Snap window automatically opens itself

 

When I launch scene where there are no snaps created. I get those errors

ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
System.ThrowHelper.ThrowArgumentOutOfRangeException (System.ExceptionArgument argument, System.ExceptionResource resource) (at <e1319b7195c343e79b385cd3aa43f5dc>:0)
System.ThrowHelper.ThrowArgumentOutOfRangeException () (at <e1319b7195c343e79b385cd3aa43f5dc>:0)
System.Collections.Generic.List`1[T].get_Item (System.Int32 index) (at <e1319b7195c343e79b385cd3aa43f5dc>:0)
Snapcam.SnapNavigator.ReadSnaps (System.String dir, System.Boolean temp) (at Assets/Snapcam/Scripts/Editor/SnapNavigator.cs:851)
Snapcam.SnapNavigator.SnapLoad (System.Boolean useTempDir) (at Assets/Snapcam/Scripts/Editor/SnapNavigator.cs:793)
Snapcam.SnapNavigator.OnPlayModeChanged (UnityEditor.PlayModeStateChange state) (at Assets/Snapcam/Scripts/Editor/SnapNavigator.cs:174)
SnapcamUtilities.EditorPlaymode.OnPlayModeStateChanged (UnityEditor.PlayModeStateChange state) (at Assets/Snapcam/Scripts/Editor/Utilities/EditorPlaymode.cs:20)
UnityEditor.EditorApplication.Internal_PlayModeStateChanged (UnityEditor.PlayModeStateChange state) (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:302)



IOException: Sharing violation on path Assets/Snapcam/Scripts/Editor/Editor Default Resources//temp.asset
System.IO.File.Delete (System.String path) (at <e1319b7195c343e79b385cd3aa43f5dc>:0)
SnapcamIO.FileIO.FileWriter (System.String p) (at Assets/Snapcam/Scripts/Editor/Utilities/FileIO.cs:22)
Snapcam.SnapNavigator.WriteSnaps (System.String dir, System.Boolean temp) (at Assets/Snapcam/Scripts/Editor/SnapNavigator.cs:807)
Snapcam.SnapNavigator.SnapSave (System.Boolean useTempDir) (at Assets/Snapcam/Scripts/Editor/SnapNavigator.cs:768)
Snapcam.SnapNavigator.OnPlayModeChanged (UnityEditor.PlayModeStateChange state) (at Assets/Snapcam/Scripts/Editor/SnapNavigator.cs:178)
SnapcamUtilities.EditorPlaymode.OnPlayModeStateChanged (UnityEditor.PlayModeStateChange state) (at Assets/Snapcam/Scripts/Editor/Utilities/EditorPlaymode.cs:20)
UnityEditor.EditorApplication.Internal_PlayModeStateChanged (UnityEditor.PlayModeStateChange state) (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:302)
UnityEditor.EditorApplication:Internal_CallGlobalEventHandler() (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:329)

 

When I make a snap I can't see Unity UI Canvas

 

@Gua -- Thanks for the feedback!! - I'll address these ASAP.

Also, sorry for the delay in my reply -- I wasn't notified of any replies in this topic until you messaged me! D:

So let's get started...

If you are using the vanilla Unity camera movement (i.e. WASD keys) instead of the alternative scene camera movement options (i.e. the ViewNavigator functionality) such as forward movement with the Shift key and/or rotation functionality with the Spacebar + mouse movement to rotate around the selected gameobject, then to remove the clutter in the SceneView you can simply delete the ViewNavigator.cs script, and you should be good to go.

As a plus -- I am looking to be heavily involved in Unity's new Overlay / UX system. My goal is upgrading Snapcam to Unity's new Overlay (and shortcut) system as soon as Unity gives me enough of a platform to do so. This will greatly benefit me in solving UX issues I've been forced to work around using Unity's current (non-sensible) approach to its UI implementation.

There are some weird (Unity-generated) bugs in the 2018 releases in regards to UI and lighting (and many many other things, actually). I think some of these have to do with backported "fixes" in the LTS versions.

If you can, I highly suggest upgrading to 2019.4 at least. I am no longer officially supporting anything below 2019.4 due to these unpredictable issues with UI. Most of the new tech stack UI bedrock exists in 2019.4, and the majority of these "glitchy" UI issues are gone with the latest editor releases. The latest Snapcam release (currently awaiting approval on the Asset Store) should fix the other issues.

I'll have to look into this one. This _could_ be triggered by your custom scene-opening script somehow, but I will have to make sure. Feel free to PM me your code for your MenuItem in your toolbar you're using in that video so I can make sure what I'm doing is compatible and not interfering with what you're trying to do behind the scenes. The issue could easily be related to 2018.LTS UI issues though. Like I said -- weird UI bugs aplenty in 2018. D:

I'm aware of this one -- this bug was related to how Unity handled (or rather _didn't_ handle) SceneManagement when I developed the architecture for Snapcam back in the day. Now that Unity seems to have proper functionality for managing Scenes in the Editor these days, I will get a fix for you on this one ASAP.

This one would be useful if you could show me a video showing how to reproduce the bug -- However, again, I suspect it has something to do with Unity's general UI problems in 2018, as I do nothing at all with the in-game UI / UI Canvas / UI situation as a whole -- I generally only use standard EditorGUI elements.


Overall -- I will get you a new build ASAP!

If you don't mind, I will handle the rest of the responses via PM (trying to keep the thread a bit clean for the moment due to the current need for other kinds of feedback), so please respond to me in a private message if you would!

 

2 issues SnapcamAudio.AudioTools.PlayClip (UnityEngine.AudioClip clip) (at Assets/Snapcam/Scripts/Editor/Utilities/AudioTools.cs:33)

and i cant see any of the video in this fourom because they have a sign saying cookie setting and do nothing when i click them
..
i have no clue how to make this works with the error or otherwize.. a little help? somehow give me a link to a video that works

 

If this is the video you're referring to, you can either click the link or copy/paste the text-based link below into your browser to see the video:

Code (CSharp):

1. https://www.youtube.com/watch?v=1jbKijEQMsA

To get started, you can toggle open the SnapNavigator by pressing "S" and add a couple of new "Snap" positions (by either middle-clicking in the SnapNavigator window or by right-clicking and selecting "Add Snap") whenever you've arrived at the positions in the Scene you want to return to later.

After adding a few snaps, you can either tuck the Snap Navigator window out of the way and use the slider in it to switch between these locations as you need to or close the Snap Navigator with "S" and temporarily open the Grid Navigator with "G" and click on an image to zip to anywhere you wish. You can also close it with "G" as well if you decide to not go to another location. I am currently working on revamping the workflow as I have time (making the Grid Navigator more functional and self-contained)

There is also a help file / readme / howto in the package as well, describing further functionality.


What version of Unity are you working on?

This error was caused after Unity changed some things in regards to playing audio in the Editor.
This has been fixed (along with other things) in the current version of Unity (in the 3.0 beta version of Snapcam), but I have not released it yet because some people still seem to be using older versions of Unity (and I still have a few more things I want to add/experiment with before the official 3.0 release).
However, if you are on a more recent LTS version of Unity, feel free to PM me to let me know if you want access to the (more stable) beta version meant for the (more 'recent') LTS versions of Unity, as this sounds like it might be the issue.

 

You've put a lot of time and energy into this obviously, it looks really useful thanks for your service to the Unity community!

 

Thanks for your kind words! That made my day!

 

Are there extra "navigators" on the itch store version or is the Unity store version up to date?

Thanks.