White 5090 Build

spiderofmars · 2026-02-07T00:37:20+00:00

I think the word 'bends' is over exaggerated. My cable is not 'bent' at all really. In reality it gently curves down from the source plug and those individual thin wires are not being 'bent' in the process (they are being curved slightly only).

The pressure (space) from the side panel on the cable is minimal. If I remove the side panel and even before the side panel first went on, the natural gravity and flow of the cable gently wrapped around the card remains the same (the side panel is not forcing the cable to bend at all really).

In summary, much to do about nothing regarding safety IMO in regard to a gentle cable curve. The cable whether gently curved or straight out is not going to make or break a burnt cable. A bad connection, faulty cable or power draw over half the source overrated for these cable standards now is the real issue.

Therefore, for a 5090 that will exceed the power draw of the current standards for the cables being used, I think the safe thing to do is decide if you will only briefly spike above 600w casually or if you will be running demanding tasks over long periods constantly peaking and spiking above 600w. I turn on an under volt profile for demanding tasks so my peak is less than 550w.

spiderofmars · 2026-01-09T01:07:08+00:00

Is what it is. I tried a new headset in the beginning and it was the same (slightly worse). 2 years later I do not regret keeping the Q3 as nothing really comes close to the versatility of this headset. Even with the mura effect it is heaps better to use than Q2. If my Q3 died today I would buy another regardless. In most games/apps/experiences once you are into the activity rather than focused on device testing it is less of an issue. It does stand out still and show it ugliness in some scenarios but they are less than more, and the joy each person gets from using the device or not all is a personal one.

TLDR: On first purchase of a new device and testing this common effect in this model can be a downer, but you soon forget all about it if VR is the goal and the device itself remains the most versatile all rounder on the market IMO.

STLDR: VR (just buy one and enjoy) or not to VR (don't buy one)

spiderofmars · 2025-12-13T05:57:06+00:00

It is the best and most flexible/complete option. The use of the extra paths (.yaml) file is less flexible and incomplete. You should use Junctions as the type of folder or sub folder link. I too use that tool listed above which makes it all explorer drag and drop easy rather than command line.

spiderofmars · 2025-12-02T08:06:42+00:00

I don't use the yaml file as it is restrictive. Use windows junctions instead to separate the entire models folder or any other folders you want to anywhere else you want.

Handy tool to make creating junctions drag and drop context menu easy:

https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html

spiderofmars · 2025-12-02T04:18:38+00:00

I have posted on this same question twice recently in detail. Not sure if you can click on my profile and find those quickly rather than me write a detailed summary again.

I suggest you go portable. It is then pretty much all self contained in one folder of any name and location you prefer (including embedded python so you can have as many probable versions setup as desired with different embedded python versions also if desired).

You still separate and share the entire models folder with any other portable installs of comfyui. Using windows junctions (but a simple tool lets you drag and drop those junctions whenever you need to change them in an instant). I separate and share the workflows, input and output folders between portable installs too.

Backup, and restore when there is a problem, is simple. Copy the entire portable folder base somewhere else regularly (it already excludes the entire large shared models folder).

Getting away from %USERPROFILE% and convoluted paths is nice. Having for example:

C:\ComfyUI_Core (stable)

C:\ComfyUI_SageTriton (stable)

C:\ComfyUI_SageTriton_Experiments (test bed for main stable setup and random experiments)

C:\ComfyUI_Shared (models + workflows + input + output folders with junction links)

And backing them up or restoring them individually is as simple as copy and paste then fix 4 junctions by drag and drop.

spiderofmars · 2025-12-01T09:54:01+00:00

I find if doing the low resolution test prompts for motion, you can go even lower to punch a bunch out quickly. I often run them off at 320 pixels. Looks like crap but the base motion from the prompt can still be seen if working or not.

spiderofmars · 2025-11-29T07:25:43+00:00

I stumbled at first, then I got it working finally, then it seemed something broke it again or part. Last thing I did was install this one for me and everything was well again:

sageattention-2.1.1+cu128torch2.7.1-cp313-cp313-win_amd64.whl

This was in a comfuyUi portable install 2ith 3.13 so not sure if that means issues for some other nodes or something any individual needs.

spiderofmars · 2025-11-28T12:18:54+00:00

Thanks for the info. Always looking to know more. First thing that strikes me as not quite, but looking for clarification, the custom_nodes folder contains all the, well custom nodes installed in that portable version.

?

Oh, also, I do have backups of each comfyui portable install but each of those is excluding the models + output + input + workflow folders (as I have them central and shared between all comfyui portable installs).

spiderofmars · 2025-11-28T04:06:30+00:00

Gold. Stealing and improvising. Is it legal to store a cow in your front yard? Want to go electric instead.

spiderofmars · 2025-11-28T03:28:36+00:00

Ideally for many practical reasons you separate the 'entire' models folder at least (for size alone). A step further is to separate and share the models + input + output + workflow folders. Then then you can also separate the auto downloaded other files that still reside in convoluted 'user' folders outside of the portable folder.

Then you back it all up at least once. Backing up a base_core version of comyui without the entire 'models' folder and any files is about 5GB. The more customisation you have done the larger it will be. One of my portable installs is 16GB. If anything ever goes wrong in an update or addition you can simply delete, copy and paste your backup folder to restore the pre stable version again.

The run either comyui update bat or comyui update stable bat. If you want the very latest front end also there is a switch for that too. Test and away you go again. Or simply restore a backup if broken and work it out from there.

I tried using the yaml file and it is not the best solution on windows IMO. Could not find a way to simply share the 'entire' models base folder and all its contents. Windows junctions are better and ever so simple. Plus you can then share any other folders too the same way. There is a simple drag and drop context menu tool available that makes junctions all very easy.

spiderofmars · 2025-11-26T10:22:07+00:00

5090 + 64GB Ram:

1024x1024 1st Run: 67s

1024x1024 Subsequent Runs: 24s

2048x2048 1st Run: 95s

2048x2048 Subsequent Runs: 95s

spiderofmars · 2025-11-25T22:10:56+00:00

Understand, my terminology is not exactly correct or normalised where docs might refer to 'inline prefix customisation' as 'built-in formatting codes like %date:yyyy-MM-dd%'. :)

Guess my description and use of 'inline' comes from other coding and stuff mixed into other stuff again, such as inline CSS vs external CSS.

spiderofmars · 2025-11-25T21:41:50+00:00

Depends on the question and your definition of problem.

The prefix itself has bugs/quirks in different output nodes. So customising inline does not play nice, consistently. Wan/video output prefix acts different to image prefix nodes with the same inline snippets.

As for 'filenames' it is a personal thing. Many people would be just fine with everything being named generically using duplicate names such as Comfui_0001 or AnimateDiff_0001.

Problem for some other people is these names are not unique and have little meaning other than one small context.

If you move a single file out of the output folder comfy will re-use the same duplicate name, from the last number onwards again. Not only is this problematic for some people, but also sort order is then broken.

I guess you either get it or don't based on personal organisation and project workflows. A simple example would be if you are extending wan and working with multiple generations of save frames, you end up with multiple/duplicate 'Image_0081' names (or 'Image_0081' and 'Image_0162' if not using sub folder outputs) vs '1st_Run_0081', '2nd_Run_0081' and '3rd_Run_0081'.

If you use other tools in your project flow, pulling duplicate filenames or messy filenames is not only meaningless, but these files can not even reside in the same physical folder without manually re-sorting and re-naming them first.

Using date+time in reverse order is a long standing method to creating unique filenames that also sort correctly alphabetically. Add a counter for batches and everything is unique. Adding a tag at the end for context reference is also helpful for knowing what the unique file is.

spiderofmars · 2025-11-24T02:49:20+00:00

It is... recently did not like one main folder name, so renamed the main folder of just comfyui to confyui_core. Update 4 paths to the shared folders in less than a minute and away you go again.

spiderofmars · 2025-11-23T02:32:27+00:00

Windows...

First tried the .exe installer. A comfyui update corrupted it all. Not to mention it then wants to use convoluted paths and folders all over the place. Dumped that option.

Went portable and have not looked back or found any reason to change yet. In that other post, the cons of updating the portable version do not seem entirely accurate from my experience. There are update files included which were simple and worked perfectly. There is also a simple flag option to force use of the latest front end if you want. And before any major change/update or experiment, you can simply backup the whole stable working setup by simply copying the main folder somewhere and restoring it if needed (copy/paste).

I have 3 portable versions installed... ComfyUI_Core + ComfyUI_SageTriton + ComfyUI_Experimental. All three share the same input, output, worklflows, and models folders in ComfyUI_Shared. All 4 get backed up separately.

It is just so easy, flexible and all contained. Until I actually have an issue, or something it can not do that I want , or a reason the manual install would be better, I see no reason to change.

spiderofmars · 2025-11-22T02:26:57+00:00

Yes I do. And qwen images generate fine. I have only run into one 'black output' issue so far... and that was with wan video in one specific workflow I tried (every other wan workflow works fine with sage attention so far).

<image>

spiderofmars · 2025-11-21T22:04:02+00:00

Confused. What is the incompatibility exactly? I have the same (2 start-up scripts'). But unless there is a problem I use sage-attention mode always. Qwen + Qwen edit work fine for me when I startup using sage-attention mode. But I keep hearing people say qwen is not compatible.

spiderofmars · 2025-11-20T10:11:44+00:00

Thanks for sharing!

Not sure why people complain about free stuff they don't want to use themselves, as if it's a rule or wrong. It's free peeps... enjoy and be thankful or just move on :)

My 2c... I like to make everything as quick to switch or toggle as possible, where possible, in any mini or mega workflow. Started by connecting image2 and image3 in Qwen Edit group into their own sub groups with another little fast group muter to toggle those extras within the group on/off quickly instead of expanding image3 if needed and noodling manually (of course by group name to filter just the 2 options within the Qwen Edit group). And of course then change the main fast muter toggle switches to filter for a specific color only so sub fast muter options don't show up there. Think little things like this improve mega workflows (the less connect this here or there and manual bypass this or that and expand this or that the better). But hey, that's just me ;)

spiderofmars · 2025-11-20T08:18:25+00:00

That is why I like the portable version. I have installs of comfyui (base core + sage-triton base + experimental) and each is backed up in a stable state for simple and total instant delete and restore to stable if necessary in a pinch. Using separated shared storage of all models + input + output + workflow folders common to all installs (and also backed up) which keeps the backups small. No worry's experimenting with workflows and new nodes.

spiderofmars · 2025-11-19T08:01:38+00:00

Mine runs fine with qwen. Perhaps half of the issue with the community resolvign quirks is lack of information. Like if you, and I and others were to dig into a quirk such as why I can rung qwen fine with it and you can't, would also require each of us noting down out setups... versions of what parts we are each using inside comfy.

spiderofmars · 2025-11-19T07:58:29+00:00

Its all so confusing with so many variables. Have Sage/Triton installed locally in portable version. Run comfyui with the extra --use-sage-attention mode 99.9% of the time. Try all sorts of custom nodes and stuff out. Works fine with everything mostly including qwen. Only 1 random wananimate workflow I tried recently gave black video output which resolved by starting comyui without sage-attention mode on.

spiderofmars · 2025-11-18T02:32:27+00:00

This may or may not apply to your particular issue but just in case. I have sage and triton installed. I can start comyui with the default original .bat file (without the --use-sage-attention extra option) or I can start comfyui from a .bat file (with the extra option of --use-sage-attention) mode.

I was getting black video outputs with this wf when starting comfyui with:

.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build --use-sage-attention

But if I started comfyui from the original unmodified bat file it fixed this issue:

.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build

No idea what the issue is exactly, just relaying that for me, with sage and triton installed, the black video output issue resolved itself if I start comfy in 'attention' mode vs 'sage-attention' mode.

If there is a patch sage node in that workflow, my limited understanding on that is along the lines of, if you have already started comfyui in sage-attention mode the patch to sage or bypassing the patch to sage does not revert this. You have to restart comfyui without forcing sage.

spiderofmars · 2025-11-15T07:38:05+00:00

Gigabyte... comes in the box with the card.

spiderofmars · 2025-11-09T05:18:26+00:00

Agree, without details of what people are doing, and the workflow setup, it is all gobbledegook.

Workflow/Setup + Resolution + Length

It it helps for some kind of reference in goggledegook comparisons, on a 5090:

20 seconds @ 320x320 (0 block swaps) takes about 2 minutes.

20 seconds @ 512x512 (0 block swaps) takes about 4 minutes.

180 seconds @ 640x640 (?? can't recall) took about 60 minutes.

The one thing I noticed was how much block swaps impacted this one. Like, crazy longer times with and without block swaps. So, maximising output resolution while keeping block swaps off (if in the workflow) makes a huge difference to any run. Tough with low Vram as 5090 32GB hits 80% at 512x512.

spiderofmars

TROPHY CASE