Graphics

 View Only
  • 1.  DataLinq material error when opening Xpression Package

    Posted 02-19-2020 21:42

    So.. I'm working with the same project on two different machines usually... One being a Graphite, the other being Designer at home. No problems exporting a package, then opening this at home, or the other way around.

    However, I have found this one thing that bugs me to no end... In the same folder as the Xpression project, I keep a DashBoard, a rather extensive DashBoard.. In that DashBoard, I use several file pickers to select a file, and then use that string to update a logo, or a player picture or what not. Now THAT part works just fine... If the parameter points to

    images/players/player1.png

    DataLinq can get that value, and then use it to change a material texture, all good!
    However, if I then take this project, export it as a package, take it home, and unpack it...
    All of those materials that rely on DataLinq, suddenly reports an error!
    Now, it will not find the material, and will throw an error for each of those with the description:

    "File not found: D:\folder\folder\folder\images\images/players/player1.png"

    (the \folder\folder\folder part substituted for the actual drive and folder structure on the machine).
    So for some reason, now it suddenly adds another "images" to file structure... And I have to fix each and every one of them... And it's kinda getting a few too many!

    1. Anyone experienced something similar?
    2. Why does DashBoard return the file path with / while Xpression looks for \ ?


  • 2.  RE: DataLinq material error when opening Xpression Package

    Posted 02-19-2020 22:58

    Addition:

    However, if I use DashBoard to pick another image, then go back to the original, it works just fine...
    And changing the picture also removes the error message in Xpression.
    So, my hunch, something is wrong then opening an Xpression Package, and one of the materials have a DataLinq texture. For some reason, it adds the \Images onto the file path before then taking the value that was allready there from the DataLinq when the package was exported.

    So, might file this one in under bug?


    #XPression