Results 1 to 6 of 6

Thread: Opengl for srl6

  1. #1
    Join Date
    May 2013
    Posts
    52
    Mentioned
    0 Post(s)
    Quoted
    33 Post(s)

    Default Opengl for srl6

    This is post is directed to @Brandon and all the developpers of the OpenGL plugin. Is there an estimated time when OpenGL can be used?
    ty for your work :P

  2. #2
    Join Date
    Feb 2011
    Location
    The Future.
    Posts
    5,600
    Mentioned
    396 Post(s)
    Quoted
    1598 Post(s)

    Default

    Quote Originally Posted by gaspola View Post
    This is post is directed to @Brandon and all the developpers of the OpenGL plugin. Is there an estimated time when OpenGL can be used?
    ty for your work :P
    The answer is: Never. Here's why:

    There are TWO plugins: One for colours only and another that has colours and hooks.

    SRL-6 uses the OpenGL colour only plugin but it will never use the plugin with the hooks and colours.

    P.S. You asked this over here: http://villavu.com/forum/showthread.php?t=106023 and I answered it there as well.. The devs answered there.
    I am Ggzz..
    Hackintosher

  3. #3
    Join Date
    Sep 2012
    Location
    Here.
    Posts
    2,007
    Mentioned
    88 Post(s)
    Quoted
    1014 Post(s)

    Default

    TO phrase it in [probably?] the way desired... SRL6 specifically will never work with OGL hook based coding. OGL hook based coding DOES work, when installed on a separate SIMBA instance from SRL6.

    SRL6 + hooks at same time = never.
    SRL6 = works now.
    hooks = works now.

  4. #4
    Join Date
    Nov 2011
    Location
    England
    Posts
    3,072
    Mentioned
    296 Post(s)
    Quoted
    1094 Post(s)

    Default

    @Brandon

    Ever thought of releasing a way for people to use your plugin without needing your include (there is nothing wrong with it) but it could be used something like sps or object DTM is, ((a plugin(obj dtm a extension), and a single "include" file).

    So it would pretty much be:

    Simba Code:
    {$define smart}
    {$i srl-6/srl.simba}
    {$i glxcore.simba}

    begin
      setupSRL();
      SetupGLX(__smartCurrentTarget, 1000, 2000); // I dont even know if this even possible nor if it even takes amart pid/target

      tabBackpack.open();
      glx_getmodel(some params);
    end.

    I don't even know if it's possible but it might be a nice alternative for people who just want the "core" stuff for finding mainscreen objects etc.

    Again if it's not possible dont worry or if you want people to use your include that's fine.

  5. #5
    Join Date
    Feb 2011
    Location
    The Future.
    Posts
    5,600
    Mentioned
    396 Post(s)
    Quoted
    1598 Post(s)

    Default

    Quote Originally Posted by Olly View Post
    @Brandon

    Ever thought of releasing a way for people to use your plugin without needing your include (there is nothing wrong with it) but it could be used something like sps or object DTM is, ((a plugin(obj dtm a extension), and a single "include" file).
    This is NOT a rant but..

    I plan to let the include die really.. OP can use SRL-6. I'm the only maintainer for that include and I'm being asked a lot lately. Removing parts of it in favour of colour because it makes things too easy.. I'd rather let it die before I do something like that.

    Not 100% sure why I have to be the one to do compatibility when it was built long before SRL-6. I doubt I want to make an extension and a single file include. It's far too big and a lot of work. That's like changing the reflection include into an extension in favour of colour.. It is asking a lot.. It is open source though so it should not be a problem for anyone at all. They just have to know Lape to make changes.

    However, I did include compatibility and it sucked.. So many IFDEF's everywhere.. It's like a patch.. So many changes for compatibility: https://github.com/Brandon-T/SRL-GLX <-- Latest commit.


    Even with the changes, I still don't use that include. I use the one without SRL-6 compatibility. Having to remove all of Smart, and almost all of the graphics and everything else to use SRL-6's is pretty difficult for me to personally accept. However, the public include has the options for that. If OP needs compatibility, then he will need to {$DEFINE SRLCompatibility} at the top of his script. He will still need to use the plugin with hooks though.

    Yeah there's a setup function just like that one: https://github.com/Brandon-T/SRL-GLX...er/Setup.simba

    Still.. Not sure that I want to maintain an include that no one uses except demise and myself.. From a dev point of view, it doesn't make much sense. I will be maintaining the plugins though..

    It will become like the OSR-Reflection include eventually.. It sounds harsh but everyone was working on OSR-Reflection but the second they were asked to "remove" some parts of it and only include the basics/essentials for walking and other things, it died. Only the a few maintains it now with some hooks provided by n3ss3s.
    Last edited by Brandon; 10-11-2013 at 10:16 PM.
    I am Ggzz..
    Hackintosher

  6. #6
    Join Date
    Apr 2012
    Posts
    157
    Mentioned
    10 Post(s)
    Quoted
    57 Post(s)

    Default

    Quote Originally Posted by Brandon View Post
    This is NOT a rant but..

    I plan to let the include die really.. OP can use SRL-6. I'm the only maintainer for that include and I'm being asked a lot lately. Removing parts of it in favour of colour because it makes things too easy.. I'd rather let it die before I do something like that.

    Not 100% sure why I have to be the one to do compatibility when it was built long before SRL-6. I doubt I want to make an extension and a single file include. It's far too big and a lot of work. That's like changing the reflection include into an extension in favour of colour.. It is asking a lot.. It is open source though so it should not be a problem for anyone at all. They just have to know Lape to make changes.

    However, I did include compatibility and it sucked.. So many IFDEF's everywhere.. It's like a patch.. So many changes for compatibility: https://github.com/Brandon-T/SRL-GLX <-- Latest commit.


    Even with the changes, I still don't use that include. I use the one without SRL-6 compatibility. Having to remove all of Smart, and almost all of the graphics and everything else to use SRL-6's is pretty difficult for me to personally accept. However, the public include has the options for that. If OP needs compatibility, then he will need to {$DEFINE SRLCompatibility} at the top of his script. He will still need to use the plugin with hooks though.

    Yeah there's a setup function just like that one: https://github.com/Brandon-T/SRL-GLX...er/Setup.simba

    Still.. Not sure that I want to maintain an include that no one uses except demise and myself.. From a dev point of view, it doesn't make much sense. I will be maintaining the plugins though..

    It will become like the OSR-Reflection include eventually.. It sounds harsh but everyone was working on OSR-Reflection but the second they were asked to "remove" some parts of it and only include the basics/essentials for walking and other things, it died. Only the a few maintains it now with some hooks provided by n3ss3s.
    Hey Brandon,

    You may not get it from many people, and you may not want the includes to be together. Ultimately that is your decision, as it is your plugin. But I want to thank you very much for all the help you provided me with the plugin since I started using it.

    Without your help I honestly would not have been able to get it working, and I am at that point now, where I do have it working well.

    So uhh, thank you again You have a right to rant.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •