Many times my generation will simply say ‘stopped’ and truncate the code and cause a ton of issues. Recently this happened for 2 days in a row which cost me $60-90
Hi @graillabxyz, I’m so sorry to hear that happened. Can you share the chat ID and some examples where it costed high amounts like that for debugging purposes?
https://v0.dev/chat/newest-bloodlines-GbWS1kVo2cV
https://v0.dev/chat/fork-of-sidescrolling-game-project-AeHve3uAP1R
https://v0.dev/chat/fork-of-sidescrolling-game-project-ywZhUjmZogv
https://v0.dev/chat/fork-of-sidescrolling-game-project-gHJorpSN3Jb
https://v0.dev/chat/fork-of-sidescrolling-game-project-9Z6FrkgN89O
https://v0.dev/chat/fork-of-sidescrolling-game-project-5tKgtpddbOv
I have forked a bunch to hopefully reset the context and make debugging easier. I have spent $210 (5x$30 & 1x$60) in the last two days with almost no progress on this codebase.
Thanks for sharing these. I see you are mostly using the medium model. I’d suggest mixing in the small model and design mode to reduce the cost for smaller tasks and style changes.
Can you share the most recent message or case where you faced the issue of “stopped”? I’d also urge you to maybe record the screen or take screenshot next time you face the issue.
I will share many screenshots with you if you think that will help. I use design mode when the divs are accessible in the preview, but some instances they are not.
I think the main problem is many instances when v0 truncates my code and then tries to redesign something that it truncated poorly.
You can check my logs, I have spent a large amount of time and money using this product and have shifted over time how I have addressed certain issues. Many times there is not workaround for me other than using another platform or fixing things by hand. I have, on almost every project using v0, gotten stuck in expensive debugging loops. Granted occasionally it was my fault for not understanding the limitation of v0, but after the amount of time I have spent using this product I can understand pretty often when it is user error, or hallucination that is causing a time/credit sink.
For example I have been debugging for 2 days now, still as we speak and I have had nearly 0 progress on my project. I have even attempted to redesign from more stable results to no success.
1 Like
in this chat: https://v0.dev/chat/newest-bloodlines-GbWS1kVo2cV
Nothing of note happened to the codebase here:
The syntax error was not fixed:
Many instances where either nothing changed or things were in an endless debug loop. It feels quote extractive when I am paying credits and at the mercy of the ai hallucinating and truncating what I am working on.
This is just from 1 chat and I didnt share any of the other debug issues from that chat. From other chats sent above I have a very similar experience. I can say the same for multiple other projects that I am building with v0.
https://v0.dev/chat/fork-of-newest-bloodlines-PgoJ61Dyvrk
here is an example of a fresh chat that I just forked on a working version of the project and it immediately destroyed the project on the first prompt. I then tried to recover and ended up in a debug loop again.
I have shared only the most recent instances of this..
Seems quite unsustainable to be experiencing this as consistently as I have.
I am just wasting time and money here.
Each time it stops and creates syntax errors and truncates code. I have to fork it normally because restoring a previous generation keeps the context of the broken prompt result.
Have shared alot of screenshots and chat links as requested. Has been a few days now. Any guidance on the matter?
Hi @graillabxyz, thanks for sharing detailed prompts and images of your issues. I’ll share them with the team and keep you posted here.
1 Like
Any updates on this? It happens for 30-40% of my prompting.