Jump to content

matteoluigi

Member
  • Posts

    460
  • Joined

  • Last visited

Posts posted by matteoluigi

  1. On 1/9/2023 at 6:53 PM, Tolu said:

    A docker image is not architecture-specific. However, you have to install the right Docker Desktop for your machine (Intel or Arm) based on your OS and Machine.

     

    i did install the right docker version for my raspberry pi machine. Portainer for example works perfectly. So it must be the image which only works in a x86/x64 environment.

    and, which makes me wonder is, that on hub.docker.com there is written to every image for which architecture it is appropriate.

  2. @JoshP now I tried to run ps server on a raspberry pi

    however it doesn't work, in portainer there's written, that the docker image doesn't run... 😉

     

    it's a raspberry pi 3

    Quote

    PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"

    NAME="Raspbian GNU/Linux"

    VERSION_ID="11"

    VERSION="11 (bullseye)"

    VERSION_CODENAME=bullseye

    ID=raspbian

    ID_LIKE=debian

    HOME_URL="http://www.raspbian.org/"

    SUPPORT_URL="http://www.raspbian.org/RaspbianForums"

    BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

    ~

     

  3. Hi,

     

    I really like the new 2023 Homescreen. However it doesn't have enoght features, so I don't use it actually.

    Afaik it's supposed to be the first dashboard you get, when you start Vectorworks. However, then there is a crucial features missing!

    I can't access a server based project file from the Homescreen.

    That feature is totally missing.

     

    Don't tell me, that:

    - I first have to open a new document in order to be able, to open the server-project-file window, that's neither intuitive nor logic.

    - I can open every vwxw-file I already opened before. However I sometimes want to open the vwxp file in order to create a new vwxw file... that doesn't work from the homescreen.

     

    That's a pity.    

    Now I don't use the homescreen any more, I shut it down in macOS.

    • Like 1
  4. Well, that's no 100% issue, however it happens quite easily, that an IFC-export happens to come out without file extension!!!

    After that, solibri... won't find the ifc-file and the wanted ifc file doesn't get overwritten...

    (tested on mac)

     

     

    Mainly it happens when:

    1) click on "export ifc"

     

    2) -> OK

     

    3) click on an existing ifc file in order to overwrite it

     

    4) the ".ifc" file extension disappears and won't be appended any more (unfortunately the more stress you have during your work, the more things like that do happen)

     

    5) then you wonder, why clicking on "refresh model" in solibri doesn't show all modifications you did before...

     

    Just simple said, the export should always look wether there is .ifc appended to the filename or not. With vwx-files that problem doesn't exist. It's mainly with ifc files.

    (with the dwg-export for example that problem doesn't exist)

    • Like 1
  5. 26 minutes ago, Mihail Rizov said:

    save the document after IFC Export.

    or save and commit including document settings...
    We also created a new project file in order to get that settings in the vwxp-file.

     

    damn, I guess, that those settings don't survice a Project Sharing commit...

  6. 7 minutes ago, Mihail Rizov said:

    open IFC Export, setup all and press Save Settings

    hm, ok. When I start scripting, I want to control as much as possible from the script. so, imo there should be way more options, including the option of using the saved settings, of course, too. (like IFC_ExportNoUI(path) with no options -> saved settings)

  7. Hi,

     

    somehow the error messages in the script editor are a bit misleading. Sometimes it happens to me, that the mistake I made in my code are not in the line the error has been found by the ...compiler?... but in the line before.

     

    path = (vs.Concat('/Users/matteoneustadt/Desktop/HBK2/',current_date)
    ok = vs.IFC_ExportNoUI(path)

    for example, there's missing a bracket in the "path" command.

    However I get told, that the error is in the line of the "Ifc_ExportNoUI..." line.

     

    Maybe there's a logical reason, however not a user friendly reason ;-).

×
×
  • Create New...