Pixel Crushers Forum

I believe I have set up the Journal button according to your tutorials. After pressing the J button, the journal will display, but because Invector is controlling the cursor, I could not 'click' on any journal entries or even the close button (presumably due to Invector).
I did add a second OnClick condition (see image) to pause the player and free up the cursor. Clicking entries in the journal now work, however, when pressing the J button to dismiss the journal, the player is still paused and the cursor is still visible. Not sure how to dismiss the journal and return the cursor to 'Invector' state (not shown) and un-pause the player??

Hi,

Quest Machine includes dedicated integration packages for Invector. Import these packages:

• Assets / Plugins / Pixel Crushers / Common / Third Party Support / Invector Support.unitypackage
• Assets / Plugins / Pixel Crushers / Quest Machine / Third Party Support / Invector Support.unitypackage

Then look over the setup guide in Pixel Crushers / Quest Machine / Third Party Support / Invector Support. Among other things, it explains how to add a Quest Machine Pause Player component that coordinates cursor control with Invector.

I had done the two imports. After reviewing the document as well as going back to study the example Invector demo, I noticed the demo had the OnClick values set as shown in bottom image. However, in my project, the MessageEvents.SendMessageToSystem is not an available selection (top image). ??

Hi,

I'm not sure why the MessageEvents component is missing, but it's easily remedied. Open the Invector integration example scene, inspect Quest Dialogue UI, right-click the Message Events (Script) heading, and select Copy Component. Then open your own scene, inspect the Quest Dialogue UI, right-click on any component's heading, and select Paste Component As New. You can paste the same thing onto the Quest Journal UI, too. Then you should be able to hook up the OnOpen() and OnClose() events.

OK, I am officially a bone head now. I started to perform the steps you suggested and while scrolling down within the demo scene, I noticed the Message Event script. Duh....went to my scene, and sure enough, it was missing...gezzzzz. Oh well, added the component, filled in the fields, and bingo, it works as designed. Sorry for pulling you away from more important requests....as always, thanks so much for your fast and clear reply's.

No problem! Glad to help.