I have some doubts about this, but I'll try tonight.Hey for the guys that we’re having problems with the mv-1fs board can you try and tune your 5v line to 4.6 reading directly on the Jamma edge of the board. Since I have dropped the voltage, I haven’t seen any problems, no boot problems, no switching games or to the menu problems, nothing at all. I’m curious to see if that will fix your problems too.
Yeah I know but I haven’t adjusted anything besides the voltage and it’s been good. I won’t have a chance to check things out again till probably tomorrow night (unless we finish early at bowling tonight). I’ll put the voltage back up to 5v and see if I get the errors again (I should have done that last night but I was having to much fun playing the games I’v nevered played before). I also did the menu update yesterday and seems like all the games were there, I didn’t count them to make sure but windjammers was there and it worked great.really? That makes little sense but if it works...
Is that the only error you have? That voltage thing is supposed to fix resets or games not loading.I just gave it a try. 4.6v on jamma side and I still have the green unibios error screen on kof98![]()
ok, so I dropped the voltage down to 4.6 as measured on the JAMMA edge and to my surprise I was able to play for a solid hour with 0 issues on my MV1FS.Give it a try. Pulling down the voltage to 4.5-4.6 can't break anything.
Yea its not my boards, and I've tested 4 different microSD cards now... It really seems like something is different with this final vs the beta that had no pixel glitch.Were any changes made to the final hardware or were any components substituted with a different manufacturer? Maybe the flash memory?
Yes I've used all the files available to me...@jassin000 do you still have a copy of the firmware & menu that the proto was using?
Yes I've used all the files available to me...@jassin000 do you still have a copy of the firmware & menu that the proto was using?
The issue remains the same, stuck/wrong pixels at fixed locations on the screen.
- The version of the menu the beta cart was first running when I recieved it
- The version of the menu I updated to in helping Darksoft test
- The latest version of the menu that was just released (I never got to test this on the beta cart).
All other cart functions are identical to what I experienced on the beta.
No I haven't yet, will try this tonight. Very strange though...ok, so I dropped the voltage down to 4.6 as measured on the JAMMA edge and to my surprise I was able to play for a solid hour with 0 issues on my MV1FS.Give it a try. Pulling down the voltage to 4.5-4.6 can't break anything.
Eventually it did get stuck in a bootloop on slot 3, but up until that point I played and changed slots and flashed new games etc. and even chose games that caused me issues before but nothing... it all worked great until a little over an hour in with the one boot-loop issue.
Maybe the other MVS models have some kind of power conditioning circuit that the MV1F(S) lacks? I'm not entirely sure what to make of this...
@Sp33dFr34k have you tried this?
I believe the way it works is that you specify what you want and they use that product or an equivalent? I could be wrong.Starting to sound more and more like flashcart issues.
Perhaps the build house decided to sub in different spec parts.
You, me and @waiwainl are in the same boat..So I have the "missing pixels" glitch when using the final cart with both of my 1FZ's...
This is troubling because when using the beta cart both 1FZ's were fine.
Ok so now I've tested with a Sandisk 16gb Ultra and a Samsung Evo 32GB, still have the pixel glitch.![]()
All other cart functions are working identically to the beta.
Don't forget about @MilspexYou, me and @waiwainl are in the same boat..So I have the "missing pixels" glitch when using the final cart with both of my 1FZ's...
This is troubling because when using the beta cart both 1FZ's were fine.
Ok so now I've tested with a Sandisk 16gb Ultra and a Samsung Evo 32GB, still have the pixel glitch.![]()
All other cart functions are working identically to the beta.
![]()