Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


axefrog

Member Since 08 Apr 2011
Offline Last Active Mar 29 2015 04:31 AM

Posts I've Made

In Topic: C#

24 March 2015 - 12:19 AM

2) c# basically is for microsoft and only works for microsoft platforms.


Man, I wish people would stop spouting this outdated nonsense. C# is an open standard, and as others have said, Mono/Xamarin have been around for ages now and they let you target all platforms. Not only that, but Microsoft have now fully open-sourced the next version of .Net and upon its full release within the next few months, it will be able to target multiple platforms including Windows, Mac and Linux.

C# all the things! Yay!

In Topic: Question for UE4 and Unity 4/5 experts, regarding capabilities

23 March 2015 - 11:48 PM

I know it's a bit older, but it says that better native scene management and streaming are coming in an update to 5.
 
http://blogs.unity3d.com/2014/08/04/multi-scene-editing/
 
I can't speak too much about UE, but you could also look at some open world style games made with each engine for comparison.


Thanks for the link. For what it's worth, my latest blog post provides some context for where I'm going with this.

In Topic: BGFX Renderer Compiling Woes

08 March 2015 - 06:05 PM

Here's what your bx folder should look like:

03.09.2015-10.03.png

If it doesn't look like that, you've Done It Wrong™. Just delete the folder and clone it again.

In Topic: BGFX Renderer Compiling Woes

05 March 2015 - 10:17 PM

Have you got the bx project cloned beside bgfx? your directory structure should look like this:

/whatever/bx
/whatever/bgfx

You then go into bgfx and run make from there.

In Topic: Concept for an input library - thoughts?

05 March 2015 - 04:13 AM

Still, I wouldn't use a parser, but that's just me.


To be honest, I understand if it's out of fear of missing errors at compile time, but if it's performance-related, we're talking an algorithm that's basically going to be O(N), and given that the parsing will in almost all cases be less than 100 characters, and in many cases less than 10, the performance aspect is pretty much completely irrelevant. Not sure if you were concerned about that though. The win in terms of code readability, I think, is greater than the loss of compile-time input sequence type-checking. Just my opinion though.

PARTNERS