ENIGMA Development Environment

I noticed that, that's why I said to set the depth to 2000; it didn't make any difference when the projection was set in the step event. I've just tested moving the projection settings to the end of screen_redraw and it makes it work, I'm not sure if there will be any ramifications to doing that or not.

Models should but working, reup the file it's messed.

I think after the parser is done it is near ready to ship as a proper release, go back to 64digits and places and see what they make of it.

I still think a couple of important things still need to be done though for ENIGMA to be properly accepted:
- parenting events really needs to be added (been asking for that for ages)
- the game settings need to be added (esp constants, and include files would be rather useful)
- polygon collisions is obv important and collision functions to match
- the windows widget system needs to be working as well

Check the console after compiling at it will give you the directory to the build location at the end, it will be in your user temp folder. Then just grab that and rename the extension .exe

You're supposed to be able to run 'build' from the ENIGMA menu but yeah that's never worked as far as I can remember.

Josh has suggested trying to run a game build on my system to see if it will run on yours. So if you could see if this please runs it would be useful:
https://www.box.com/files#/files/0/f/72770310/1/f_2666779757

Thanks.

Hmm unfortunately that makes it extremely difficult to debug since there is no error for us to go on. Can you just check to see if a completely blank new game does the same thing as well please?

If so I think Josh needs to test things on newer Windows systems a little. The problem is no one in the dev team uses Windows 7 so incompatibilities with it are more likely to go unnoticed.

I suddenly thought of a way to do this, right after I switch methods for what I needed doing so I don't need it any more. It should have been obvious to me near the start as well .

If you use a quadratic bezier for the path instead, then alter the value of t for smooth paths so it runs against it linearly. I have tested the values in a spreadsheet which I wrote before and it works perfectly.

You have:  D = 2(1-t)t*Q + tt*R

Where D is the distance it should be moving linearly calculated, which in the script is the value of (position - ppi->position)*total_length. Q is the length of 2nd-path point to the 1st one and R is the length of the 3rd-path point to the 1st one. Then that can be rearranged using the quadratic formula to:

t = (-2Q + SQRT((4QQ + 4D(R – 2Q))) / (2(R – 2Q))     //You have to check for 2(R – 2Q) = 0 also, in which case set t to 0.5

Then just use that value for t with a regular quadratic bezier equation to calculate the x/y positions and it will work correctly linearly as well as curving correctly. But to be honest I really can't actually be fucked programming this, maybe in a month or something lol. I really don't need it any more myself so until maybe it's an issue for someone else I can't be bothered doing it.

Meh, I'm still looking at it. Not got anywhere though.