Plugins Positioner - Main camera and Atom Positioner Plugin

[Case]

Nitpick:

If your plugin controls the orientation of the containing atom, the plugin isn't targeting the atom, it's aiming the atom (think of a gun in your hand(s): You're aiming the gun, and you use the ironsight to target your ... target). Sorry for the beancounting, but 15years @Uni have left me with some pet peeves regarding proper terminology ...

P.S.: I see you acted on my feature request! Thanks!

 

[cyberdelique]

there is a bug with the triggers:
when triggering a specific position, it works once but not twice. you have to trigger another pos to be able to trigger again the first one.
work around is to trigger another pos and then trigger the one you want

 

[Takashima]

there is a bug with the triggers:
when triggering a specific position, it works once but not twice. you have to trigger another pos to be able to trigger again the first one.
work around is to trigger another pos and then trigger the one you want
View attachment 266107

Thank you for the bug report and for posting a workaround. I have also noticed this yesterday and I've updated the main page of the plugin that this is a known bug. For some reason every second time, I get an empty value when calling the Action instead of the selected value. I'm working on it when I have time, but I don't know yet, why this happens.

 

[ShiRO]

Hey ! my plugins being often corrupted and i need to reload it and do again the pos, it's clearly unusable for me help me please.

btw it only do it when i put it on the WindowCamera i'll switch to another atom i think but it's strange

 

[Takashima]

Hey ! my plugins being often corrupted and i need to reload it and do again the pos, it's clearly unusable for me help me please.

btw it only do it when i put it on the WindowCamera i'll switch to another atom i think but it's strange

I assume you have the newest game update installed. Do you see something in the error log? I haven't seen this error yet, will test a bit more with the Windowcamera.

 

[Takashima]

gardanzero updated Positioner - Main camera and Atom Positioner Plugin with a new update entry:

Important bugfix release

• The issue that the "Set Position" Action only fires after values have been changed, has been fixed
• I highly recommend to update as soon as possible to this one

Read the rest of this update entry...

 

[Takashima]

there is a bug with the triggers:
when triggering a specific position, it works once but not twice. you have to trigger another pos to be able to trigger again the first one.
work around is to trigger another pos and then trigger the one you want
View attachment 266107

Should be solved with version 8. In my testing it now works reliably, without changing the value first. Let me know if it works for you as well. Thanks.

 

[ShiRO]

I assume you have the newest game update installed. Do you see something in the error log? I haven't seen this error yet, will test a bit more with the Windowcamera.

Hi, sorry for late response, i don't know i switched to an Empty object and i do not get the error anymore.

 

[cyberdelique]

Should be solved with version 8. In my testing it now works reliably, without changing the value first. Let me know if it works for you as well. Thanks.

yup works fine now, thanks

 

[virtualdude112]

Hey, total newbie here; could you give a short explanation as to how I can set the actions for looping the camera?

I tried adding a button as trigger and added the action to it as per your screenshot. But it does not work for me.

Is there any chance this could also be done with Keyboard bindings (e.g. Pressing "C" to loop view?

 

[Takashima]

Hey, total newbie here; could you give a short explanation as to how I can set the actions for looping the camera?

I tried adding a button as trigger and added the action to it as per your screenshot. But it does not work for me.

Is there any chance this could also be done with Keyboard bindings (e.g. Pressing "C" to loop view?

Hmm... you can't pull this off with just my plugin. My plugin has an action 'Set Random Position (specific group)' you can call, that will load one of the saved camera angles from a group at random and set the main camera to it.

If you want to call this action every x seconds, I recommend you look the Loop Logic brick here:

LogicBricks - Plugins -

Overview LogicBricks is a collection of now 34 reusable logic plugins to quickly build simple logic without coding. These go from a simple Relay that just groups triggers via Counter and Blend to more complex bricks for RandomChoice and a very...

hub.virtamate.com

With the Loop logic brick you should be able to call my action every x seconds. And you'll need a trigger (e.g. a UIButton) to activate the loop. Perhaps you can make a keyboard binding to this UIButton, I have never looked into that myself.

Hope this helps.

 

[mynaughtyaccount]

Is there anyway to make a bunch of camera positions and then save a scene and load with the same positions as before? Now matter what I do whenever I reload a scene all camera positions are gone. Please lmk! Getting a bunch of camera angles in a scene that can be recalled after loading a scene is exactly what I need.

 

[Takashima]

Is there anyway to make a bunch of camera positions and then save a scene and load with the same positions as before? Now matter what I do whenever I reload a scene all camera positions are gone. Please lmk! Getting a bunch of camera angles in a scene that can be recalled after loading a scene is exactly what I need.

Hi, @mynaughtyaccount, yeah that's the intention of the plugin and works for me. Normally, when you save a scene, all the positions that were created are saved in json format along with the scene data.

I assume you're using the latest version of VAM? Otherwise, I don't know how I can help you. I can upload an example scene with some saved positions, if that helps.

 

[mynaughtyaccount]

Hi, @mynaughtyaccount, yeah that's the intention of the plugin and works for me. Normally, when you save a scene, all the positions that were created are saved in json format along with the scene data.

I assume you're using the latest version of VAM? Otherwise, I don't know how I can help you. I can upload an example scene with some saved positions, if that helps.

Sorry total newb move on my part, got if fixed now and is working great! (Had it as a session plugin instead of in the scene)

 

[hentailondon]

Really useful plugin!

Oh nevermind, there is a plugin which comes with AcidBubbles Keybindings called "Keybinding Extensions", there you can activate functions for "Positioner" like "Next position" for the Keybinding plugin. Wohoo!

Is there a way to bind a key to save a position or cycle through the available monitor camera positions (or maybe a group)?

I'm using AcidBubbles Keybinding plugin but can't Positioner in there, so assume there is no native compatibility.
Has anyone found a way? Maybe a plugin which can bind keys to triggers?

 

[Takashima]

Really useful plugin!

Oh nevermind, there is a plugin which comes with AcidBubbles Keybindings called "Keybinding Extensions", there you can activate functions for "Positioner" like "Next position" for the Keybinding plugin. Wohoo!

Is there a way to bind a key to save a position or cycle through the available monitor camera positions (or maybe a group)?

I'm using AcidBubbles Keybinding plugin but can't Positioner in there, so assume there is no native compatibility.
Has anyone found a way? Maybe a plugin which can bind keys to triggers?

Awesome, I didn't know that. Thanks for posting the solution!

 

[ringoapple]

Hello @gardanzero,

I hope this message finds you well. I've been using the Positioner plugin extensively in Virt A Mate and am truly impressed with its functionality and how much it enhances the user experience.

I wanted to suggest a feature addition that I believe could significantly enhance the plugin's utility further: the inclusion of import and export functions. Having the ability to import and export settings would greatly improve workflow efficiency, especially for users who work on multiple scenes.

I look forward to any updates and am excited to see how this great tool evolves.

 

[Takashima]

Hello @gardanzero,

I hope this message finds you well. I've been using the Positioner plugin extensively in Virt A Mate and am truly impressed with its functionality and how much it enhances the user experience.

I wanted to suggest a feature addition that I believe could significantly enhance the plugin's utility further: the inclusion of import and export functions. Having the ability to import and export settings would greatly improve workflow efficiency, especially for users who work on multiple scenes.

I look forward to any updates and am excited to see how this great tool evolves.

Hello @ringoapple

Thank you for your kind feedback.

Could you explain a bit more, what you are doing and how an import/export functionality would help? Maybe you can provide example scenes, where you are using the same camera positions, or positions of objects in multiple scenes? Just so I better understand, what the use case is.

I'm not sure yet how to achieve an import/export, but I think it should not be too hard to do. But I can't make promises on the timeline.

 

[ringoapple]

Hello @ringoapple

Thank you for your kind feedback.

Could you explain a bit more, what you are doing and how an import/export functionality would help? Maybe you can provide example scenes, where you are using the same camera positions, or positions of objects in multiple scenes? Just so I better understand, what the use case is.

I'm not sure yet how to achieve an import/export, but I think it should not be too hard to do. But I can't make promises on the timeline.

Hello @gardanzero,

Thank you for your response and for considering my suggestion! In my workflow, I use the Positioner plugin to set up camera positions in my animations, and I save each cut as an individual scene within Virt A Mate. It would be incredibly helpful to have the ability to export these camera settings from one scene and import them into another, to ensure consistency across different cuts and save time.

I understand the complexities involved in adding new features and appreciate your openness to exploring this. Even if the timeline for this feature can't be confirmed now, knowing that it might be considered for future updates is very encouraging.

Thank you once again for your support and for creating such a versatile tool.