воскресенье, 28 сентября 2014 г.

Parallax Mapping Agal2 update.

Very quick post. Just recompiled my parallax experiment. Previously it worked with FP11.6 beta only, which is very hard to find this days. Now you can see the demo if you have FP15.
Parallax Mapping Agal2 and  one more

10 комментариев:

  1. Hi, love your blog, there is always something interesting to see, I just wanted to ask for your help on the topic of AGAL2. I´ve seen from your videos that you use FlashDevelop, I use it too, but I can´t seem to get it to work with AGAL2, I get the "opcode requires version 2" error even if I am using FP15 with the debugger. So, I wanted to know if you can help me to set up FlashDevelop for using AGAL2. Thanks, have a good day.

    ОтветитьУдалить
    Ответы
    1. Well, that means that you need specify number 2 in assemble() method. The last assembler version can be found here https://github.com/adobe-flash/graphicscorelib/tree/master/src/com/adobe/utils/extended.

      Удалить
  2. Thanks for the super fast response, I tried what you recommended but now I get this: "Error #3725: The requested AGAL version (2) is not valid under the Context3D profile. For example AGAL version 2 requires standard profile". I was trying it under the "Context3DProfile.BASELINE_EXTENDED", but it doesn´t work, and STANDARD is not an option. I think I know what´s the problem, in my project properties I can only get as high as FP11.8, I´ve tried to copy the "playerglobal15_0" so it can be used by the SDK, but still I can´t choose 15.0 as an option. Maybe the problem is the version of FlashDevelop (I´m using 4.4.3). If you have another recommendation it will be very appreaciated.

    ОтветитьУдалить
  3. Yes, I upgraded to FlashDevelop 4.6.4.1 which gave me the posibility to use FP14.0 by default. Now I can choose "Context3DProfile.STANDARD". I tried one of the opcodes in the new assembler (ddy specifically) and the program ran without any problems. Sorry a posted so much. Again, thanks for responding. Cheers.

    ОтветитьУдалить
  4. If you want to use the lastest fp version with fd, you need to specify swf version in additional compiler options, for example for fp 15 you need:
    -swf-version=26
    -target-player=15

    ОтветитьУдалить
  5. Cool, I didn´t know you could set it up manually like that. It´s interesting because if I set it to "-target-player=15" it tries to look for 15.1 :) , I just have to be more specific. Thanks for the tip!

    ОтветитьУдалить
  6. Hi, I´ve encountered an issue that I think you can help me with, maybe it has happened to you in the past. I have been working on a game for the past few months and I decided to try it on browser so I made a simple web page and upload it there. I tried different browsers, with Firefox and internet explorer it runs great, with a rock solid frame rate, which made me very happy, but when I tried Chrome and Opera it was a different story, the frame rate is very choppy and something more strange happens which I might describe as a glitch on the fragment shader, from what I´m seeing it´s a problem with conditional statements, maybe, I´m really not that sure. Something very important is that on Firefox and internet explorer it runs DirectX9 (Standard) and on Chrome and Opera it uses OpenGL (Standard), I think that if maybe I could default to use DirectX I could (in a way) solve that problem, but I haven´t found a way to do it, or maybe there is another (better) solution, that´s why I´m asking you for help. Thanks in advance for any advice.

    ОтветитьУдалить
    Ответы
    1. Hi, unfortunately it's impossible to force usage of graphics API (directx or opengl). Everything depends on browser and platform. I know that pepper chrome behaved really bad and unfortunately you can't do anything with that - just provide an information to your users to use different browser.

      Удалить
  7. Этот комментарий был удален автором.

    ОтветитьУдалить
  8. Thanks, that helps me a lot. Have a nice day (or night).

    ОтветитьУдалить