Jump to content
  • Advertisement
Sign in to follow this  
pifor106

u8/s8/u16/s16 not working on Xbo360 with native calling conventions ?

This topic is 2945 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi,

I'm in the process of running my learning/unit tests on all platforms that I have to support right now and I've stumble upon a bug/problem with the Xbox360.

It seems that uint8/int8, uint16/int16 are not supported. The thing is that all input parameters of this type are passed 0 when going to the C++ side.

If I compile the same code using AS_MAX_PORTABILITY, I have no errors.

I looked rapidly at the code and it seems that the Xenon native implementation only supports integers/floats/doubles and booleans. Am I correct ?

Share this post


Link to post
Share on other sites
Advertisement
This is new to me. It could be a bug in the as_callfunc_xenon.cpp code, possible due to big-endian/little-endian differences.

Unfortunately I don't have any way of testing this myself so I'd appreciate any help I can get from this.

Share this post


Link to post
Share on other sites
We only used ints and floats in our script code on Xbox 360, so we never came across this issue.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!