• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
vroad

Improve handling of shared script entities

3 posts in this topic

When the engine loads precompiled bytecode, it performs linear search from ALL types which was registered before loading. I think this is because the engine doesn't know which module has shared entity. So saving the name of module to the bytecode would allow the engine to search shared types from fewer number of the types.

 

Other problems of shared script entities are
  • bytecodes doesn't have information about dependencies. You need to store them to another place and load manually.
  • you need to mark all entity as shared to use them from other modules.

What do you think about it?

0

Share this post


Link to post
Share on other sites

Shared entities was introduced as a mean to allow modules to interchange objects without causing dependency on which module is compiled in which order.

 

The module name is not part of the bytecode. You can load the same bytecode into different modules (sometimes that is necessary to get separate set of global variables).

 

I didn't quite get what you meant with the comments in the bullet list, so I have probably not answered what you really asked for.

 

 

There are certainly improvements that can be made. You mention the linear search of all types. This can quite easily be optimized if there is a need for it. Are you seeing performance issues with loading pre-compiled bytecode?

0

Share this post


Link to post
Share on other sites
Sorry I was confused. Let me sort my thoughts out first.
You said that there is no need to worry about which bytecode should be loaded first. That means declaration and implementation of shared functions will be saved to every file when I save them?

Linear search of script entities may incur some performance penalties, though it's very smaller than the case of string constants.
0

Share this post


Link to post
Share on other sites

Yes, the shared entities are saved in all byte codes to guarantee that they will function regardless of the order in which modules are loaded.

 

 

You may want to know that I have plans to make improvements to the import functionality, which currently only works for global functions. Importing entities would be different from shared entities in that the imported entity must have been compiled / loaded in a previous module for the import to work. I can't say exactly when I'll get to work on this improvement though.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0