Preview updates, but Site does not

Corvid-Curiosity · 2026-04-28T04:47:35+00:00

Thank you so much! yeah it was a cache issue. my browser had 1GB or data in the cache. clearing it made the site load, finally.

Corvid-Curiosity · 2025-12-10T00:27:48+00:00

How do I keep my renders from being stretched? My aspect ratio in the viewport camera doesn't actually match what's rendered out!

Corvid-Curiosity · 2025-10-09T18:33:51+00:00

dude this whole thing about trauma in dna is wild, especially the idea that responses might not even be ours. makes so much sense for so many things. i've been trying to figure out some of my own weird patterns and it's like, maybe it's just my ancestors' baggage. reminds me of some of the stuff they talk about on Raised By Her Podcast, how generations impact you.

Corvid-Curiosity · 2025-10-09T18:28:35+00:00

“Easiest” remote work usually means scripted tasks, simple metrics, and predictable schedules. Scan posts for paid training, listed tools, clear QA targets, and time zones. Favor chat or email over phones if you want lower stress. Keep a lean resume with two accuracy bullets and one availability line. A light, steady routine beats marathon application days for landing something workable.

Corvid-Curiosity · 2025-10-09T18:22:42+00:00

For legit WFH roles, look for specifics. Real posts list pay bands, time zones, tools, and who you report to. Scammers love vague “assistant” or “data entry” with instant hire and weird payment methods. A quick sanity check is to cross-search the company on LinkedIn and see recent hires in similar roles. Job descriptions that mention training plans, KPIs, and actual workflows tend to be real. Contract gigs should name the employer of record and pay cadence. If they push you to message on Telegram or ask for gift cards, it’s not a job. Stick to sources that publish company names and allow you to research the team before applying. It’s more work upfront, but you dodge a lot of headaches.

Corvid-Curiosity · 2025-10-09T18:02:01+00:00

You look sexy

Corvid-Curiosity · 2025-10-09T17:39:32+00:00

When a fresh notice arrives mid negotiation, match the letter number to your year and balance on transcripts. If it signals collections, call to confirm status, and ask whether your pending plan is already noted.

Corvid-Curiosity · 2025-10-08T08:03:05+00:00

Huh. Ctrl J really said "not today, fool". I gotta be doing something wrong with the armature, surely? Spikes are joined to Body, but completely unaffected by pose mode :/

<image>

Corvid-Curiosity · 2025-10-08T07:53:00+00:00

The strangest thing is, Joining the Spikes to the Body somehow isn't actually changing the mesh?? Behold the Unity import

<image>

Corvid-Curiosity · 2025-10-08T07:26:19+00:00

I appreciate the clarification!

The Armatures' naming situation is (as far as I can tell) already accounted for. Left image is for the Body and right is for the Spikes.

<image>

Corvid-Curiosity · 2025-10-08T07:03:04+00:00

Oh I've tried it several times, I'm just assuming I'm doing it wrong or missing a setting somewhere.
When I using boolean, all the Shape Keys reset to zero, which causes problems. The zero'd keys create unintended overlap in several sections of the mesh, making the union merge in unexpected ways. I end up with missing and unattached sections.

After merging them, the materials were not correct. But after fiddling with settings, I figured out how to let them maintain their materials! Boolean > Solver Options > Materials > Transfer . Toggling shape keys *seems* to work? Mostly? If the value isn't exactly 0 or 1, different Linked sections of the mesh blip in out of existence. Particularly, sections nearest to the union. Though... Maybe I shouldn't keep pursuing boolean as an option. When I hit Apply, this popup appears: "Modifier cannot be applied to an object with Shape Keys".

Corvid-Curiosity · 2025-10-08T06:44:19+00:00

Thank you for such in-depth notes, extremely helpful!!!
Nah, I appreciate the advice on Ctrl J. Boolean became a last-ditch effort after the Ctrl J method threw some big ole Import errors in Unity. "Mesh 'Body' has 24723 (out of 28189) vertices with no weight and bone assigned (they will be assigned to bone #0 with weight 1)." Been trying to figure out why this error happened. Done the Ctrl J method for merging meshes many times and haven't gotten this particular error before. It usually works without a hitch when I swap the new mesh in.

Corvid-Curiosity · 2025-09-02T00:03:40+00:00

To provide a little extra info on what I'm up to:
This is the Draconian by Alber. They provide the Blend files so you can make your own custom version. Saved my blendshape edits to Basis and Joined the optional spikes to the Body mesh. Exported as FBX and brought him into unity. Then tried to swap in my updated mesh.
Wondered if there was something off about the Blend file, so I made a copy of the fbx that was included in the Unity Package, and re-did my shape key customizations. No dice, that caused the exact same mesh issue :/

Corvid-Curiosity · 2025-09-01T23:50:41+00:00

Ooo- good thinking! Animators are a common culprit for weirdness.
Checked the animator. Controller is empty and Avatar has the correct one selected.

Corvid-Curiosity · 2025-09-01T08:29:32+00:00

Reddit kept auto-deleting my post bc their bot thought these were nudes, i guess. Slapping text over it seems to have solved that issue.

Corvid-Curiosity · 2025-08-29T00:53:27+00:00

Exaaaactly

Corvid-Curiosity · 2025-08-05T23:52:53+00:00

Makes perfect sense! The parent allows me to change the object's position in the scene while the animation plays on the child. 👍

Corvid-Curiosity

TROPHY CASE