• 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
Arthur Valitov

Unsigned int64 wokring wrong

8 posts in this topic

Dear Andreas and all,

 

1) This code will cause an error "Implicit conversion changed sign of value":

uint64 ui64b = 4294967295;

But this won't:

uint64 ui64b = 4294967296;

2) If I declare a global application function like FnTestUint64(uint64 val) and pass ui64b variable to this function, then there are two different behaviours:

 

uint64 ui64b = 4294967295; FnTestUint64(ui64b); // C++ debugger will show incorrect value 0xffffffffffffffff

uint64 ui64b = 4294967296; FnTestUint64(ui64b); // C++ debugger will show correct value 0x0000000100000000

 

0xffffffffffffffff is -1 in int64 and 18446744073709551615 in uint64.

 

It seems that compiler incorrectly converts 4294967295 to int as -1, then converts this -1 to int64, then converts this big -1 (represented as 0xffffffffffffffff) to uint64

 

Maybe it is a well-known bug? Is it possible to fix it?

Thank you.

Edited by Apmyp
0

Share this post


Link to post
Share on other sites

I assume this is in C++. As far as I know, you must append "ull" to mark it as a unsigned long long int constant, otherwise, it is interpreted as an int. I think your particular compiler makes the assumption that this should be a 64bit value, and will treat it correctly for you. In GCC, you'll get the (in my opinion) correct warning "integer constant is too large for '<type>' type", where in your case, <type> would be int because you're using an int constant with a value outside the range representable by an int.

0

Share this post


Link to post
Share on other sites
Ectara, it is not C++ because I am looked to the memory at pointer gived from GetArgAddress (when investigated an original error).. so there is 0xffffffffffffffff in memory prepared by AngelCode engine.
 
Also, I declared application function as FnTestUint64(asQWORD ui64b) and there is nothing misunderstandable for compiler.
0

Share this post


Link to post
Share on other sites

Ah, now I see which subforum this is. My apologies, I came here through the sidebar on the main forum page, which doesn't show the name of the subforum. I just guessed from the mention of the C++ debugger.

0

Share this post


Link to post
Share on other sites

Hello, Andreas.

 

I've encountered a similar problem with uint64 values. It seems to me that the value 9223372036854775808 is not processed correctly. However, everything is fine with the values 9223372036854775807 and 9223372036854775809. For 9223372036854775808 I just get 0 but according to http://www.angelcode.com/angelscript/sdk/docs/manual/doc_datatypes_primitives.html  type uint64 supports values up to 18,446,744,073,709,551,615

 

Regards,

AlexeyO

0

Share this post


Link to post
Share on other sites

I didn't get any problems with the following tests:

r = ExecuteString(engine, "uint64 ui64 = 9223372036854775808; assert( ui64 == 0x8000000000000000 ); ");
if( r != asEXECUTION_FINISHED )
   TEST_FAILED;
 

r = ExecuteString(engine, "int64 i64 = 9223372036854775808; assert( uint64(i64) == 0x8000000000000000 ); ");
if( r != asEXECUTION_FINISHED )
   TEST_FAILED;

Can you give an example script where you see the value become 0?

Edited by Andreas Jonsson
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