job000184
Closed
Unity Crashes after trying to verify my p4 connection settings.
My experience after installing the P4Connect unity package:
- I could not edit Perforce settings after integrating plugin. Sorry, didn't save log error. Restarting Unity fixed this.
- After restart, see this error in the console:
"
Multiple plugins with the same name 'p4bridge' (found at 'Assets/P4Connect/Editor/p4bridge.dll' and 'Assets/P4Connect/Editor/x86_64/p4bridge.dll'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor.
"
- Can edit settings now though, after entering in user/pass/workspace I get this on the final verify:
"
P4Connect encountered the following exception:
Client '<myclient>' unknown - 'client' command to create it.
P4Connect will disable itself...
"
Closed dialog, Unity crashed
My experience after installing the P4Connect unity package:
- I could not edit Perforce settings after integrating plugin. Sorry, didn't save log error. Restarting Unity fixed this.
- After restart, see this error in the console:
"
Multiple plugins with the same name 'p4bridge' (found at 'Assets/P4Connect/Editor/p4bridge.dll' and 'Assets/P4Connect/Editor/x86_64/p4bridge.dll'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor.
"
- Can edit settings now though, after entering in user/pass/workspace I get this on the final verify:
"
P4Connect encountered the following exception:
Client '<myclient>' unknown - 'client' command to create it.
P4Connect will disable itself...
"
Closed dialog, Unity crashed
- Status
- Closed
- Project
- perforce-software-p4connect
- Severity
- A
- Reported By
- infosekr
- Reported Date
- 10 years ago
- Modified By
- Norman Morse
- Modified Date
- 10 years ago
- Owned By
- infosekr
- Dev Notes
- This is a combination of "multiple plugins" and "crash" bug.
Both of these should be fixed in Beta2, closing. - Type
- Bug
Hi Infosekr,
Yes, some errors can be expected on the initial install. Usually restarting Unity will fix them.
I think in your case, you need to remove the old P4Connect before installing the new one.
The Client unknown error means that you need to set up a Client/Workspace. I recommend that you do this
and make sure it is usable in P4V before you try configuring P4Connect. P4Connect does not provide a way to create new client workspaces, they need to be configured from the command line or P4V.
Use the connection settings from P4V to help you discover what you need to configure P4Connect properly.
I do have a client/workspace setup from p4v, possibly the command line is not finding it as I believe I have seen in the past. I will play around with it to see if i can get it to work.
The crash is unnerving though.
Some more clarification. I did remove P4Connect, as I do with all Unity packages because the Unity package system is flawed and can't handle upgrades correctly.
I got rid of the Client unknown error by doing the following.
(This is completely unintuitive and misleading, the only reason I knew to try this is other cases where my command line env variables were not set correctly. If i check this box it sounds like my current connection settings will be used at the command line, but I don't get this)
P4Connect crashes Unity when trying to verify my workspace settings. Note: to get Unity to even load P4Connect I had to delete one of the duplicate copies of p4bridge.* files. I deleted the main ones and left the x86_64 version.
I'm having the same issue with Unity 5 with a new empty project. After importing the plugin it says: "Multiple plugins with the same name 'p4bridge' (found at 'Assets/P4Connect/Editor/p4bridge.dll' and 'Assets/P4Connect/Editor/x86_64/p4bridge.dll'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor."
When I try to connect to a good workspace, Unity crash.
I was also getting the Client Unknow error and get rid of it the way infosekr said. But after verifying the workspace, Unity still crash :(
the server is local (localhost:1666), don't know if it can help :)