Jump to content

What's next for UAK?


Josh
 Share

Ultra App Kit development  

32 members have voted

  1. 1. What next?

    • Mac / Linux support
      9
    • C# / Lua support
      7
    • Vulkan 2D graphics for games
      3
    • I don't care, just give me the 3D engine
      13


Recommended Posts

new script editor/better direct support for VS code
better shader workflow(getting lots of engine side bugs while working with shaders)
hair (alpha like leaves.shader but animated), outline shader for selecting things
terrain heightmap generator (from 1..n noise funcitons with custom arguments)
 

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...
5 minutes ago, Lethal Raptor Games said:

I've never used Linux before, but there seems to be a lot of people there who won't even give it a chance.

Some GTK devs hang out there I think. :D

Yeah, you have to basically force people to try anything new by giving them something they can't say no to. I'm not committed to capturing the Linux GUI market but when the 3D engine comes out I'm expecting death threats. The amount of hate you receive is actually a pretty good indication of how successful you are at any given moment. When LE3 was released I had people calling my phone in the middle of the night.

  • Haha 1

My job is to make tools you love, with the features you want, and performance you can't live without.

Link to comment
Share on other sites

The fact there is any discussion at all is a good sign. I post very rarely on Twitter or Facebook anymore, but it looks like Reddit is actually a good place for me to post and have it actually be seen.

My job is to make tools you love, with the features you want, and performance you can't live without.

Link to comment
Share on other sites

As much as I support Linux support, that thread right there just shows you that the average Linux developer isn't interested unless it's free/open source. 

I think the real attraction of this is for developers on Windows who can be certain they are one compile away from a linux version of their software.

You also have been battling with marketing paid software to a generation that don't remember big box stores for years and got everything for free. The reaction you got on reddit made sense with you asking money for proprietary software to a cult about Open Software.

Games for some reason are the exception for some reason. Hopefully when the engine ships, you'll get better feedback.

  • Thanks 1

Cyclone - Ultra Game System - Component PreprocessorTex2TGA - Darkness Awaits Template (Leadwerks)

If you like my work, consider supporting me on Patreon!

Link to comment
Share on other sites

Yeah, we still have no idea what will happen once the store page on Steam starts listing Steam support. I would say that is going to probably be the moment of truth that reveals a lot.

https://steamcommunity.com/app/1512210/eventcomments/3093389895549898357?snr=1_2108_9__2107#c3093389895553059119

My job is to make tools you love, with the features you want, and performance you can't live without.

Link to comment
Share on other sites

  • 2 weeks later...

I have some upcoming API changes planned. These are small things that I don't think will affect anyone:

  • SeedRandom renamed to Seed()
  • Thread::Resume and Thread::Pause are gone, since these don't work with POSIX threads
  • Added Thread::Start().
  • Added PATH_DOWNLOADS and removed all other paths except DESKTOP, APPDATA, and DOCUMENTS.
  • CreateThread() will start the thread immediately by default.
  • MOUSEREPEAT event and Widget::MouseRepeat are gone, since the slider it the only widget that uses this. I programmed the desired behavior into the Slider class which leaves the window class more lightweight.
  • The CursorBlink() stuff is moved out of the Interface class and just contained in the textfield class, since this is the only class that uses it.
  • Window::Close() will go what, use EmitEvent(Event(EVENT_QUIT)) instead.
  • Adding Display::ClientArea() which returns an iVec4 defining the usable area inside the screen, minus any bars the OS uses.
  • Adding Widget::SetFontBold()

My job is to make tools you love, with the features you want, and performance you can't live without.

Link to comment
Share on other sites

6 hours ago, Josh said:

Window::Close() will go what, use EmitEvent(Event(EVENT_QUIT)) instead.

A little curious about this change. Will this complicate future 3D examples down the road? Are you also making this change for thread syncing?

Cyclone - Ultra Game System - Component PreprocessorTex2TGA - Darkness Awaits Template (Leadwerks)

If you like my work, consider supporting me on Patreon!

Link to comment
Share on other sites

There is no such action as programmatically closing a window. There is no HitMouse() command either because it doesn't make sense.

Emitting a general QUIT event does not require a window. It's just a signal that says "I'm done". You have to have handling of this event anyways on Mac to check if the user has quit the app from the dock or menu.

My job is to make tools you love, with the features you want, and performance you can't live without.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...