[RELEASED] Pro Camera 2D - The definitive 2D & 2.5D Unity camera plugin

Parallax layers are not showing up for some reason. I've removed them from the culling mask on the main camera and everything seems to be in order. Any idea what's creating this problem?

 

@johannig It seems you're using the new URP, which is currently incompatible with the Parallax and TransitionFX extensions. I'm sorry about the inconvenience, but I do have planned an update to add support for it.

 

Oh sorry, hadn't seen that yet. Glad there's an update coming soon!

 

@luispedrofonseca any updates on this? Unity 2019 is now on LTS, I assume it is stable now or there are still things preventing the updates for ProCamera2D?

 

@luispedrofonseca Is it possible in a future update to add UnityEvents on ProCamera2DRails extension when the rails are enabled/disabled, i.e. at ProCamera2DRails.EnableTargets() and ProCamera2DRails.DisableTargets() ?

 

Hi, is there a way to keep the shaded rectangle bounds of the camera (from ProCamera2DContentFitter) viewable in the Scene window without having the Camera selected in the Hierarchy? If not, is this a possible feature in the future. It is very helpful while laying out a scene to visualize the camera's boundaries, even though they may change depending on the device's resolution.

Thanks!

 

@Stilghar You're right. It should be stable now, I'll look into it.

@Nikaas I'll add it in a future update. Can it be regular C# events instead?

@FireMutant The only way I can think of is to open two Inspector panels and on one leave the camera selected.

 

Sure, they are fine too. I said UnityEvents because I saw them at the Rooms extension. Anyway UnityEvents are a pain in custom inspectors. Their gameObject drag and drop does not work with custom inspectors, only object select window.

 

Noticed a bug related to the Rails extension and prefabs variants (2020.1.6 and 2020.2.0 beta)

1. Create camera prefab.
2. Create variant of the prefab.
3. Make scene copy of the variant prefab.
4. Modify rails path in the scene.
5. On scene instance of the prefab click Override -> ProCamera2DRails.

When you click 5, the path gets restored to default state.

Similar thing happens when trying to disable extensions. Add extension at the variant level. Then start transitioning between base->variant->scene. If you try to disable some extension (through the enable/disable buttons) it will get reenabled after you do back and forth transitions between scene<->variant. If you remove the component the usual way it does not happen.

 

@Nikaas I'll have a look at that and see what I can do. Not sure if it isn't a bug with Unity's prefab system.

 

BTW if that would help I just noticed that after unpacking the variant and the base prefab (i.e. pure scene object) the rails path that I edit at the scene is still applied to the variant prefab. Variant path change though is not applied to the scene.

 

@Nikaas Those are certainly related issues. I'll see what I can do about it.

 

2 questions.

Is it possible to zoom absolutely vs always relative? I want to do: ProCamera.Zoom(10) and have that always zoom to the same "level". Currently, it seems to only allow me to zoom relative to the current zoom factor.

Is it possible to read the current zoom level?

Why I ask:
I have a character that skis... when he crashes, I zoom in. Then, when I reset, I need to zoom back to the baseline.

I would prefer to not have to keep track of the relative zoom amounts as I may zoom in/out for various reasons. Plus, if I have to reset the zoom when a zoom is in transition, then I'm not sure how to calculate the amount required to back-out the zoom to my original.

-Jeff

 

@jeffweber You can use the "UpdateScreenSize" method to directly set the camera size. The "Zoom" method is always relative by definition.

 

Hello @luispedrofonseca

i have a strange issue, i'm using transitions fx on my main camera. When i start the game i use transition exit, and when level is loaded i use transition enter. Then i go back to main menu (main camera is singleton, i use a bootstrap menu) and when i call the transition exit it doesn't happen. On level loaded transition enter still happens normally.

You can find the example in the video. I get no warnings or errors in the log.

Unity is 2018.3.7., PC2D is 2.6.5.

 

@Oshigawa Please update to the latest ProCamera2D version and see if it still happens.
If so, please submit a bug report through the support page here: http://www.procamera2d.com/support/

 

Still not working, submitting the report.

 

@luispedrofonseca

I have a feature request unless you can show me a way I can do this with the current system.

I have a large world that requires me to occasionally shift my origin in order to avoid floating point inaccuracies.

When I origin shift, I translate everything in the world by some amount and need to do the same with ProCamera2D.

I tried just translating the underlying ProCamera2D transform and of course that did not work because I have smoothing enabled and that does not account for your internal variables related to smoothing.

I also tried 'MoveCameraInstantlyToPosition', but that does not quite work either because it resets the smoothing variables and causes a noticeable visual glitch when the origin shift happens.

The only way I could get this to work was adding my own method to ProCamera2D:

Code (CSharp):

1. public void Translate(float x, float y)
2.         {
3.             _transform.localPosition += new Vector3(x, y, 0);
4.  
5.             CameraTargetPosition += new Vector3(x, y, 0);
6.  
7.             _cameraTargetHorizontalPositionSmoothed += x;
8.             _cameraTargetVerticalPositionSmoothed += y;
9.  
10.             _previousCameraTargetHorizontalPositionSmoothed += x;
11.             _previousCameraTargetVerticalPositionSmoothed += y;
12.  
13.             TargetsMidPoint += new Vector3(x, y, 0);
14.             PreviousTargetsMidPoint += new Vector3(x, y, 0);
15.         }

This worked perfectly. Could you add a method that does this?

-Jeff

 

@jeffweber Actually, just very recently I had another client asking me exactly the same thing! That's not part of the core component, but I can definitely see the benefit for it.
Would you mind me adding your code (with some slight changes)?

 

I don’t mind at all. Thanks.

 

Should TranstitionFX be working with the Universal Pipeline yet? Nothing happens for enter or exit, but if I trace the code I can see it's hitting the coroutine correctly and incrementing/decrementing the transition values correctly.

I"m using 2020.1.9.

Here are my camera settings:

 

@luispedrofonseca
Any ideas on the above. This would be really useful for me but if TransitionFX does not support URP I'll need to roll my own solution.

Thanks

Jeff

 

@jeffweber That is correct. TransitionFX and Parallax extensions are not supported on URP (or HDRP) yet. I have plans to implement them but no timeline estimate yet.

 

hello
i have a question.

If using CenterOnTargets() ,the camera will move to the target instantly,
Is it possible to move smoothly instead of instantly?

 

@mk7gwc Not through that method. Can you please explain what you're trying to achieve? There's probably another way to do it.

 

@luispedrofonseca
OK
https://drive.google.com/file/d/1jQ77O03Kuw966Ii6i3dfQZ947gfLqVTw/view?usp=sharing

As you can see from this video, we are currently using the "Camera Window" feature of Procamera 2D to follow when the target goes out of a certain area.


The target stays at the very limit of the range. In the case of this video, it is difficult to see the upward direction. Therefore, for example, if the character is on the floor for a few seconds, we want the camera to move smoothly to the center.

 

@luispedrofonseca I'm having a strange issue with damping(?) not working intermittently. More info posted on your forum, double-posting here for visibility!

https://procamera2d.proboards.com/thread/221/intermittent-camera-movement-smoothing-issue

 

@mk7gwc Apart from dynamically resizing the camera window to zero (and then back to the current size) I'm not seeing any immediate solution for your problem. However, this is an interesting problem to solve and I'm there are other users who could benefit from a better solution. I'll give it some thought and see what I can come up with.

@Aurigan Thanks, I'll reply there.

 

@luispedrofonseca
OK.thanks!

 

@luispedrofonseca
I just grabbed the latest version of ProCamera2D that has the new "TranslateCamera" method. I think there is a bug with that method.

When I call that method, it ends up shifting my camera on the Z axis.

Looking at these two lines:
var currentPos = _transform.localPosition;
var newPos = currentPos + VectorHVD(translateAmount.x, translateAmount.y, Vector3D(currentPos));

If translateAmount is (300,300) and currentPos = (10,10, -60)
Then newPos = (310, 310, -120)

Then you do:
_transform.localPosition = newPos;

Which pushes my camera back to -120.

-Jeff

 

Hmmm...
I also think this logic does not quite work:

_transform.localPosition = newPos;
CameraTargetPosition = newPos;
TargetsMidPoint = newPos;
PreviousTargetsMidPoint = newPos;

Here you are setting the CameraTargetPosition = newPos, but what if localPositon and CameraTargetPositon were not equal prior to the translation

I think you need to translate all values separately.

 

Bumping this for @luispedrofonseca
Not sure you saw this, but would love a fix in future version so I don't have to use my own logic.

 

Thanks for the heads-up @jeffweber! Sometimes I stop getting notifications from the forum for some weird reason. I'll see what I can do about that bug.

 

Hi @luispedrofonseca
I have a game with a 3d grid in isometric view, that 3d grid provide a bounds property.

I have a Canvas UI with
- Header (Part of Scale with Screen Size uGUI)
- Content Area (this is where my 3D element will appear)
- Footer (Part of Scale with Screen Size uGUI)

and i want to "fit" that 3D grid inside the content area perfectly by manipulating camera.



Your plugin seems to offer all these but may require an example scene cater to above needs?
So if i buy the plugin, can you please provide support for above usecase?

Thanks

 

@jGate99 That seems feasible. If you encounter some trouble getting it to work let me know.

 

Any idea when parallax will be supported on URP? It's been creating a bit of a bottleneck for me the past couple of months Cheers!

 

Unfortunately I don't have a timeline yet, but hopefully soon if time permits! Sorry about the inconvenience.

 

Hi @luispedrofonseca

I'm having trouble on making

RemoveCameraTarget(Transform)

work.





Am I doing it like it's supposed to? Thanks.

 

@MSavioti That doesn't look right. Can't pinpoint exactly what you're doing wrong but something must be out of place. Please contact me through the support page: https://www.procamera2d.com/support

 

Are there any updates on rotated camera? It was mentioned on the forum couple of times over the years but I didn't find anything on it

 

@jflejmer I actually explored that possibility a couple of years ago, but it ended up being too complex as it would require a large rewrite since it would essentially make it 3D camera.
Like I said before, it can be used outside of the predefined rotations/axis (XY, XZ and YZ), but some calculations will be offset. Many customers have done it, but it's not officially supported.

 

Do you have plan to adopt asmdef? Currently I have to restructure your source and add asmdefs manually. Though it's quite easy since I don't have to edit your code, it's still tiresome everytime I update to the latest version.

 

@Laicasaane I haven't thought of that to be honest. Can I ask what are the benefits? If it's to speed up compilation time, you can put the ProCamera2D folder in the Plugins folder and that should make it only compile once.

 

It's not about the compilation speed actually. The main reason is I've been using asmdef in every projects, and any asset not adopt asmdef makes it impossible to be referenced in the main project. (Asmdefs can be auto referenced in Assembly-CSharp, but not vice-versa.) The second reason is with asmdefs I can make ProCamera2D a package and put it in the [project]/Packages folder for Unity to exclude it from the C# solution, thus reduce the workload for Visual Studio. Or I can unload specific .csproj in the solution and that can also reduce the workload.

 

The other benefit is with asmdefs, you can choose to exclude some .dll from the build. For example, I want to retain ProCamera2D example codes in my project so I can easily examine them when needed, but I don't want to include example codes in the final build. For that I will move all examples to a folder named ProCamera2D.Examples and put an asmdef into it then uncheck every platform.

 

@Laicasaane I see, thanks for the explanation. Makes a lot of sense. I'll add it to the next release. Can you show me how you'd prefer the asmdef's to be setup?

As for including the example scenes in the final build, from what I understand they're automatically excluded, as is everything else that is not part of the Build settings. So as long as the example scenes are not on that list you should be good.

 

I think this structure is ideal

Code (CSharp):

1.  
2. .
3. └── ProCamera2D/
4.     ├── Editor/
5.     │   ├── ProCamera2D.Editor.asmdef
6.     │   └── ...
7.     ├── Runtime/
8.     │   ├── ProCamera2D.Runtime.asmdef
9.     │   └── ...
10.     ├── Presets/
11.     │   └── ...
12.     ├── TransitionFX Textures/
13.     │   └── ...
14.     ├── Examples/
15.     │   ├── ProCamera2D.Examples.asmdef
16.     │   └── ...
17.     └── 3rd Party Plugins/
18.         ├── PlayMakerActions/
19.         │   ├── ProCamera2D.Plugins.PlayMakerActions.asmdef
20.         │   └── ...
21.         └── ...
22.  

I'm afraid it's not, or at least with asmdefs, I've tested this before. For example, even though the ProCamera2D.Examples.asmdef is nowhere referenced, the ProCamera2D.Examples.dll is still included in the final build.

 

And I advice to uncheck this box so the asmdef will use names for the references below. Because GUID can change, sometimes unexpectedly.

 

Hello ,please let me know if the asset support isometric 3d view(camera ruler(30,45,0)) now?if that i will buy it ,thanks~

 

hey!
when i set timescale to 0, i often but not always get this error as shown in the picture. in PC2D component i've set it to ignore timescale.

this only occurs when Update mode is set to Late Update, is there a reason for that?