Video

Should be as is in the video. Is the hole listed in the NavMesh's Inspector, and is it surrounded by the NavMesh from all sides. If need be, you can click Bake to make the hole ahead of runtime and see the effect it has.

Dialogue timing and skipping options are set at the top of the Speech Manager

@@ChrisIceBox OMG you're a lifesaver!!! I'm still a noob in unity/adventure creator and there's a lot of pressure for me right now. Thank you for responding! Appreciate it!

AC will work with 2022's way of working yes - so long as the NavMesh is baked, AC will make use of it. A tutorial covering the differences between Unity versions can be found here: adventurecreator.org/tutorials/unity-navigation-pathfinding

Apologies for the hassle - are you using URP or the built-in render pipeline? It may be down to a change in the Unity Editor, I'll take a look.

Hey Chris, No, I've tried with the URP too (with the URP-dedicated resources) and that's a different scenario altogether. I've just posted a message on your forums. @@ChrisIceBox

Do any related messages appear in the Console? Check that you have "Hand bone" transforms assigned in Tin Pot's Player Inspector, and that you're using the "Character: Hold object" Action to take the book. Just before, search for the Book in the Hierarchy window and keep an eye on it when taking the book. Where does it move to in the Hierarchy, and what is its position? When selected, you can go to the Scene window and press "F" to focus on it. If you still have trouble, share screenshots over on the forum and I'll take a look: adventurecreator.org/forum/

@@ChrisIceBoxthanks for your quick reply, I found what I missed~~~ Thanks a lot~~~

If it's the one using draggables, no - each should be independent. If it's the drawer that uses ActionLists, you'll need to rely on ActionList assets and the Set Interaction Parameters component to have multiple prefabs use the same logic. See the Logic Prefabs tutorial video for details on the latter, but if you can share screenshots on the forum I'll take a look

@@ChrisIceBox Where can I find the Logic Prefabs tutorial?

@@pushingpandas6479 www.adventurecreator.org/tutorials/logic-prefabs

AC won't interfere with post processing, but you'll need to bear in mind it's the AC MainCamera that does all the rendering. If you're attaching a post processing component to a camera, add it to the scene's MainCamera.

@@ChrisIceBox thank you Iam dumb. I used post processing volume instead of "volume" in URP ... LOL

Okay so I went out and found out from another video. the AI - > navigation no longer comes installed with Unity so you have to install it from the packet manager (AI navigation) and then you go window -> ai -> navigation (not the obolete one) and then you bake. Similar, but confused me. Also make sure your path is wide enough to accomodate the nav mesh. I have a feeling that there's some numbers you can change for that but my cube was too thin to show the blue navmesh

@@awhellyeah543 The differences in baking NavMesh depending on Unity version can be found in the tutorial here: adventurecreator.org/tutorials/unity-navigation-pathfinding With the AI Navigation package, the radius is set from the "Agent Type" field in the NavMesh Surface component - click "Open Agent Settings.." from the dropdown to configure the size values that used to be in the Navigation window.

@@ChrisIceBox Didn't think you'd reply which is why I just went ahead and looked for another solution but thank you! :D I didn't think to check AC's documentation (stupid of me, I know)

@@awhellyeah543 No problem! If you have any more issues or questions, feel free to ask here or on the forum over at adventurecreator.org/forum

Do you have a copy of your player model in the scene file? AC will spawn in the Player prefab you assign in the Settings Manager when you hit Play, so you don't need your character to be in the scene file itself. If that's not it, best to see screens - post details on the forum at www.adventurecreator.org/forum/ and I'll see if I can spot the issue.

@@ChrisIceBox No I thought that was the issue but deleted it out of the scene when you said I should. I will post on there shortly and will use some screengrabs too. Thanks for the prompt response!

You can use the "Engine: Manage systems" Action to disable AC's Movement, Interaction etc systems, but dialogue itself still relies on the ActionList, Cutscene and Menu systems so you'll still need to set up AC via the Scene Manager.

You could incorporate platforming elements, particularly if you made use of a dedicated custom motion controller, but I'd recommend relying on a dedicated "platformer game" asset over AC, which is intended for traditional adventures.

@@ChrisIceBox appreciate you reply

A tutorial covering third-person Direct control can be found here: www.adventurecreator.org/tutorials/making-3d-game A text tutorial covering the creation of 3D characters can be found here: adventurecreator.org/tutorials/making-3d-character If you'd like to share screenshots/details of your own setup over on the forum, I'll try to spot what's wrong: www.adventurecreator.org/forum/

You're most welcome!

RETWEET - thank you so much!!!

Make sure that your Settings Manager's "Camera perspective" field is set to 2D - this'll be set automatically if you opt to make a 2D game when running the New Game Wizard.

@@ChrisIceBox Although I initially set the game design as 2D, in the "settings manager" I had the camera set to 3D. I changed it and everything works as it should :D Thank you

Yes. The only effect AC has on rendering is the Highlight component, and that'll work with URP's Lit shader.

Check that the GameCamera's Camera component is disabled - AC should disable it automatically, but a script from another asset could feasibly re-enable it. The GameCameras are just position references, it's the Main camera that should be the only one rendering

@@ChrisIceBox you are rigth! Thank you! That fix it

What is the error message in full, and what are both your AC and Unity versions? Best to share details over on the forum where we can look into it properly: www.adventurecreator.org/forum/

@@ChrisIceBox ok. I'll switch to forum

"Choose Hotspot Then Interaction" will open up the Interaction menu by default - but you can still have the behaviour as in the video for specific Hotspots by checking "Single 'Use' Interaction?" in the Hotspot's Inspector. This is what the 2D Demo does (which also uses this Interaction method) for its Exit Hotspots, since you typically don't need to see a list of icons for an exit. The empty black pixels sounds like the Interaction menu turning on, but with no Interaction icon that matches the one defined in the Hotspot - "Exit" in this case. If you want to rely on the Interaction menu for this case, you just need to add that icon type to the Interaction menu - which you can do by adding a new "Interaction" element that's "Cursor" is set to "Exit".

Check that your Settings Manager's "Camera perspective" field is set to 2D - the behaviour you're describing sounds like it's set to 3D. Did you select 2D when using the New Game Wizard?

The order of tracks in the Action should match that in the Timeline, so it may just be that your order is different in the asset. If you can share screenshots of the Timeline and the Action running it over on the forum (adventurecreator.org/forum), I'll try to spot what's wrong.

@@ChrisIceBox ALsom the mouth shapes for Brain, were those created in another software and imported in ?

@@SayceBuckleyFreak Yes, the modeling was done in Blender - including the shapes which are Blender Shapekeys, and imported into Unity as Blendshapes.

What is your AC version, and does clicking the Hotspot result in the AC variable changing value? Best to see screenshots of your setup - I'd only be making guesses otherwise. If you, share screens/details of your setup over on the forum and I'll try to spot the issue: www.adventurecreator.org/forum/

@@ChrisIceBox I'll get on the forum tonight. But I did a quick check before leaving this morning and no, during runtime nothing fires up in the animation graph when clicking the hotspot. It shows the name of the door but no doesn't open, only when I manually click on the IsOpen variable. Also, should be the latest version of AC, just downloaded it yesterday. I'm sure I might have missed a step.

@@kelvina.2031 I'll look out for your post, but I was referring to the AC variable's value, rather than the Animator parameter. Keep the Variables Inspector selected and see if its value changes - we'll need to determine if it's a case of the variable not updating, or it not being linked to the Animator.

I had the same thing happen. Had to add cabinet to the variables slot in the link variable to animator component

@@avocadofiregame Ah! So glad I checked the comments. This solved the problem for me. Thanks!

If the Settings Manager's "Hide cursor when locked in screen's centre?" is unchecked, AC's main cursor will display in the centre when it is locked (i.e. free-aiming is possible). To have it be display at all times, just add it to an Image component as part of a Unity UI canvas. If you want this separate Image to only show when the cursor is locked (allowing for a separate texture to show instead of the main cursor), you can use this script on the AC wiki: adventure-creator.fandom.com/wiki/Adding_a_separate_crosshair

A Document can be opened using the "Document: Open" Action. For it to appear on screen, you'll need a Document menu. One is included with the default interface, but if you're missing it you can copy it from the Default_MenuManager asset file by switching to it at the top of the Menu Manager. This menu can be modified, but by default will display the Document's title, page text, and image.

For areas of the screen that the player can click on, yes - but interactivity can also be achieved through Triggers and Input.

Thanks very much! A series of tutorials on extending AC through scripting can be found here: www.adventurecreator.org/tutorials/third-party-tools-and-customisation

Hi, it has a "drag camera" that scrolls when the player clicks and drags - but not a screen-edge camera like that. You can, however, add custom camera types. If you have a script that handles this movement style, you can attach AC's "Basic Camera" component to it to have it be listed in e.g. "Camera: Switch" Actions and the Scene Manager's "Default camera" field. See the Manual's "Adding custom cameras" chapter for more details on this.

A shop system example can be found on AC's Downloads page: adventurecreator.org/downloads

Playmaker is a general purpose visual scripting system for any game type, while AC is a toolkit specifically designed for traditional adventure games with an emphasis on storytelling and puzzle solving.

The length is inevitable, I'm afraid, given the size of the existing project. If you're looking for smaller, more manageable tutorials, you can find a series of text tutorials starting here: www.adventurecreator.org/tutorials/introduction

It really depends on what you want to make. If you want to make a traditional adventure game that AC is designed for, then it'll help you out whether you're a coder or not. If you are a coder, AC caters for extensions by providing event hooks and a documented API

@@ChrisIceBox thank you!

AC does not support VR, no, though there are those who have added VR functionality through custom scripting.

@@ChrisIceBox Ok, thanks for the quick response!