This is the most exciting release in a long time! Thanks for all of the hard work!

Thanks contributors for the half decade of commits that went into this release! Hopefully some of the modernization in 1.3 will make 1.4 more fun to work on.

This is awesome! It’s great to bring another major platform into the community! I’ve done a bunch of work on the iOS port, and a recurring problem is that players can’t include their Android friends in multiplayer matches. Net play is super fun when everyone is in the same room together, and now vir...

treellama wrote:Large is 26.5 inches from collar to bottom. I've washed it a few times. It's 100% cotton

I had a similar experience. If they are still selling these, get a size larger than you would normally wear!

If this studio has solved the free-locomotion problem, it would be considered a major breakthrough in VR. Maybe they’ve done it (and that would be awesome), but I’d wait for more player feedback before assuming they’re going to be successful. If you want a new scenario to play, Mararthon: Yuge just ...

VR support is already available in Unity, and it wouldn’t be impossible to add it to AlephOne either. The real issue is that games with a lot of independent camera movement (such as an FPS) don’t work well in VR.

The games are all live on the App Store, so there is no need for pre-release testing right now.

The most recent updates add support for MFi, Xbox One, and PS4 controllers. You should try it out, if you haven’t already!

This is a crude sprite emboss effect. It mostly works as you would expect; you can see the glare on objects shift as the player pans left/right. The only major issue is that the effect is sometimes flipped horizontally or vertically, depending on how the sprite was transformed for display (I’m not s...

Do those issues with mouse input happen on all platforms? I have not noticed input glitches on MacOS, except for sometimes not being able to skip chapter screens; but nothing that affects gameplay.

You know, I think I've seen similar problems like that before (though not often). If that issue shows up in the software renderer also, it could be some edge case where render tree drawing order is not perfect; say if a sprite is drawn and then other polygon walls are drawn over the top of it. If th...

What is the easiest way to demonstrate that issue? It could be something simple, like a sprite is getting closer than zNear.

Maybe it's too soon to ask this question if you haven't decided on a solution for sure, but for scenarios that include custom shaders, is that something that will need to be changed for future versions of A1? I would expect all of the shaders will need some adjustment. It’s my understanding though ...

This is awesome! I never thought I would ever be able to play this game without a lot of inconvenience, but here it is. Thanks for porting it to AO!

People ask this pretty often... I think an Android version would be great, but I’m not in a position to start a project like that right now. However, I would contribute if someone else were to take the initiative on it.

A few other people have asked about controller support, so it’s on the to-do list. I will probably need to buy one myself in order to develop the feature - I don’t personally know anyone who has a mobile controller.

Hope you are having fun!

Where were you during the beta test? :) Anyway, the trigger buttons are gone because it was the single most complained about feature in the old version. You couldn’t fire and aim at the same time (which was sort of a problem) nor could you fire both modes simultaneously with one thumb. I think the t...

Not yet, but it’s on the wish list. The ES2/3 renderer (I’m trying to keep them interchangeable) is about 90% done. When it’s ready, I will probably just release it as-is. If by some miracle we can actually include MoltenGL for the project, it will bring down power draw and open up some of the more ...

and I would’ve done it, too... except that Vulkan is the graphics API equivalent of the ALS Challenge. Sure, it’s unifying efforts to solve an important problem, but it’s about as fun as taking an ice bucket to the face.

Fortunately it’s just a donate button now... But yeah, I was originally opposed to that too - If only because StoreKit integration just complicates things. I changed my mind though when I saw that the MoltenGL license was going to cost $1500 annually.

Hopefully this won’t put too much more load on the meat server. Between the convenience of mobile, and the meatspy bot, I expect we can get even more people joining online games. ‪https://itunes.apple.com/us/app/marathon-1/id419805412‬ ‪https://itunes.apple.com/us/app/marathon-2-durandal/id421697209...

The various OpenGL implementations aren't exactly known for their consistency...

In some (or all?) of the shaders, the problem seems to be that the main() function ends with a '};' instead of '}'. If you remove that last semicolon, they should compile fine on Apple's OGL.

GLSL is strict about data types. Try using 12.0 instead of 12.

I think Aleph One should report shader errors when they occur, instead of exiting.

Can you try this 5-line patch? I've not seen your particular issue, but I suspect it's related.
https://github.com/Aleph-One-Marathon/alephone/pull/137

ravenshining wrote:Building the latest from git I get some weird HUD issues when switching weapons..
system: debian 8 amd64 w/NVIDIA Quadro FX 1600M

I’d be interested in contributing to an Android port, but I’m not in a position to initiate a project like that myself. I’ve not heard of any attempts to run the engine on Android yet.

I think you’re right; it’s more or less an issue with all digital distribution systems. Hopefully as competition between platforms increases, they become more open. For now I’m doing my best to make this a good representation of the project. I expect that the community will let me know if I’ve slipp...