Page 5 of 5 FirstFirst ... 345
Results 41 to 45 of 45
  1. #41
    EmuTalk Member
    Join Date
    Dec 2008
    Posts
    137
    Mentioned
    0 Post(s)
    Hey noone says that Gonetz completly stops working on GLideN64
    What the hell are you?

    30.11.13 R.I.P Paul Walker

  2. #42
    Zelda CelShade Producer
    Join Date
    Feb 2004
    Posts
    1,025
    Mentioned
    11 Post(s)
    Great work for this release : Bloom and New HD Pack , with AA 8x





    but too bad that this version has big bugs with majora's mask like no eyes or no text on main intro...
    Strange this bug appear only with the HD pack texture option enable. But work fine with rice plugin...

    Last edited by Djipi; April 16th, 2015 at 10:14.

  3. #43
    EmuTalk Member
    Join Date
    Dec 2008
    Posts
    137
    Mentioned
    0 Post(s)
    Report it to Gonetz
    What the hell are you?

    30.11.13 R.I.P Paul Walker

  4. #44
    Plugin Developer (GlideN64) Gonetz's Avatar
    Join Date
    May 2002
    Location
    Siberia, Russia
    Posts
    407
    Mentioned
    6 Post(s)
    Development is not finished. It stepped in a new phase - Android port. Lots of work expected here.
    Source code is not released yet. I need to clean it first. That is the purpose of "Early release" - supporters already can play with final product while I can silently move to next tasks.

    As for 125 remaining issues: may be somebody with keen eye will just look at the sources and noticed wrong places right away. There were several places in legacy code, which I did not touch because they were in functions used by any game. I thought that some part of code is for reason, but actually it was a crutch to avoid some particular problem.
    Sorry for terrible English, my native language is C++

  5. #45
    Surreal64 Nut weinerschnitzel's Avatar
    Join Date
    Jan 2011
    Posts
    73
    Mentioned
    0 Post(s)
    Quote Originally Posted by Gonetz View Post
    As for 125 remaining issues: may be somebody with keen eye will just look at the sources and noticed wrong places right away. There were several places in legacy code, which I did not touch because they were in functions used by any game. I thought that some part of code is for reason, but actually it was a crutch to avoid some particular problem.
    I asked before about detailed comments in the source code, but I would like to reiterate how useful it would be to have:
    1) Questionable legacy code noted and explained (purpose and problems)
    2) Comments on your changes (which part of code affects which games and which components, what regressions to look for when modifying)



    You know an incredible amount of what to look for and how GFX issues are related between games. Some of that is learned in the issue tracker, but any more of this knowledge that can be "spoon-fed" to us will make it a lot easier to pick up.

Page 5 of 5 FirstFirst ... 345

Tags for this Thread

Posting Permissions

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