It looks like there is an issue with syncing back non-script instances, will fix that today.
1 Like
Argon executables are built automatically on GitHub Actions runners so there isn’t much I can do to fix it other than downgrading the OS they use. I released a new CLI version today, could you test it and let me know if the issue persists?
VS Code extension does not respect CLI config as it’s a separate system. I added a new setting for it that you can disable:
Make sure you update the extension to the latest version.
It’s caused by the install_plugin setting which is enabled by default. Installing the Argon plugin via CLI isn’t currently supported on any Linux distro so make sure you disable it.
Yeah that’s how Argon gets compiled so I might have to downgrade Linux runner. Let me know if the issue is still there on version 2.0.23.
i have not used UIDragDetector, however, it seems that it works now! thank you for this update.
hey so uh, apparently i managed to break argon. idk how, it was working just fine,
now it wont even find reg, and if i put C:/Windows/System32 or something similar it just keeps telling me to restart the computer or run vs code as administrator with both doesnt work
That’s weird, what OS are you running? Also could you run this command: reg query HKEY_CURRENT_USER\Environment /v PATH in your terminal and let me know if it still errors?
hey so uh, i didnt see this but i managed to fix this by doing a system restore which fixed my problem, i ran the command which seems to tell me the paths after i did the system restore, now im not sure whenever it couldn’t find path because the path was exactly the same or reg just wasnt a command. If the problem still occurs i’ll report it in here asap
1 Like
How can I use argon for multiple developers at the same time working on the same place?
Hi, it broke same error. (Verified by manually downloading 2.0.23 from github)
Thanks for adding that option in VS Code extension.
I will compile it myself for now. Let me know if you downgrade Linux runner. I will test it again.
I recommend using this official VS Code extension called Live Share. It works exactly the same as collaborative editing in Roblox Studio. Keep in mind that only host needs to run Argon.
Okay, I’m going to downgrade it in the next update. Will let you know when it’s ready
Hello,
The “Open In Editor” feature is not working properly.
After checking the detailed logs, I found the following:
- In Roblox Studio:
TRACE: Client request: open - In VSCode:
TRACE: Received request: open [argon::server::open:19]
However, nothing opens in VSCode, and no changes occur. I’m using Windows.
Is there anything else I should check to get this feature working? Would it be possible to investigate this issue?
Thanks!
Hi, thanks for all the details. I will look into it next week.
1 Like
Is there a way to edit multiple places at time?
Oh also would like to report a bug, It cant find my Git binaries, while i have them installed and fully functional
nvm, i figured it out, you just set the port to something different for each place
Hi, found another issue:
When building my project, I’m seeing all my BasePart objects colors being reset to {255, 255, 255} even though the init.meta.json file has specified its Color value. Is there a setting I need to turn on when building?
Suspecting what’s wrong:
MeshParts are storing the color property as if they were getting translated as RGB uint8 values, but Im guessing you are treating them as regular color3 float values between 0 and 1. So when you multiply them by 255 you get a number greater than 255, which is just 255, hence why everything is white.
Thanks for this plugin! I use it with Knit + Roblox LSP, and it works great. However, I have a small issue: I need to start Argon after Roblox LSP. If I start both at the same time, IntelliSense doesn’t work.
Do you have any suggestions to fix this?
Im using the Default Roblox LSP, and it works just fine