Page 26 of 30 FirstFirst ... 16222324252627282930 LastLast
Results 251 to 260 of 291

Thread: Team M33 is back | 3.52 M33-3 Released!

                  
   
  1. #251
    DCEmu Rookie jerrt's Avatar
    Join Date
    Apr 2005
    Posts
    186
    Rep Power
    74

    Default

    Quote Originally Posted by Veskgar View Post

    Also, not being able to put the PSP in sleep mode or power down by holding power slide up for 4 seconds is really annoying. It takes like 10 seconds to get the PSP to forcefully shut off.
    was this something that was intentionally added in the v3 update? i would hate that as i use the sleep mode quite often. any more info on this phenomenon from anyone else?

  2. #252
    DCEmu Old Pro mavsman4457's Avatar
    Join Date
    Mar 2006
    Location
    East Coast, USA
    Posts
    1,278
    Rep Power
    75

    Default

    Hmmm has anyone seen what PS3News has had to say about this? I would just go straight to their site but it is probably the most spyware abundant site I have ever visited in my life. And to think, I used to actually get news from there.

  3. #253

    Default

    nvm all my questions i just ran it and saw the anti ps3news site thing, and updated, and it went successfully, and the vshmenu is extremely helpful/useful

  4. #254
    DCEmu Legend dejkirkby's Avatar
    Join Date
    Feb 2006
    Age
    45
    Posts
    2,632
    Rep Power
    101

    Default

    Quote Originally Posted by jerrt View Post
    was this something that was intentionally added in the v3 update? i would hate that as i use the sleep mode quite often. any more info on this phenomenon from anyone else?
    Slepp mode seems fine on all my PSP's!

  5. #255
    DCEmu Legend
    Join Date
    Sep 2006
    Location
    USA
    Posts
    2,152
    Rep Power
    79

    psp

    Quote Originally Posted by jerrt View Post
    was this something that was intentionally added in the v3 update? i would hate that as i use the sleep mode quite often. any more info on this phenomenon from anyone else?
    Well upon further experimenting, it looks like sleep mode DOES work during both GAMES and XMB which is a relief.

    I'm not sure why I was having problems at first. Maybe its when the XMB is set to a low speed like 75 or 100, that's when sleep mode won't work.

    The built in XMB menu is amazingly convenient. Perhaps one of the biggest annoyances has been that some games need to be played at higher CPU speeds if CiSO'd to prevent lag and going into recovery was a hassle to have to do back and forth for different games. This eliminates that.

    Thanks again M33 Team!

    I just need to figure out why my SVCapture plugin stopped working on XMB, GAMES, & homebrew now. Maybe I overwrote something in the seplugins folder when updating to this latest update.

  6. #256
    DCEmu Rookie jerrt's Avatar
    Join Date
    Apr 2005
    Posts
    186
    Rep Power
    74

    Default

    dejkirkby & veskgar: thanks for the update. i'm going to update when i get home, does anyone know a good write up on playing ps1 games on the newer firmware. they talk about pops loaders, but i don't remember having to use anything special if i used ice tea to make the games from iso

  7. #257

    Default

    Okay after some investigating I have finally figured out what the problem is with not getting 333mhz in the XMB. After disabling my VSHAnalog (which switches the analog and Dpad and vice verca in the XMB) I can get 333mhz in the XMB but there still remains to be some issues. Now see I asked in my last post what the HOME button menu thing was, the reason I didn't know what it did was because while having the VSHAnalog enabled in the Recovery menu the HOME button menu wouldn't come up. The strange thing is the VSHAnalog plugin doesn't use the HOME button just the 2 volume buttons to switch between the Dpad and Analog. After disabling this I could get 333mhz but I still had small bugs, such as the mhz not staying at 333mhz (going back to 222mhz) and then freezing in the XMB. My PSP would freeze and just act funny even after disabling the plugin, so I have gotten back to 3.52 M33-2. I haven't experienced ANY of these issues with previous versions of M33 firmwares, but please someone report these bugs and hopefully we will get a M33-4 fix.

  8. #258
    Registered User NoQuarter's Avatar
    Join Date
    Dec 2005
    Posts
    2,106
    Rep Power
    0

    Default

    Veskgar,I experienced similar slow power off and sleep mode in other programs when I turned the clock speed way down.I'm pretty sure that's what it was.

    I'm still debating whether to update,I'm on m33-1,m33-2 and 3.4OE.

  9. #259

    Default

    Well when I had my XMB at 333 and then it would randomly switch to 222, after that my xmb would act funny, freeze, or the power switch just wouldn't work unless I held it for like 10secs. I think M33 needs to fix all these bugs and release a new update because I think they rushed this release or something but it has bugs that's why I went back to M33-2.

  10. #260
    DCEmu Pro MicroNut's Avatar
    Join Date
    Aug 2005
    Location
    here or there
    Posts
    777
    Rep Power
    77

    Default

    Quote Originally Posted by CaptainMorgan4 View Post
    Okay after some investigating I have finally figured out what the problem is with not getting 333mhz in the XMB. After disabling my VSHAnalog (which switches the analog and Dpad and vice verca in the XMB) I can get 333mhz in the XMB but there still remains to be some issues. Now see I asked in my last post what the HOME button menu thing was, the reason I didn't know what it did was because while having the VSHAnalog enabled in the Recovery menu the HOME button menu wouldn't come up. The strange thing is the VSHAnalog plugin doesn't use the HOME button just the 2 volume buttons to switch between the Dpad and Analog. After disabling this I could get 333mhz but I still had small bugs, such as the mhz not staying at 333mhz (going back to 222mhz) and then freezing in the XMB. My PSP would freeze and just act funny even after disabling the plugin, so I have gotten back to 3.52 M33-2. I haven't experienced ANY of these issues with previous versions of M33 firmwares, but please someone report these bugs and hopefully we will get a M33-4 fix.

    good info thank you!
    With all the plug-ins and other possibilities
    The level of complexity involved in making sure everything works is high.
    The more information everyone has the better,
    Folks can make decisions for themselves...
    Everyone should keep reporting their experiences.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •