Results 1 to 5 of 5

Thread: Some .fx aren't output in DAE.(3dsMAX)

  1. #1
    Junior Member
    Join Date
    Feb 2006
    Location
    Tokyo Japan
    Posts
    5

    Some .fx aren't output in DAE.(3dsMAX)

    Hello,

    There are some .fx files which aren't output in the <library_effects>.
    You can confirm this by using the '3dsMax8\maps\fx\blend_dxsas.fx'.
    (This .fx file is distributed with the MAX.)
    In fact, One of my .fx file isn't output, either.

    Why isn't this .fx file output ?

    Thanks

  2. #2
    Senior Member
    Join Date
    Aug 2005
    Location
    California
    Posts
    165
    I am not a developer of the 3dsmax plugin but I do have an idea of whats going on.

    COLLADA does not have a profile for hlsl. so the plugin probably just drops the .fx files when it exports.

    There are plans for a hlsl profile in the future.

    -Andy

  3. #3

    Re: Some .fx aren't output in DAE.(3dsMAX)

    Quote Originally Posted by Nagaya
    Hello,

    There are some .fx files which aren't output in the <library_effects>.
    You can confirm this by using the '3dsMax8\maps\fx\blend_dxsas.fx'.
    (This .fx file is distributed with the MAX.)
    In fact, One of my .fx file isn't output, either.

    Why isn't this .fx file output ?

    Thanks
    Hi,
    Check that the DirectX9 shader is pointing to the correct location of your .fx file. If Max can't find it then the exporter will fail to output it.
    Max will not tell you when you open the scene that the .fx file can't be found!

    Kev

  4. #4
    Senior Member
    Join Date
    Apr 2005
    Location
    Feeling Software, Montreal, Quebec
    Posts
    111
    Unfortunately, the HLSL that you wrote isn't accepted by the ASHLI parser used within IGame/3DXI. That's the main reason your .FX files won't export.

    I'm not sure if this will work on release versions of the plug-in, but since we all use the same version of the IGame plug-in, it may be worth a try: Attach a debugger unto 3dsMax. Export your mesh that uses the DX9 material that doesn't export correctly. Check in the Output->Debug window for more information. If ASHLI complained, it should be there.

    I have personally verified quite a few of the sample HLSL effects given with 3dsMax and the main issue is often case-sensitivity and over-definitions of terms like "sampler2D" [should be "sampler"].

    Sincerely,
    Guillaume Laforte
    Feeling Software Inc
    http://www.feelingsoftware.com

  5. #5
    Junior Member
    Join Date
    Feb 2006
    Location
    Tokyo Japan
    Posts
    5
    Quote Originally Posted by glaforte
    Check in the Output->Debug window for more information. If ASHLI complained, it should be there.
    Thank you for very useful advice.
    I could observe the error message in the debugging window.
    The message is useful because a line number with the problem is indicated.

    In blend_dxsas.fx case,
    (NG)
    Texture TextureTop
    < ...

    (OK)
    texture TextureTop
    < ...

    In my case, it was a cause that there was no input in the pixel shader.
    ex)
    struct PIN
    {
    };

    float4 pmain(PIN i) : COLOR
    { ...

    Now, I could be made to output a my .fx.
    Thanks

Posting Permissions

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