Giter Site home page Giter Site logo

autodesk / synthesis Goto Github PK

View Code? Open in Web Editor NEW
149.0 17.0 50.0 479.81 MB

A Robotics Simulator for Autodesk Fusion CAD Designs

Home Page: http://synthesis.autodesk.com/

License: Apache License 2.0

C# 60.23% NSIS 0.30% HTML 0.08% Shell 0.67% Batchfile 0.15% ShaderLab 2.26% HLSL 0.38% Rust 0.19% Makefile 0.03% C 0.07% Java 0.09% Python 6.71% PowerShell 0.05% CMake 0.37% C++ 8.32% Dockerfile 0.14% JavaScript 13.70% EJS 0.01% TypeScript 6.22% CSS 0.03%
robot-simulator inventor frc autodesk autodesk-fusion360 first-robotics-competition fusion360

synthesis's Introduction

Synthesis: An Autodesk Technology Synthesis: An Autodesk Technology


Engine API Clang Format Black Format

Synthesis is a robotics simulator designed by and for FIRST robotics students to help teams design, strategize, test and practice. Teams have the ability to import their own robots and fields using our Fusion 360 Exporter or use the pre-packaged ones that come included with every release of Synthesis.

For more information on the product itself or the team, visit http://synthesis.autodesk.com.

Goals

Synthesis is built with a direct focus on the FIRST community. Every single one of our developers is a FIRST student. We've also made the project completely open source in order to better involve the community. This way contributors can help make Synthesis better or modify Synthesis to better suit their team’s needs.

Here are some of our primary goals for Synthesis:

  • Ease of Use: It's important for us that Synthesis is out of the box ready for teams to use. We want to make sure that teams can get up and running with Synthesis as quickly as possible. To that end, every release of Synthesis comes pre-packaged with a variety of robots and fields; in addition to the ability to export and import your own.
  • Testing Robot Designs: Synthesis is designed to be a tool for teams to quickly test their robot designs in a semi-realistic environment. Are you a builder who wants to use some crazy virtual four-bar linkage and your team says it's a waste of time? Well now you can prove them wrong by testing it in Synthesis!
  • Exploring the Field Environment: Every year on kickoff, for both FTC and FRC FIRST competitions, Synthesis has a new release with the brand new field for that year included. This allows teams to explore the field through a 3D model, drive a robot around, and begin to strategize for the upcoming season's game.
  • Driver Practice & Strategy: Not getting enough driver practice or don't have a full field available to you? Synthesis has you covered with the ability to drive your robot around with a gamepad from a first-person view at the driver station; allowing you to get a feel for potential control scheme layouts and any line-of-sight challenges that may arise. This also allows the drive team and the programmers to communicate about what control layouts work best for each driver.

Getting Started

If you are a FIRST robotics student who just wants to use Synthesis, you don't need this repo. Simply install the latest release of Synthesis from synthesis.autodesk.com/download.

If you're a developer who wants to contribute to Synthesis, you're in the right place. Synthesis is comprised of 3 main components that can be developed separately. These components include:

Each of this components can be manually compiled separately, but this is not recommended. Instead, we recommend using the init scripts provided (init.bat & init.sh) to build and link each component together (excluding the Fusion Robot Exporter).

Compatibility Notes

As Fusion 360 is not supported on linux the linux installer does not come with the Fusion 360 Addin for exporting robots and fields.

Also note that the linux installer is tailored for Debian based distributions. Synthesis can be installed and ran on other distros but the installer is not guaranteed for your operating system.

Dependencies

Synthesis Version 6.0.0 has the following dependencies:

These dependencies need to be satisfied before attempting to build Synthesis with unity. You can either install these dependencies manually or use the resolve dependencies scripts (scripts/win/resolve_deps.bat & scripts/osx/resolve_deps.sh) to install some of them for you.

To automatically install .NET and Protobuf run the following script depending on your operating system:

  • Windows: scripts/win/resolve_deps.bat
  • MacOS & Linux: scripts/osx/resolve_deps.sh

Dependency Notes:

  • The windows script requires admin privileges to install .NET and Protobuf to the system PATH. For this reason it is not included by default in init.bat unlike how init.sh includes resolve_deps.sh.
  • Unity must be installed manually through the Unity Hub app which can be downloaded from https://unity.com/download.

How To Build Synthesis Using An init Script And Unity

Before attempting to build Synthesis, ensure you have all dependencies installed.

  1. Open a command prompt.
  2. Change directories to a location where you'd like to clone the Synthesis repository.
  3. Clone the Synthesis repository using git clone https://github.com/Autodesk/synthesis --recurse-submodules.
  4. Change directories into the root of the Synthesis repository and run the init script for your operating system.
    • Windows: init.bat
    • MacOS & Linux: init.sh
  5. Open synthesis/engine in Unity.
  6. From there, you can run the simulation engine inside the Unity editor by opening MainScene from the Assets/Scenes directory or build it as a standalone application.
    • To build Synthesis as a standalone application, go to File -> Build Settings and select your target platform. Then, click Build and select a location to save the built application.

Contributing

This project welcomes community suggestions and contributions. Synthesis is 100% open source and relies on the FIRST community to help make it better. The Synthesis Contribution Guide suggests ways in which you can get involved through development and non-development avenues.

Before you contribute to this repository, please first discuss the change you wish to make via a GitHub issue, email us ([email protected]), or reach out through our community discord. This way we can ensure that there is no overlap between outside contributors and internal development work.

When ready to contribute, just submit a pull request and be sure to fill out the template accordingly so that we can verify them and eventually merge. Feel free to check out our contributing guidelines to learn more.

Code Formatting And Style

Synthesis uses clang-format and black to format all of our C++, C# and Python code. Additionally we have GitHub workflows that verify these formatting standards for each and every pull request. For more information about how to run these formatters yourself, check out the formatting tools we use.

Components

Here is a brief overview of each of the components found in this repository. For more information about each component, their dependencies and their individual build processes, check out their respective READMEs.

  • Synthesis API
    • Components used to extend Synthesis' functionality while remaining Unity agnostic.
  • Code Emulation
    • Synthesis tool designed to help users test their FRC robot code in a simulated environment.
    • Code emulation is an advanced feature that is still under development, functionality and support is limited.
  • Core Engine
    • The core of Synthesis, the Unity project that contains the simulation engine.
  • Fusion Exporter
    • The Fusion 360 plugin that allows users to export their robots and fields into Synthesis.
  • Installer
    • Tools used to build the Synthesis installer for Windows, MacOS and Linux featured on our Download Page.
  • Mirabuf
    • A custom 3D file format developed by @HiceS that our Fusion 360 exporter uses.
  • Tutorials

Tutorials

We have a variety of tutorials available to help you get started with Synthesis. These tutorials can be found on our Tutorials Page on our website. Additionally, you can view these same tutorials as Markdown files in the tutorials directory of this repository.

Updating our tutorials is a ongoing process. If you are at all interested in helping, checkout the Synthesis Contribution Guide for more information on how to get started.

Immersion Program

Annually, since 2014, Autodesk has sponsored the Synthesis Immersion Program for FIRST robotics students to develop Synthesis. The immersion program is a 10 week paid work experience at the Portland, Oregon Autodesk office from June 20th to August 25th. The immersion program focuses on not only developing Synthesis, but also allowing for opportunities to meet and collaborate with other Autodesk employees. For more information about the immersion program, visit our website at synthesis.autodesk.com/internship.

Want To Be A Part Of The Team?

If you're a FIRST robotics student who wants to be a part of the Synthesis development team here is some basic information about applying.

Applicants must be:

  • At least 16 years of age
  • Been a member of a FIRST Robotics team for at least one full season

Applications open each year during the spring. For more information about applying, exceptions to these requirements or for more info about specific positions offered, please visit the Synthesis Immersion Program website.

Contact

If you have any questions about Synthesis or the Immersion Program, you can contact us through email ([email protected]). Additionally please reach out through our community discord. It's the best way to get in touch with not only the community, but Synthesis' current development team.

License

Copyright (c) Autodesk

SPDX-License-Identifier: Apache-2.0

synthesis's People

Contributors

a-crowell avatar aaron7317 avatar ambercmerrill avatar benjamin-l avatar brandonpacewic avatar cobaltcause avatar dj-jazzyjaz avatar hices avatar hunterbarclay avatar isabellecordova avatar joshgrace avatar kiracorbett avatar laurenchoquer avatar liamjwang avatar lonesymmetry avatar lucahaverty avatar luckyqxw avatar mackinnonbuck avatar mattmoradi avatar nickburrell avatar nicolasespinoza avatar nwalker1208 avatar pepperlola avatar philiparola avatar rasberrypai avatar tmiler avatar tridha avatar victorxheng avatar victoryforphil avatar waggonernathan0 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

synthesis's Issues

No emulator download link?

Description
The emulation tab gives an "emulator not installed" error and there is no download/install link for the emulator on the website.

Typo on "Network"

When going through the Network Multiplayer Beta (LAN) wizard, the banner over the top says "Nework" instead of "Network". It's not a huge issue, but something to maybe fix in the next release.

ADSK returning null in FusionExporter

adsk.fusionSendData('highlight', jointName);

Fusion 360 adsk is null issue

Currently having some issues with adsk for javascript specific calls returning null seemingly randomly. Is there a specific way that we need to access adsk object calls in our code in order to not have it return null on occasion ?

Specifically whenever we have buttons that may be used in palettes etc sometimes when you click them they do nothing and if debugging you can see that adsk is showing null but if you click it again it may be not null.

This is also happening with just palette sample code for us.

Usage with 2019 build system/GradleRIO

Absolute newbie to Synthesis here. Is Synthesis currently setup to work with GradleRIO and the 2019 build system? If so, how would I deploy my code to the Synthesis code emulator?

Joystick 4 constantly being pressed down, even when no controller is even connected

When trying to map joysticks and buttons from a controller, "joystick 4" is always registering, and overriding all over button presses, making it impossible to use. I thought this was a problem with the controller, but after restarting the app with dead zones on all the sticks so that no input should be read I found that the application itself thinks that "joystick 4" is always being held down, even with no controller connected. this has rendered the application useless if I can't map controller buttons.

Got stuck when I went into quick reset

I was in the Stronghold field with 188's 2016 robot. I pressed "quick reset" and then it won't let me return when I press the return button.

Also happens when I press "Change spawn point"

"User program not found"

When I selected my latest 2019 season code and clicked the "Run code" button, a message showed up saying "User program not found". The problem seems that QEMU was successfully booted but the code was not loaded. Does the v4.3.0 really support java code emulation?

Keybinding conflict between robot control & driver station control

To reproduce:

  1. Set the keybindings for robot control of Player 1 to a typical gamer-style configuration which uses a keyboard and mouse:
  • W = Forward
  • S = Backward
  • A = Left
  • D = Right
  1. Set the camera view to "Driver Station", which is a standard match configuration

Problem: When turning the robot left or right, the camera moves left or right in conjunction with the key pressed.

It would be nice to re-bind the driver's station camera binds to any keys, similar to robot control. In the very least, the key binding UI should provide a warning that these keys are reserved.

Alternatively, the default binds for camera control behind the glass could be the left/right arrows rather than A/D, as a static option in the keybinding UI.

Error installing on Ubuntu 19.04

Describe the bug
While trying to install Synthesis on Ubuntu I got this error: ./SynthesisLinux4.3.1.1.run: 1: eval: ./LinuxInstaller.sh: not found. It's really not lying (that file doesn't exist), but I think it should be working.

To Reproduce
Steps to reproduce the behavior:

  1. Open the terminal
  2. Run chmod +x SynthesisLinux4.3.1.1.run
  3. Run ./SynthesisLinux4.3.1.1.run
  4. Observe error

Expected behavior
I expected it to install successfully.

Screenshots
Screenshot from 2019-11-01 19-40-12

Desktop (please complete the following information):

  • OS: Ubuntu
  • Version 19.04

Additional context
¯_(ツ)_/¯

Synthesis installer skipping directories when installing

Describe the bug
When I install Synthesis, using the 64-bit installer provided on the Autodesk website, with all boxes checked (including the box to install the Fusion 360 addin), the Synthesis default robots and the Fusion 360 exporter addin both are not installed.
C:\Users<USER>\AppData\Roaming\Autodesk\Autodesk Fusion 360\API\AddIns
path is empty, I also had other addins there, but they were deleted in the process of uninstalling Synthesis, I think. I also don't have a Synthesis folder anywhere in my AppData folder. I have started the program multiple times, but never got past the starting screen where I select my robot, because I don't have any robots, default or otherwise. I am using an installer downloaded three days ago.

To Reproduce
Steps to reproduce the behavior:

  1. Download the 64-bit version of the Synthesis installer
  2. Run the installer

Expected behavior
I expect the installer to install the sample robots and Fusion 360 addin

Screenshots
C:\Program Files\Autodesk\Synthesis\Exporter
image

This is where I found what looks like to be an Inventor addin, maybe? These are all of the files in that directory.

Desktop (please complete the following information):

  • OS: Windows 10
    Version 1909

2020 Summer Intern Applications OPEN NOW!

2020 Synthesis Internship Post

Hey all we are opening our internship application for the 2020 summer internship that extends from:

June 22nd 2020 - August 28th 2020

Link to our internship application

Below you can find some information, FAQ, What the devs are looking at, and our new modernization information:

FAQ

  1. What is the skill level required of an intern?
    We interview and look for interns in all skill ranges from beginners to super users, my recommendation is if you get excited about robotics simulation we would love for you to apply. Honestly a lot of what makes developers crazy good is their passion to improve a project.

  2. What age do I need to be?
    You need to be 16 by June 22nd Technically. For any more information or questions regarding this please email [email protected].

  3. Where are the position descriptions?
    Currently we haven't posted the hiring position descriptions and rundowns (by accident) but when they are available which will be soon they will be located on our internship page found on our website in the link above.

  4. Where is the internship located?
    The internship is located in Portland, Oregon. You need to present during the internship in the Portland office which can be difficult for students that need to find housing so we try to make decisions early in the year if possible.

(Any other questions we get from emails or forums or in person should be added here to be tracked if viable for general public.)

Development Ideals

We are actively trying to find people that fit into both specific and general development roles. Specific meaning that some positions require advanced knowledge of a topic in technology we are trying to take advantage of to modernize our software.

Some of the things we are currently investigating for modernization:

  • Compute Shaders and Graphical Parallelism
  • GRPC
  • Protobuf
  • Physx in Unity
  • Customer Deliverable

Many of these we need to refine, we have built some prototypes for the new engine and exporter as well as the basis for what we are calling the "Controller". Which is a replacement and enhancement of the emulator. (more in the modernization section)

Modernization

After looking through our JIRA and debilitation on improving the current state of the engine and physics simulation we have made some difficult decisions surrounding the continuing development of the physics simulator with Unity.

Unity

Unity is a fantastic platform and we will continue to use it to develop the simulator after prototyping some modern fixes for older issues. We will be using the most up to date unity edition to redesign basic functionality with better rendering pipelines to improve machine dependent performance issues as well as enabling the integrated PhsyX platform in Unity to do our physics solving. Through the last two years they have made so much progress and enhancements to their built in physics layer that it was an easy decision to abandon the bullet wrapper we were using previously. This will also come with a host of improvements to the code base and completely axe off any asset store dependencies.

Fusion 360

From our analytics and communicating with teams it seems that Fusion 360 is increasingly popular with our user base. However this is also the most problematic and hard to maintain feature of our codebase which is why we have switched to developing in C++ to developing in Python in order to reduce complexity and training overhead for new developers. It also supports our goal of minimizing the exporting steps and maximizing customization in Unity for reduced number of "re-exports" to fix the user story of re-exporting the robot to re-configure the CAN values or Gearing values. We also entirely depend on Protobuf to define how we export geometry and join values from the fusion 360 model which reduces save time, memory consumption, and hard drive space for files. Overall we were also driven to make these changes to support the OSX users that have been giving us feedback about the usability of Synthesis on other machines.

Inventor

We are still deciding on Inventor changes and support may be delayed until finalizing changes for Fusion 360 and supported exporting formats to minimize old file error issues between the two.

Controller

The most exciting new change for us is the Controller product. The Controller will feature a set of communication protocols in order to enable outside developers to use a common communication library to control the robot and world simulation. One of the development tasks is also to create a template repo that contains the basics of how to develop a new library in any language you choose to communicate with Synthesis over GRPC. We will be developing a sample library to use for those users who want to develop code for robots and practice with a variety of different libraries in a simple way. This is going to be a main focus for us in creating new experiences for our users in ways the hopefully encourage learning and possibly creating workflows we previously hadn't thought of. We are very excited to see what we can come up with in this area, we are also looking for developers in this area with experience in using libraries in other languages and understand async code as well as GRPC.

Recommendations:

  • Put your github on your resume (please)

  • We are really interested in hearing about your projects and the cool things you do for fun. I find a lot of people will forget to include fun projects in resumes or applications but at Autodesk we love to see awesome people making cool things so don't feel afraid to include too much information.

  • We won't care how long your resume is as long as you're using the space constructively and it can describe what you like and what you have done, so please don't delete anything for the sake of saving a page. Especially if it's technical.

  • We don't want super short ones, many people miss out on opportunities because they must either think we won't look at the resume or we wont want to look at a long one but I promise you we all look through all of them and most of us are developers so please include some technical stuff. (Personally I care a lot less about where you go to school and far far more about when you used opencv to do some cool things with graphics or when you wrote a world of warcraft script etc. so please don't only put your school give us something to get excited about for meeting you)

Version controlling unnecessary files

For example, there are a disappointing amount of *.dll files, obj, and bin directories. These should not be tracked by git, as it's main purpose is source version control, not binary version control. It's likely that a discussion about .gitignore files should occur.

Fusion - Read Component Tree

Write code to go through each component in the current design and read it's data, preparation for protocol buffer

Known Issues

Hello everyone, we had a discussion about wether to keep our publicly known issues for the release in a forums post or on the git page. For now the git issue page has won.

Version Number (4.2.0.1): Release Link

  • Controller mappings disappear when changing fields
    Fix: In release

  • When going through the Network Multiplayer Beta (LAN) wizard, the banner over the top says "Nework" instead of "Network". -insert name of reporter but I'm on mobile so check back later

  • Trying to setup our joysticks for tank drive (Attack 3 joysticks.), but it is not registering the joysticks properly. Both Joysticks read as Joystick 1.

  • PS4 Controllers are having issues with Joystick4 Issue posted

  • Fusion 360 exporter buttons wont work
    Fix: right click on palette -> showdevtools (instantly fixes problem) Issue posted

  • Exporters export to %appdata%/Synthesis/Robots instead of %appdata%/Autodesk/Synthesis/Robots causeing issues for users.

  • Support more than 8 CANIDs issue posted

  • Robot wheels not colliding with ground properly issue posted

  • Fusion 360 exporter won't start for some machines issue posted

  • Fusion 360 exporter causes many crashes

Could not find the selected robot!

In many occasions, when I launch Synthesis (Windows 10 - 64 bits version), the Robot Selection pop-up window opens with the following message: "Could not find the selected robot"
When selecting "Change Robot Directory", I am taken to the correct folder. By selecting the folder again, Synthesis becomes capable of finding the robot.

image

MD5 checksum error

I'm trying to install synthesis on Ubuntu 18.04. I've tried downloading the .run file from your website multiple times on different networks and each gives the following error:

./SynthesisLinux4.3.3.run

Verifying archive integrity... 100% Error in MD5 checksums: 9ad4b1713f8037af0e19d82daac9301d is different from 6ebc204e0021d72674c6bfb35e7451a6

Engine - Asset Manager

The object manager handles loading in assets such as robots and fields. They are then added to a registry so they can be instantiated by the world manager at any time.

post-install.sh on MacOS shouldn't rely on homebrew

Is your feature request related to a problem? Please describe.
Most users don't have homebrew installed, so post-install.sh shouldn't rely on it.

Describe the solution you'd like
Use the tools that are part of unmodified MacOS installs.

Describe alternatives you've considered

  1. Remove the "Sanity check for brew" block.
  2. Replace wget https://github.com/Autodesk/synthesis/releases/download/v4.3.3/SynthesisSampleAssets.zip -q --show-progress with curl -LO https://github.com/Autodesk/synthesis/releases/download/v4.3.3/SynthesisSampleAssets.zip

The entire screen shakes

Describe the bug
The first time when i start the program after downloading it. It workes "fine". Except the robot flies everywhere. Something with the physics. (when the robot has less parts it works better).
Every time when I start the program after that, the entire screen UI shakes. And I can't click on anything in th UI.

To Reproduce
Download it.
open the programm.
close the programm.
and re open it.

Expected behavior
good working physics and an UI which stays on it's place

Screenshots
If applicable, add screenshots to help explain your problem.
image

Desktop (please complete the following information):
-Windows 10
-synthesis 4.3.1.1
-NVIDIA GeForce GTC 1070 max-Q
-i7 processor

Additional context
Add any other context about the problem here.

No network multiplayer?

Description
Has the Network Multiplayer been removed from Synthesis? I can't find it 🤔
Thank you!

Emulator tab non-functional

I have just downloaded and installed the latest version of Synthesis (4.2.2.0) and then installed the corresponding emulation package.
When I launch Synthesis I see an emulation tab, but when I click it nothing happens. The icons do not change and I am unable to load code or perform any other emulator specific tasks.

Gamepiece selection can't be changed

Describe the bug
In the Gamepiece tab, the leftmost button shows a drop-down menu to select a different gamepiece. It seems like it should allow settings to be changed for the second gamepiece. However, selecting it doesn't appear to do anything. This makes it so the intake, release, trajectory, spawning, etc. for the second gamepiece can't be used.

To Reproduce

  1. Start Synthesis
  2. Change to a field with two gamepieces such as 2019 Deep Space or 2017 Steamworks
  3. Try changing the selected gamepiece in the Gamepiece tab

Desktop (please complete the following information):

  • OS: Windows 10 Version 1903
  • Version: 4.3.1.1

Trajectory Setting with Robot Reference Axis Skewed

If a Robot is defined with its axes so that it will be placed on its side when being added to the field, the release trajectory setting axes will also be skewed, making it impossible to properly set the trajectory. See attached screen capture.
Running Synthesis V4.2.0.1
releasetrajectorysettingissue

CAN IDs more than 8 possible?

Currently in the Inventor Exporter we're only able to set maximum 8 CAN IDs while our robot uses 16 motor controllers (Talon SRX). Are we limited to these 8 or are we doing something wrong?

Emulator support for macOS

Is your feature request related to a problem? Please describe.
Can't run the emulator on macOS.

Describe the solution you'd like
To be able to run the emulator on macOS. It looks like this has come up before (#477), so I'm wondering if there's a timeline for when this is expected to be implemented.

Make wheels not bounce after going to fast

Due to the fact that cylinder colliders have flat faces, they can start bouncing if they roll to fast. We need to either find a way around this or a middle ground that will make it so that user can't tell the difference.

Synthesis causes crashes

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
Description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. Windows 10]
  • Version [e.g. Service Pack 2]

Additional context
Add any other context about the problem here.

Qemu not found on Arch

Describe the bug
On Arch, I have installed the 'qemu' and 'qemu-arch-extra' packages, but Sythesis cannot find qemu. I don't know if there are more packages I need to install, but no combination of these will work.

To Reproduce
Steps to reproduce the behavior:

  1. Install 4.3.2 through the latest github release for linux.
  2. Install 'qemu' and 'qemu-arch-extra' through pacman.
  3. See error

Expected behavior
The emulator tab should show a Start button, not a Not Installed button.

Desktop (please complete the following information):

  • OS: Arch Linux 5.4.11-arch1-1
  • Sythesis Version 4.3.2

Can't run Synthesis on Arch Linux

Description

After installing Synthesis on my machine and looking through the installer script for the installation location, I tried to run it.

~ ➜ /usr/share/Autodesk/Synthesis/Synthesis.x86_64
fish: The file “/usr/share/Autodesk/Synthesis/Synthesis.x86_64” is not executable by this user

So I tried running it again with sudo...

~ ➜ sudo /usr/share/Autodesk/Synthesis/Synthesis.x86_64
Found path: /usr/share/Autodesk/Synthesis/Synthesis.x86_64

A blank fullscreen window appears, and...

fish: “sudo /usr/share/Autodesk/Synthe…” terminated by signal SIGSEGV (Address boundary error)

I didn't get any more output, so I have no idea what the issue could be.

System Information

  • Operating System - Arch Linux
  • Desktop Environment - GNOME 3.36.0
  • Window Manager - Wayland 1.18

Engine - EnvironmentManager

This will be manage the lifetimes of the objects inside the core. It will create objects, update them throughout their lifetime, and deleting objects from the core environment

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.