And what is the error?

hi! i am not too sure, i use gemini and it mentioned because my model was not in the diffusion model folder but it is and i also installed all the Moss needed nodes but it just cannot work

I experienced the same problem with this int8 quant. Didn't have any issue loading the one released by Abiray a few days ago even though they're both convrot-int8, so not entirely sure what the issue with this quant may be but refuses to work for me also.

There are no nodes to install, these models are meant to be used only with the native ComfyUI core nodes.

Im getting:

ComfyUI Error Report

Error Details

• Node ID: 32
• Node Type: UNETLoader
• Exception Type: RuntimeError
• Exception Message: RuntimeError: ERROR: Could not detect model type of: H:\cimfyuidoc\models\diffusion_models\moss_image_base_int8_convrot.safetensors

on the Load Diffusion Model Node.

I noticed that the WFs use 'moss-image' for the CLIP-type, but I cant use that one, it throws an 'invalid input', so I changed it to the 'Flux 2' CLIP Type.

Did you update Comfy? As of last night, I still had to go to the nightly build to be able to use the moss-image type in CLIP...but this morning the stable build seems to work

Did you update Comfy? As of last night, I still had to go to the nightly build to be able to use the moss-image type in CLIP...but this morning the stable build seems to work

Yes, I did. Checked multiple times today, latest 4 minutes ago. Im on 0.41.3.
Any place I can check the latest changelogs? On https://docs.comfy.org/changelog the latest entry is 0.41.1

Did you update Comfy? As of last night, I still had to go to the nightly build to be able to use the moss-image type in CLIP...but this morning the stable build seems to work

Yes, I did. Checked multiple times today, latest 4 minutes ago. Im on 0.41.3.
Any place I can check the latest changelogs? On https://docs.comfy.org/changelog the latest entry is 0.41.1

If you have 0.41.3 you are on a "tagged" version, which means you are on the latest stable branch which does not have MOSS support yet.

For having the required nodes you need to be in the nightly build, which corresponds to the latest master github branch without tagging (will show 0.41.0 version).

Making the transition from stable to nightly is tricky and somewhat dangerous if you don't know what you're doing, so I advice you to make a full backup copy of your installation and then proceed to update using the bats in th comfyui update folder.

Did you update Comfy? As of last night, I still had to go to the nightly build to be able to use the moss-image type in CLIP...but this morning the stable build seems to work

Yes, I did. Checked multiple times today, latest 4 minutes ago. Im on 0.41.3.
Any place I can check the latest changelogs? On https://docs.comfy.org/changelog the latest entry is 0.41.1

If you have 0.41.3 you are on a "tagged" version, which means you are on the latest stable branch which does not have MOSS support yet.

For having the required nodes you need to be in the nightly build, which corresponds to the latest master github branch without tagging (will show 0.41.0 version).

Making the transition from stable to nightly is tricky and somewhat dangerous if you don't know what you're doing, so I advice you to make a full backup copy of your installation and then proceed to update using the bats in th comfyui update folder.

Got it, thank you for the answers yall.

Also another error at the ksampler is dtype. For whatever reason this INT8 version errors due to the shift node and removing it does solve it.

Also another error at the ksampler is dtype. For whatever reason this INT8 version errors due to the shift node and removing it does solve it.

Nothing to do with the model file, if you're using ModelSamplingSD3 that's just a wrong node in general, to adjust shift you'd just the ModelSamplingAuraFlow or ModelSamplingFlux -nodes as they use same scale.

if the type is new and not selectable in clip nodes that is usually a good indication that the version/update is not updated.

if the type is new and not selectable in clip nodes that is usually a good indication that the version/update is not updated.

Thats what I thought, but someone in the comments said that he was on stable and it worked. That was the source of my confussion.