pyro/fyer_deck
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'refs/remotes/origin/main'

Browse Source 
Adjusted some files and added 3mf files.
This commit is contained in:
pyro57000
2025-03-26 09:43:03 -05:00
parent ba0d7e882d 0dc3e36223
commit 8ea6f03265
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -38,7 +38,7 @@ I'm still in the prototyping phase (I'm close to a final design, so the current
I also have not figured out the screen solution yet, so bear with me, I'm still working on it! I also have not figured out the screen solution yet, so bear with me, I'm still working on it!
# Assembly # Assembly
1. print out all the parts, starting with the battery tray. 1. print out all the parts in the stls/fyerdeck_files folder, starting with the battery tray.
2. assemble the battery tray halves together (it may require a hammer to get the halves flush, since they are friction fit it will be a VERY tight fit, this is expected. 2. assemble the battery tray halves together (it may require a hammer to get the halves flush, since they are friction fit it will be a VERY tight fit, this is expected.
3. put the framework speaker modules in the slots for them. At the moment they are just friction fit, so I might design some kind of locking mechanism for them, but haven't had to yet. 3. put the framework speaker modules in the slots for them. At the moment they are just friction fit, so I might design some kind of locking mechanism for them, but haven't had to yet.
4. make sure the connector is run about where it will pop through the motherboard tray. 4. make sure the connector is run about where it will pop through the motherboard tray.
@@ -109,7 +109,7 @@ Otherwise, the whole purpose of VR/AR compute environments is to not be constrai
5. `cd ../simular; cargo build --release` 5. `cd ../simular; cargo build --release`
8. (optional) copy the resulting binaries to somewhere on your $PATH, to make running them easier. 8. (optional) copy the resulting binaries to somewhere on your $PATH, to make running them easier.
9. make a stardust startup script. 9. make a stardust startup script.
1. 9a.) `mkdir ~/.config/stardust` 1. `mkdir ~/.config/stardust`
2. `nano ~/.config/startudst/startup` 2. `nano ~/.config/startudst/startup`
3. paste the following script into the editor, and edit the paths to accurately reflect where you either compiled the binaries, or saved them to your path: 3. paste the following script into the editor, and edit the paths to accurately reflect where you either compiled the binaries, or saved them to your path: