Mega Book - Easily create working 3D books Comics

I don't know how I missed that, I was using buildpages() on awake function.
Thanks

 

Hi SpookyCat, One question want to consult :

does world space Ui ( such as button ) can be curved just follow the page turned ?

in your previous description , the world-space ui is just attach to page , in theory , this kind of ui seems can't be deformed as turned page , the ui is just follow the page turn position , but can't be deformed, right ?

if so , any tip or idea how this world-space ui button can be deformed just follow the deforming turning page ?
Thanks.

 

Unity UI objects do not expose a mesh that can be deformed and generally a button is small enough that attaching it to a page works well. My only suggestion would be either have a mesh copy of the button as content to the page that could be toggled on and off as the page turns, or if it is just buttons then use a mesh button as part of the mesh content for the page and have collider attached to the page for the button and do simple button script that raycasts against the collider for touches or clicks.

 

Hey @SpookyCat,

I'm on 2019.3 / .4 and using the latest version of Megafiers & MegaBook w/ HDRP
.
Things seemed to have changed and I was hoping to confirm whether or not this was by design or a bug.

So - originally, as described in the documentation and the site - the book populates with a few pages. Each of these pages inside the covers has a white texture overlaid on the front and back. The name of these textures are "MegaBook Front" and "MegaBook Back", and they are set in the "Pages" foldout section.

As of 1.47 what happens is every page mimics the cover page. Every page uses the Front & Back material from the "Mesh Options" foldout unless explicitly overwritten by the Front & Back Material in the "Pages" foldout.

Should that be happening?

Thanks in advance!

 

To answer the question above a new update just been accepted to the Asset Store that brings support for different Render Pipelines.

Changes in v1.49

• Updated the Book builder so make it compatible with Unitys new Render Pipelines. There is now an option for the Shader Texture name so you can control which texture is set by the Book Builder. Change to _BaseColorMap for non Standard pipelines.
• Fix for error if mesh content does not have a 2nd UV channel present.
• MegaBook made compatible with Unity 2019
• MegaBook made compatible with Unity 2020

 

Hey I actually just did this (If I understand correctly what you were trying to do), if you want to check it out. Essentially I wanted to have panels of comic interactable - so I placed translucent collider gameobjects over the page panels, and used GetPage() to reference whether the objects need to be enabled or not.

 

Hello.
I purchased your asset a few days ago and I'm playing around with its features. I saw in a post here that it supports Unity UI elements, so I tried to add a button via MBComplexPage, but it doesn't appear on the book pages after I click rebuild. Is there a step-by-step tutorial on how to achieve this?

The ui button is the one in orange with the "OK" text, the other elements are simple 3D cubes and they work as expected.

 

Thank you for the purchase. The mesh content system can only add content that is mesh based, so the UI stuff uses sprites so they cant be added that way, and even if they were mesh based adding them like that would lose all the functionality of the object as only mesh data is used. To add a button or something you need to Attach it to the page, it then remains an object with all its components so will work as expected, again though you can only attach objects that use Transforms and world space.

 

I attached the canvas to the first page, it appeared ok but when the page flipped, the UI buttons just turned a few degrees instead of following the page (they are attached to page 0, in the screenshot you can see page 1).



PS: In your example screenshot here, I see the canvas is not a child of a page. I just figured out that by "attach" you meant to add the canvas GameObject to the page via the Pages/Page Objects menu in the inspector. I'll play around with this a bit and see what I get. Thanks.

 

Thats because you are not attaching the object to the page you are just making it a child of the page, being a child means it knows nothing about the current deformation of the page mesh, when you attach an object to the page it will act like it is stuck to that point on the page so as it deforms and bends the transform of the object is changed to keep it in the correct place and angle as the page turns. Go to our website and look at the MegaBook section and scroll down to the 'Page Objects' section, it runs through the options for attaching objects to a page.

The demo book in the asset has a page with an object attached.

 

Yes, I just figured this out myself, thanks. I'll play around a bit and come back with a proper support ticket if I need anything more. Thanks again.

 

Hello. I've been working on this project for a year and a half with no issues regarding MegaBook. However I have some craziness happening currently. Out of nowhere (Have not touched the MB gameobject in a while) the book has translucent duplicated pages, the cover and back bend back way too far, and the first page is 'stuck' while the other pages flip though with the duplicates as well as the proper pages. Essentially there is always a stuck page flipped up and seems to throw off the entire book.This is blowing my mind because it's literally when I need to make some demos for this... lol. Any ideas? Let me know what you need to know. I guess I may have to rebuild the book but I've customized a bunch of things and that would be a headache to an extent. Thank you <3

 

Oh man. I just fixed it. Somehow all children got enabled under the book parent when I purposefully had some disabled, which were those duplicates and stuck pages... Working now. Phew.

 

Just a quick heads up that MegaBook is in the lightning sale at 50% off, only a few licenses left at that price.

 

Only 2 licenses left at 50% off, soon be gone.

 

I'm looking to make a big book — of an actual (rather lengthy) eBook. It will probably come out to nearly 1000 pages. And to make it worse, I'm doing this for mobile VR.

So, I'm not sure MB's standard flow of having all the mesh content available at build time and "baking" into a book makes sense. I would rather have a callback that asks me for the content of each page just before it's shown. And I certainly hope that if my book is 1000 pages long, there aren't really 1000 individual page meshes being submitted to the rendering pipeline.

Can anyone tell me if it is possible to use MB this way (on-demand page content), and whether it is smart about not rendering all the pages you can't currently see (except for their edges)?

 

A small update submitted to the Asset store, this makes MegaBook compatible with Unity 2021 and 2022. It also adds a new option to Recalc Tangents for the pages so if you are using a Bump/Normal mapped material for your pages it will work correctly now.

Changes in v1.51

• MegaBook made compatible with Unity 2022
• Option to have Tangents recalculated when pages turn which is needed if you use bump mapping on your pages.
• MegaBook made compatible with Unity 2021

 

It's a really nice tool to use, but I'm having some problems now.

I also encountered this problem when attaching images and text to the page, may I ask you for how do you modify it?