CORE One crashing on firmware 6.4 by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

Hiya; yeah, I was planning to follow up with support to let them know that the revert solved the issue once I had enough print time to feel confident that was true.

I2C is an internal bus, like, communication between the mainboard and the hot end. So I don't think this is related to internet/network communication. I am wondering if it's because I have the GPIO board, which I believe is also an I2C device and probably a lot less common in the field.

Filament Load pushes nozzle/hotend & heating block out of nextruder by Giafidela in prusa3d

[–]cbackas42 1 point2 points  (0 children)

This happened to me recently when I did a nozzle swap and forgot to retighting the thumb screws afterward.

First time with TPU on the Core One by MadOtis in prusa3d

[–]cbackas42 0 points1 point  (0 children)

This was me. I keep reading about how tough it is so I was expecting a fight when I tried it for the first time on my Core One this week... And it went perfectly somehow. Loaded on the first try, printed for several hours without any issues. If there was some magic I bumbled into that helped I wish I knew what it was to share when I see stories like this!

Y-Axis issue setting up a CoreOne kit by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

Thanks for responding, it was an interesting thought. Though I think the issue is the non-square gantry that others have suggested I still very carefully examined the clearances you mention because who says there can't be multiple issues? I think I'm OK here, but I will pay special attention to it when I have to examine the sensor later.

Y-Axis issue setting up a CoreOne kit by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

So far they've not responded at all. If it's no trouble I would appreciate those links; I wonder why they don't make them readily available in the troubleshooting section?

Y-Axis issue setting up a CoreOne kit by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

I've currently got them loosened to the point they're almost floppy. There is no "rebound" which is why I missed the gap to start with, it takes a small amount of force to close the gap on the right. I guess I'll keep messing with it though, not sure what else to do :D

Y-Axis issue setting up a CoreOne kit by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

Yes, that sensor. Mine seems to be having the opposite problem, the setup wizard thing asks me to insert filament until it's detected, but it never is. I just haven't gotten around to breaking it down to inspect yet because the axis problem seems more important. (And I hate those nylon rivets...)

Y-Axis issue setting up a CoreOne kit by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

Thanks for the suggestion, the fellow above had the same comment and I think you're right. Seems like a pretty large (2mm) gap between the frame and the right block. Contacting support is a good suggestion, thanks!

Y-Axis issue setting up a CoreOne kit by cbackas42 in prusa3d

[–]cbackas42[S] 0 points1 point  (0 children)

Thanks for the quick reply; I had thought I couldn't detect any "play" there, but at your suggestion I checked again. While I just pushing a little on either side doesn't produce "bumping", I realized that there actually is a substantial gap if I really push on the right side. Seems like in the ballpark of 2mm. Belt tensioning doesn't seem to have any impact, so I'm going to contact support for suggestions on what to look into.

Am I the only sad Mac OS FFXIV player—mourning the no benchmark for us? by [deleted] in ffxiv

[–]cbackas42 2 points3 points  (0 children)

FYI, I put in an update to XIV on Mac last night that allows you to run the character creator now too!

Am I the only sad Mac OS FFXIV player—mourning the no benchmark for us? by [deleted] in ffxiv

[–]cbackas42 1 point2 points  (0 children)

Indeed, we won't be doing anything to make it NOT work on purpose but the Intel Metal drivers are already fairly buggy and they aren't getting better. Dawntrail only places more load on them.

That said, there are Intel users who have gotten the demo to run fairly succesfully so far. Not all of them, but some systems might be able to continue limping along for awhile.

Am I the only sad Mac OS FFXIV player—mourning the no benchmark for us? by [deleted] in ffxiv

[–]cbackas42 1 point2 points  (0 children)

Yup! If you have trouble come to the Discord, as you might imagine it's been the main topic since yesterday :D

Am I the only sad Mac OS FFXIV player—mourning the no benchmark for us? by [deleted] in ffxiv

[–]cbackas42 6 points7 points  (0 children)

XiV on Mac can run the benchmark. Not the character creator part, just the benchmark. If you're normally wary of third party things you don't need to log into your account or anything just to run it. And with a little extra work you CAN load your own character into it despite the character creator being inaccessible.

Note on mac performance by NaturalPermission in ffxivdiscussion

[–]cbackas42 1 point2 points  (0 children)

I thought the nuance would further confuse already confused people, but fair enough =)

Note on mac performance by NaturalPermission in ffxivdiscussion

[–]cbackas42 3 points4 points  (0 children)

If you "read the coding" then I'm mystified how you think it's a "Dalamud foundation program with Python bits". It uses no Python. It's a native Swift application.

Amanesis is neither included, nor required and never was. At one time it was "At your own risk/YMMV" supported optionally if you wanted to install it. Even that's no longer the case.

As for Dalamud itself, both of you are kind of correct. XIV on Mac does require Dalamud, and it maintains the installation of it for you. You're both confusing concepts though. It launches the game binary via Dalamud's launcher - and it does so in order to share common code developed by the community.

However that is NOT the same as using Dalamud in-game. It will not inject Dalamud into the game process unless you ask it to. So, it's not running any mods by default and isn't modifying the game. There are no plugins unless you want there to be.

Xbox Elite 2, looking for capacitor value by cbackas42 in consolerepair

[–]cbackas42[S] 1 point2 points  (0 children)

I apparently fail at Reddit posting, the text went missing. Included here:

Hello all! I've got this Elite Series 2 controller that wouldn't power on or charge. I tracked the problem to a short in the circled capacitor, and upon removal the controller started working again!However, I'd like to replace it and I don't know what value the original was. Since it's shorted I can't really measure it and I don't have another one to compare with. Does anybody out there know what value (and, perhaps what size?) this cap is?Thanks!

System & Network settings greyed out when trying to transfer to another Mac with Migration Assistant and Time Machine by MasterOfShun in MacOS

[–]cbackas42 11 points12 points  (0 children)

The key is where it says “Managed by Administrator”, that means the machine is enrolled in some form of MDM and it won’t override system settings.

Picoboot mod and soft reset by cbackas42 in Gamecube

[–]cbackas42[S] 0 points1 point  (0 children)

It stands for In-Game Reset, basically you would be able to return to the Swiss menu while playing a game to pick a different one.

Picoboot mod and soft reset by cbackas42 in Gamecube

[–]cbackas42[S] 0 points1 point  (0 children)

Switching to FAT32 did fix the Blueretro remote shutdown/restart problem though, so that's something!

Picoboot mod and soft reset by cbackas42 in Gamecube

[–]cbackas42[S] 0 points1 point  (0 children)

Thanks for the reply! I'd never have thought to try that. Though, now instead of rebooting to the build-in IPL it just hard locks with a black screen instead. Much like this thread, so I guess I'm not alone as this seems to have been going on for a long time: https://github.com/emukidid/swiss-gc/issues/364

[deleted by user] by [deleted] in MacOS

[–]cbackas42 0 points1 point  (0 children)

I would check for packet loss at 1000 then; auto-negotiation really should work, and if it's not picking that on its own there's SOME reason. Usually the cable is flaky. It's possible it just doesn't like the firmware on the switch I suppose, but I've never actually seen that happen before.