So I used to be able to make decently photorealistic images using a photo reference but tonight I tried it again and the output was very plastic and off-looking. Nano Banana Pro was able to get the style right but Pro has its own set of issues and has a smaller limit.
Anyone else having this problem or more insight on this?
HONEY BADGER ACTION HERO WAGES WAR ON BIG TECH CENSORSHIP IN META-HORROR SHORTSTOFFEL IN: THE GOOGLE CONUNDRUM
Filmmaker Gary Ugarek turns real-world AI filmmaking roadblocks—undisclosed profanity filters, haywire third-party copyright triggers, and weapon-swapping glitches—into a 3-minute, 30-second-plus action-comedy promo ahead of STOFFEL vs. THE LIVING DEAD (October 2027).
PENNSYLVANIA — November 22, 2026 — Independent filmmaker Gary Ugarek today announced the release of STOFFEL in: THE GOOGLE CONUNDRUM, a 3-minute, 30-second-plus late-1990s-style action-comedy promo short born directly out of the real-world production battles behind his upcoming creature-feature STOFFEL vs. THE LIVING DEAD (slated for October 2027).
Originally generating footage on Pexo AI, Ugarek hit a wall when complex action prompts yielded an under-25% success rate—prompting him to move shop to Google Flow for its stunning 70mm-style visual polish. What Google’s filmmaker marketing left out, however, was an aggressive, undisclosed profanity filter and an overzealous third-party copyright blocker that repeatedly stalled production.
"When you’re making an R-rated action-horror comedy starring a honey badger who famously doesn't care, having an AI platform secretly slap a PG-13 muzzle on him is an automatic declaration of war," said writer-director Gary Ugarek. "My dialogue prompts kept coming back 'Failed' with zero explanation until Google’s own AI admitted there was a built-in profanity filter. I sat on the phone with Google support pitching an age-verified 18+ filmmaker toggle—not to make porn, just to make my movie—and later found whole Reddit communities dealing with the exact same brick wall while being ignored."
Rather than scrap the project, Ugarek wove the censorship battle directly into the plot: whenever Stoffel and his deadpan, hazmat-suited "Negotiator" DURDEN (Which had to be spelled DIR-DEN ot get past 3rd party filters) are inside the confines of the Google studio lot or server facility, Stoffel’s profanity is automatically bleeped—until they take an aluminum baseball bat and a Smith & Wesson Semi-Automatic to the "PROFANITY SUB-FILTER" mainframe, blow the bunker to rubble, and reclaim Stoffel's unfiltered vocabulary outside... or did they???
Behind the Scenes: Outsmarting AI Filters & Hybrid Workflows
Beating Overzealous Filters: Beyond profanity blocks, Google Flow’s third-party IP filter repeatedly flagged DIR-DIN’s yellow hazmat suit as Marvel’s Rocket Raccoon and forced Ugarek to spell "Skynet" with two T's (Skynett), swap a direct Matrix reference for a "Do you know kung fu?" gag, and get creative with phonetic spelling just to slip R-rated dialogue past the guardrails.
The Pexo-to-Flow Weapon Swap: When Flow burned through more than 10 failed attempts trying to animate Stoffel twirling and smashing a server with a baseball bat, Ugarek ran the exact same prompt in Pexo—which nailed the martial-arts choreography in one shot, but turned the bat into a samurai sword. Ugarek then fed Pexo’s clip back into Google Flow to replace the sword with an aluminum bat, manually splicing frame-grabbed screenshots to bridge Flow’s 15-second clip cap.
Dodging Trademark Headaches: With help from Google’s Gemini to dial in the prompt, Flow rendered a dead-on 3rd-Gen Camaro—which Ugarek deliberately rebadged from IROC-Z to IROC-B (B for Badger) to avoid General Motors trademark headaches.
"Here’s a piece of advice for both Pexo and Google: don’t advertise your movie making abilities if you’re going to restrain the filmmaker with a bunch of undisclosed roadblocks," added Ugarek. "Once their system catches on after watching The Google Conundrum, they’ll probably tighten the filter or kick me off—but until then, Stoffel gets the last word."
STOFFEL in: THE GOOGLE CONUNDRUM is streaming now on YouTube and Facebook. Fans can also follow production updates and support the ongoing crowdfunding campaign for STOFFEL vs. THE LIVING DEAD on GoFundMe.
Written and directed by Gary Ugarek, STOFFEL vs. THE LIVING DEAD is an upcoming independent action-horror comedy blending late-1990s theatrical action swagger with classic zombie-siege mayhem. Scheduled for release in October 2027.
Google must step up their Flow game and their usage policy.
Half of the videos hit hard rendering problems, (unable because of this, that etc.) 40% of the videos are really bad at animating , not following prompts etc.
And they charge for every rendered videos through credits. And the way omni is priced, even for ultra thats not enough credit AT all if you are really using AI as ULTRA productivity.
On the contrary, other features like Colab are best in the world, hands down.
Disappointed with Flow's performance, especially how paying customers are being charged.
I have spent 12k flow credits in the last 48 hours failing to make two ~60 second videos. These are simple explainer tutorial videos with an entirely fictional male sfw character.
It's so powerful, the videos are amazing, the speech is amazing, music, graphics, everything is amazing. But making something with continuity is a nightmare.
The video editor is so extremely hard to use and produces unexpected results... and not in the expected ways. For example I'd expect weirdness from model outputs, that's fine. But small things -- if you make a clip, extend it, clip it, change it, and delete those extensions. The prompt content from the earlier edits/extensions are still used somehow in the next generations (with no way to edit/change it). I put something specific in an extension, hated it, deleted it -- and that content appeared in all future generations of that scene, making me start over from scratch.
Moving on to the tool builder. It's an AMAZING idea but the tool builder agent is a complete idiot, and I cant edit the code by hand so a few more hours wasted. And with the content filter not allowing ANY video extensions that include a human person -- useless.
Basically gripes with every part of it. This tool could legit dominate all video spend but it falls short at the finish line.
I just spent $2k on higgsfield for worse videos with better tooling around them. Its so stupid.
Get it together google! We want to use it!
Edit: google if you read this.. the tool builder could be the most powerful tool in the entire video gen industry. You have a customizable tool, that has an embedded agent, and that embedded agent can see & hear the video content and make edits. Those building blocks lead to every objective in this domain. But the guardrails and other restrictions in it make it a pain to use and get any good results.
I see no reason why they shouldn't make this a competitor to Higgsfield or fal. ai etc like they have all the tools all the money all the resources to do so... like can they lock in please
I use Google Flow to create images for my own personal flora and fauna encyclopaedia. Well, I had a prompt that would create the exact style I wanted and used this for around a year. Then something changed in the last 1-2 days. I use the same prompt but the produced images are not the same. The new images are cold, pale, use thinner lines. I don't want that. I tried to change the prompt, I used reference images, previously created ones etc. and it doesn't change a thing. You can see an example from what I want (first one) and what it produces (second one) below. Is there any way to fix this? I was using ChatGPT for the same purpose before Google Flow and the same thing had happened to it as well.
Looking for a Google AI plan owner (Pro or Ultra—for example, a developer who only uses the coding/agent quotas and has leftover Flow credits) to share a family group slot on a monthly basis.
What I will use (and what I WON'T touch):
- ONLY Flow (generating images with Nano Banana and animating short clips) + basic chats that don't eat into compute limits.
- ZERO coding/agent usage: I won't touch Antigravity, CLI, agents, or heavy Gemini reasoning prompts, so your 5-hour and weekly rate limits stay 100% yours.
I have two accounts. In one account, the nano banana 2.1 flow works the same as usual. On the other, its mechanism is somehow entirely different, much more filtered and very inflexible. I could use the same prompts, and the results on the second one is much more cartoonish or AI looking, but the first account works fine and generated me a more surreal results. It doesn't matter how many times I generate, the mechanism on the second acc hits different. What's happening? It's like having two entirely different applications.
How could there be different mechanism on diff accounts?
I needed a place to rant about how absolutely dumb and horrible and ...(pick any phrase that can convey how insanely infuriating the implementation of these filters are...something that conveys a level of frustration that has turned an extremely nice and empathetic human into someone that is thankful they cannot find you.
I could write for weeks about filters that are so poorly designed and conservative that it makes me dislike every product and service google has to offer. A level of filters that don't even qualify for rated PG....<breath...fluffy kittens....happiest of happy thoughts>....
I am going to break down one example of my frustrations:
After many many many issues (using all the techniques and still feeling like you are scamming me to burn through the 10K credits I was an idiot to have gotten a plan for...)
Below I get one of the messages about my prompt "might" violate your policy. "Might" with no details about your super secret multi-layered filter system that is crap no matter how you slice it....
The LLM wrapper that should be catching shit and silently helping to work through your dumb filters wants to rewrite my prompt to possibly get around common dumb shit that the filter catches...
The main discovery I have found is that google hates attractive people with tattoos. As someone with tattos, It seems very wrong, but heh, as long as it is under your secret umbrella of "safety", it must be ok. Anything for the kids, am I right.
The LLM basically tells me that having specific places that you call out where a tattoo is on the body is very likely raising a flag. Body areas like hip, or leg... oooh Those people must be the worst kind of people.
Then if the clothing is something that could be sexy like spaghetti-strap or tank or mini skirt, then bring out the fucking national guard. A sexy person with tattoos and clothing that shows said tattoos has to be a massive safety risk.
[Now, never mind that if you don't call out exactly where the fucking tattoo is shown and what it looks like, you end up with one scene will have a tattoo on your leg, the next on your head, the next none at all, etc, etc, etc. The character drift is so fucking bad it is like watching a Disney mashup while on acid. And letting that happen like the LLM is setting up, means you pay again to try and fix if you really are
So...tattoo and clothing that you don't want to be changing should not be called out in a prompt because google unfairly targets people who have tattoos and are casting them in an unfair light of being potentially safety risks.]
Next, and this one is the best. A physical action, such as a kiss on the head. Paired with detailed body and clothing descriptions often trigger a policy filter!
The LLM suggest I change the ever so fucking risky and safety violation prompt of "Joy leans down and gives him a small kiss on the top of his head."
To
"Joy leans down with a small affectionate smile toward Original Me"
I am sorry, but in no way should the phrase "Joy leans down and gives him a small kiss on the top of his head" be something that needs to get changed because it indicates a possible policy violation when paired with those evil sexy people with tattoos that google has targeted for some unfair reason.
Even if some other place in the prompt said "after Joy just finished taking a big steaming shit on his chest".... there is no reason to flag and change "Joy leans down and gives him a small kiss on his head".
It is just beyond ridiculous. I mean, what is the problem with sexy revealing clothing to begin with? Have you been on the internet? Regardless, we are talking about things that don't even flag PG13. It just puts people spending hours and tons of credits (which is where you are fucking scamming people) just to break the scene up and describe it in a way that you might get a video that is still 60% of your artistic vision if you are lucky.
I've gone through thousands of credits. I have had chatGPT and Claude structure the prompts. These fucking filters are so utterly ridiculous, however, it makes me dislike the entire company.
I realize this is all over the top for a silly tool that cost real money with a verified adult who has tons of googles' products for more than 30 years. I mean, it makes perfect sense that people with tattoos and sexy clothing be classified as safety violations, especially when paired with something as shamelessly affectionate as "Joy leans down and gives him a small kiss on his head."
Note: Joy is sitting on a baby grand piano and he is sitting on the bench playing it. (even if Joy is sexy as hell, it is not fair to flag a safety risk).
Great job google flow filter admins! I didn't know how much of a safety concern I would become when I first starting getting my tattoos 20+ years ago. Had I known I would be singled out and hated by the google flow filter admins, I would have never gone down that unholy path.
Again - I realize all of above is over-the-top. I felt I needed to match the level of how insanely ridiculous these filters are.
I tried maybe 5 times, to make a 24 second video (I am using image as reference) Problem is when I get to the 3rd scene to connect the first frame I keep getting a stutter on the connect.
Is this just something it is incapable of doing or is there a way to fix it?
Would love it to look like 1 seamless loop of 24 seconds repeating.
I'm asking to know if anyone else encountered the same problem as me. Using Nano Banana 2.1, I set the image ratio at 16:9, but the results always came out at around 3:4. Why is that?
I'm struggling to generate a character that holds up a SMG gun next to her head level with the right hand. Somehow the Ai keeps generating it in the left hand no matter what wording I'm trying. I can't understand what's going on. I even asked Gemini, Grok, ChatGPT for prompts. It never gets the image right.
Sometimes, Labs got shit up their sleeve not to be believed. The latest Flow Music has left me speechless.
I'm conjuring cinematic and electronic tracks I simply cannot comprehend. - So far beyond the sonic Uncanny Valley, it's absurd.
Listen, I'm still super pissed about the forced migration to Omni 1.2. It's a thing. But this... This is the other half of the equation weaponized and straight lethal.
They don't feel it's too politically correct and sensitive. Google Flow 1.2 and expensive at the same time. I don't do anything weird, I just annoy friends by making them pass themselves off as characters from an isekai parody, haha.
So, given that that Thinking Levels are not available on a free plan for Flow, you would think they would default to Low Thinking; but no, they default to High Thinking, the very thing that mangles and destroys prompts to the max!
Over the last two days, I’ve been getting the "You are asking too fast" error after generating just a few videos and images. I'm on a Pro plan and have unused credits, so I shouldn't be capped like this?!
Hoping this is just a temporary bug—is anyone else experiencing the same thing?
Hey everyone, im trying to make a short film about a certain war and there are scenes showing shooting and action etc, basically like any war movie out there lol, but the google flow keeps telling im violating the policies, is there a way or a prompt for this? im using omni if that makes a difference
In today’s update, the way projects are sorted has changed. Projects are now sorted by the date of the last change, rather than by the date they were created.
At first, I thought my main project had been deleted. And it turned out to be right at the top of the list of projects.
For a while, whatever guardrails they put in NB2.1 largely didn’t effect NB Pro. Not sure if it hit everyone else but it is now doing it for me. Sanitized prompts now which amounts to people just standing around now. Which ultimately means wasted usage since we only get to generate 100 images in pro.