Mako Reactor vs Source Engine

Posted: March 30, 2012 by Hannibal[SPA] (Rafuron) in Hannibal is mad!

Hi, as I tell you in the post before, the new version of Mako Reactor (ze_FFVII_Mako_Reactor_v5) crashes in many servers (but not all them : / ). Tomorrow friday 30 I will ask for all your cooperation to test two versions:

– The first one doesn’t use the ‘classname’ player for materias filtering (that thing could be in conflict with the Zombie Mode)

– The second one hasn’t area portals

I don’t have any clue, the crash logs are all them very weird; I got some information from a log that the last source engine function called by server was one about area portals (thats the reason of the second test version); and, the classname change is the only big weird thing I did for the new version v4 to v5.

If both versions crashes (I need 40-50 players), Mako Reactor will stay as it is, no more versions, just let the v5 for small servers, and v3_1 for big servers. It’s a fucking waste of time (sorry) working with a shit engine like Source Engine; ok, the editor is fucking awesome, but the limited tools, the crashing combos, the fucking shit of fucking buggy and slow compilation, flickering textures, small limits (vertex, planes, models, etc…), the repentine crash in the editor, the buggy/non working entities, the weak visualization in the editor … , all this is a pain for me and every crash version I feel how my mapping hobby is getting more and more boring/annoying, and the life is not for having boring and annoying hobbies.

Thats all, if that two versions fail; I will forget Mako Reactor forever; I’m going with Minas Tirith and Paranoid.

  1. Kaemon says:

    Ey, I just created a new category for this kind of news called “Hannibal is mad!”. I can see us using it again when he is working on fixes/updates on both Minas Tirith and Paranoid. XD

    If Mako still crashes on both those test and Hannibal had really enough with it, I may give it some more shoots myself to try to fix it, if I’m allowed. This way I could even add those last fixes that I wanted to include; like fixing the Hit-Box of those buildings that won’t allow you to come close.

    But yeah, having crash problems that seem to come from no-where and that aren’t explained by the logs is really not fun at all; and way too time consuming… And all that time is a complete waste of time if at the end you didn’t manage to fix the crash.

  2. Cookie says:

    he mad

  3. schmosalt says:

    I agree with you on the whole Source engine deal. Valve may be able to keep the engine graphically up to date via its modular nature but many under the hood areas have been seriously neglected. Heck, I doubt they’ve made any significant BSP changes since HL1. I can only hope that Valve sees issues like this in the modding community and decides to improve their under the hood components.

  4. Andrew says:

    Contact me if you need a server to test with, my guys will be happy to help!

  5. Cazador says:

    Where are u gonna test? metro server or pF? And at what time?^^

  6. Joris Ceoen says:

    Hahaha, that’s funnier than a rage quit x) Well, he’s pretty mad O.o

    On the sideshot, he’s right :S Source Engine has limits which are imo unresponsible for the year 2012…

  7. Joris Ceoen says:

    The only thing that should be changed are the freakin plane limits and brush entities. Crashes inside the code… Well yea only Valve really perfectly knows how to counter those.

  8. WaterHazard says:

    o.o Forget Mako forever?
    Holy shit ur kidding me..
    (Crosses Fingers) lets hope it works!

  9. Metro says:

    hannibal is busy man Waterhazard he dont got time fix this crashes in 1month cus of valves stupidy

  10. Joris Ceoen says:

    There are indeed better things to do than to waste time on other person their faults 🙂

    I don’t mind v._1 staying but there will be the neverending problem about materia spammers x)
    I haven’t been able to test v5 because I think they are all removed now since I could play. I’ll be able to play today but Idk on which servers they will be tested

  11. Cazador says:

    supreme elite still has v5 and it didn’t crash in a good few rounds the other day, as Legrem said

  12. Purpzz says:

    Dont put mako a side if it crashes 😮 just do another map and give it a little waiting time so u dont get annoyed in it, i know how it feels if u need to keep editing a map but hey, there are so many people who love the mako map and also the new changes are much better and fun to play so please dont give it up, its one of my favorit maps and it would be not so fun to see we all go back to a previous version just duo some crashes.

    If you start making a difficult ZE map, then u know things like this can happen, putting it a side is the easy way, just give it some waittime and do some other map in that while and in the meanwhile u dont get annoyed so hardly!

    Hannibal and Kaemon, DONT GIVE THIS MAP UP PLEASE!!! ❤

  13. Sabresrock16 says:

    Wow, v5t1 was fun on that rz server… didn’t crash at all! great work Hannibal!

  14. { V o_0 v @ N } says:

    So Hannibal,when a new version? 🙂

  15. Kaemon says:

    The first test went good (not a single crash) and we didn’t bother doing the second test. The main suspect of the crash issues was (unless we were really ultra-lucky and crash was still there but didn’t occur) the use of ClassName for filtering the materias.

    I don’t know when the new Mako Version will be out; but shoul be soon enough.
    Finally Hannibal decided to use the TargetName, currently used to keep track of the player-based materia-levels, to check if you are the owner of the materia instead. This means the materias will be still filtered and imposible to use (by mistake or not) by people that don’t own them.
    However, this also means that the current Materia Leveling will get removed. Instead, all materias will be “normal” during Normal difficulty; all materias will be “+” during Hard, and all materias will be “++” during Extremes.

    It loses some of the charm; but it also allows people that recently joined the game to pick a key-materia (like Heal on Extreme 2) without having to worry about screwing the team because having a low level on it.

    On a side note, Michelle’s ZE map “Destruction of Exorath” was also crashing randomly, and aparently had the same cause: using a ClassName to filter who was allowed to use the special weapon within the map.
    Also, we found and fixed some extra really minor glitches on Mako Reactor.

  16. Hek says:

    I’m looking for a LIKE button!

  17. Joris Ceoen says:

    Perfect! Personally, I never liked the ++ system, it was glitchy itself anyway. Sometimes people with ++ received + for no logical reason so I’m very happy it’s normal now 🙂 The most important is that you have found the problem! Targetname is nice indeed, but yea, the leveling has to be removed that way.

  18. Puni, Punisher, css_matt says:

    Shame, doesnt look like classname is a viable option then possibly?
    Luffaren also used it though and I havnt heard of him having any problems with it

  19. Kaemon says:

    Yeah, Luffaren and myself used it for Serpentis Temple, and I think he also used on Crazy Karts.
    However, both those maps are made to be played in MiniGame servers with normal CS:S settings; and also usually with fewer people.
    It could be ClassName conflicting with Zombie Mod itself, since it kinda has classes. Also, notice that the crashes were kinda weird and random; it wasn’t crashing 100% of the time that all materias were picked, or that Extreme 2 ended; it was more like a “Chance of conflicting make it crash”.

    Myself I would have prefered testing for 20-40 minutes more, and getting at least 10 extra people in the server; just to be completly sure… But it really looked (and was likely) that it was the ClassName causing the problem.

    Joris Ceoen, it wasn’t really glitch; but if two or more people were on top of the materia and the time it was picked, the trigger would filter all of them. Thats why sometimes you could level up without being the one picking the materia; or why sometimes 3 different messages of “Fire+” and “Fire++” upgrapes showed at the same time.
    And I’m not sure of people with ++ getting +, but the other way around was possible indeed.