Playmaker Forum
Bug Reporting => PlayMaker Bug Reporting => Topic started by: westingtyler on September 25, 2016, 05:50:08 AM
-
I use a mouse pick to determine where the laser sight should land in my game.
since updating to unity 5.4.0b24, the cursor in the play mode window does not line up with the mouse picked location. playmaker 1.8.2f7
the location v3 saved by the mouse pick (shown in white text in the game window) DOES correspond to the location of the objects in the scene, but to make my laser pointer be at that spot, I have to move my actual cursor up and to the right, so far sometimes that I try to shoot a flying enemy, and it defocuses play mode because I have clicked outside the window. this used to work fine, and now I can't playtest my game.
The mouse pick works normally in a compiled game (because it takes up the whole screen?) but obviously it's not viable to compile a build of my game every time I want to playtest.
please help.
-
Hi.
I think this might be an unity issue and not from playmaker.
You can try updating to unity 4.1 and also update PM to 1.8.3
let me know if the problem is still there.
If it is, can you show what is going on and show the fsm's / action (in a video if possible)
-
could this be caused by custom font size settings in windows 10?
-
I uploaded a video of the problem. I THINK it has to do with the new unity game view scale slider messing up the Mouse Pick action in playmaker. https://youtu.be/wEiAFg9KpM8 (https://youtu.be/wEiAFg9KpM8)
video description has these details: The mouse cursor and the mouse pick location do not align since the Unity game view scale slider was added. Watch how the game view Scale slider distorts the mouse pick location, looking at the scene view. Does the Playmaker Mouse Pick action need to be updated to account for the game view scale slider?
Issue still present after updating to playmaker 1.8.3.f4
-
Hi,
Could you also show how you set up your action?
or even beter could you export and share the scene.
right click on the scene and select export package, then un-check dependencies
and press export
-
in the video I pull the playmaker editor over and show how the fsm is set up, action by action. if that doesn't provide any light, here is the scene, having done the steps you mentioned.
-
Hi,
I just tested the scene you have send and it works perfectly on my end.
Have you updated unity to Version 5.4.1f1
I tested this on pm 1.8.3f4
unity 5.4.1f1
and window 8.1
-
Btw,
This is a better way to set this up :
(http://imageshack.com/a/img922/1227/iRMtT6.png)
-
I tried this in 5.5.0b6 and had the same problem, but I have not tried in 5.4.1f1.
I am using windows 10.
I was told by oculus to use my current version of unity for best compatibility with the Oculus Touch assets.
-
I just started a new project in unity 5.4.0b24, the version of unity that has the problem.
I imported the scene in this thread, that I had already uploaded, into the project, along with Playmaker 1.8.3.f4.
It works fine.
What could this mean?
-
Hi,
Probably some settings in your project or something interfering the variables.
If you want you can upload your project and message me a link to check it out.
-
i appreciate that. the project itself is like 40 gigs because of all the imported 3d models and such from the asset. store. is there a trick to making the project smaller for upload? the large size is also the reason I can't submit bug reports - the report is like "we'll upload your 40 gig project, too" and I'm like "no you won't."
-
Hi,
Wow 40 gigs is a lot, are you using all of it?
Maybe make a backup (which you should always have)
and clean it up a bit if many things are not used.
You can try using 'export package' and see how big the file is.
In the project window Select your scene, then right click and select Export Package..
(this might look like it's not responding and might take a while depending on your project size)
When exporting keep dependencies checked.
If you just send a private link to me you can leave it as is.
If you want to share public you need to remove the playmaker.dll file from the export list (in the plugins folder)
-
what I might do is export random packages to import into that clean project, to pinpoint which assets are causing the issue. if I can upload the project in a sane way I will try to do that. thanks for your help.
15 gb of my project is in a folder called metadata. is that important?
-
Hi,
It is probably from an asset you added.
Have you tried the export package i mentioned?
-
i have not tried the export package. but I did discover something.
in the project I sent you, the simple one-scene one, turning on "Virtual Reality Enabled" (Oculus SDK) caused the problem to happen, but as soon as I turn OFF "Virtual Reality Enabled" in the Player Settings, the problem disappears, and the mouse aligns with the in-game cursor in play mode. What could this mean?
Also, now building my big project works, but then the game won't recognize the rift, and the app stays in 2d screen mode while my rift stays dark. possibly not related, but this happens now even with really old builds I have made of my game, from earlier versions of unity. When I play other, official, oculus store games, the headset is recognized fine.
-
Hi,
I have not worked with VR yet, but you should try to look around on the unity forum.
I don't think this is a playmaker issue.
-
thanks for all your help in narrowing down the issue. i am going to still experiment with the export package thing. would that be a way to export my project with only the used files, then create a clean project with only the used files? or is there a way to "remove all unused files from project?
thanks again!