Announcement

Collapse
No announcement yet.

using new smoke v1.05

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • using new smoke v1.05

    There was never any reason to post about smoke in the past, if just worked perfectly, but after installing smoke v1.05 I can't make it working. no matter what resolution I set I get this:

    "Failed to allocate offscreen textures,
    probably due to insufficient free video memory.

    Try selecting a smaller video mode or decreasing
    the color depth."

    That happens in windowed and fullscreen mode.

    My machine is Toshiba Satellite Pro 4600 with Win2k SP2.
    Trident Cyberblade XP.

    As mentioned before all old versions supported 1024x768 no problem.

    Btw. I can't run MD with that graphic card. again no resultion is working.

    any help appreciated.

    Cheeers,
    Otto

  • #2
    It sounds like that card just can't create a texture that you can render to [as opposed to just rendering directly to the frame buffer]; both MilkDrop and [the new] Smoke do this. Smoke tries first to make a 1024x1024 texture; if that fails, 512x512; and if that fails, it goes for 256x256. I doubt it's true that your card can't afford that much texture memory; more than likely, it just can't create a texture that is also a render target. Some very old cards/chipsets have this limitation, unfortunately.

    Have you tried updating your video driver? It's very possible that that could fix it...

    Good luck,
    -Ryan

    Comment


    • #3
      Wow, Ryan himself answered....

      I think I'm using the latest drivers I can find (and I have looked with Toshiba , HP and the others that OEM this graphic card.)

      Can you confirm you have changed that part of the code in Smoke as it worked perfectly with all older Smoke versions.

      Btw. Monkey beta9 works on the same machine !!! Any news on that awesome new plug-in?

      and this is the debug output:

      [smoke debug file]
      Ini file path is:
      d:\Program Files\Winamp\Plugins\smoke.ini
      MMX: found
      Init: current Windows display mode uses 16-bit color
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fbf8
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fbe4
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fc18
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fbc8
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fc04
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fc04
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000908
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000000
      [MSG] hwnd=00950784, msg=, w=000001fe, l=03a6f150
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000000
      [MSG] hwnd=00950784, msg=, w=000001fe, l=03a6f150
      [MSG] hwnd=00950784, msg=, w=06010934, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6fc04
      [MSG] hwnd=00950784, msg=, w=00000000, l=01f802a0
      [MSG] hwnd=00950784, msg=, w=00000000, l=00400040
      Init: creating main DirectDraw object
      Init: setting cooperative level
      Init: creating primary surface
      Init: getting ddraw caps
      Init: creating clipper
      Init: creating backbuffer
      Failed to allocate offscreen textures,
      probably due to insufficient free video memory.

      Try selecting a smaller video mode or decreasing
      the color depth.
      [MSG] hwnd=00950784, msg=, w=00000000, l=007f079c
      [MSG] hwnd=00950784, msg=, w=000001fe, l=03a6e798
      [MSG] hwnd=00950784, msg=, w=00000000, l=007f079c
      [MSG] hwnd=00950784, msg=, w=007f079c, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=000001c0
      [MSG] hwnd=00950784, msg=, w=00000001, l=00000000
      Finish: starting cleanup...
      Finish: releasing backbuffer
      Finish: backbuffer released
      Finish: releasing primary surface
      Finish: primary surface released
      Finish: releasing main directdraw object
      Finish: main directdraw object released
      Finish: destroying main window
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6f79c
      [MSG] hwnd=00950784, msg=, w=00000000, l=03a6f79c
      [MSG] hwnd=00950784, msg=, w=00000000, l=00000000
      [MSG] hwnd=00950784, msg=, w=00000000, l=00000000
      Finish: main window destroyed
      Finish: cleanup complete.
      Finish: starting cleanup...
      Finish: cleanup complete.


      Cheers,
      Otto

      Comment


      • #4
        I actually encountered the same error. I have a W2K Dell Latitude C800 ATI M4 32. Tried DirectX reinstalls and older/latest video driver combos. Nothing worked.

        Ran dxdiag (duh, should have done that first) and got an immediate dialog box stating that NetMeeting is running and Direct3D hardware acceleration may not function. You also see this error under the Display tab in the diagnostic tool. So I simply killed NetMeeting and my visuals worked fine.

        Should have guessed it was NetMeeting since NetMeeting gave me issues with my DVD decoder because it grabs the overlay and holds on to it.

        Comment


        • #5
          Wow. What bad, bad, BAD programmers they are! How irresponsible! That's really annoying. Thanks for tracking this down; I'll try to verify it and update my plugins accordingly. ARGH.

          Cheers,
          Ryan

          Comment


          • #6
            Here's some more info about rat-bastard NetMeeting:

            Eventhough I chose the option for NetMeeting not to run automatically in the background when Windows starts up, it still allocates the DirectX resources!

            The resolution is to open Netmeeting, and then exit it to release the resources before running the plug-ins. Then everything will work fine.

            I can see a process called conf.exe that spawns when NetMeeting is kicked off. It's there on boot up also, but directly killing the process does not free up the resources. You have to open and exit NetMeeting as stated above.

            And of course, for me I have to keep NetMeeting on my computer... damn Microsoft.

            Hope this info helps.

            Comment


            • #7
              Interesting, I don't have Netmmeting on my machine.

              I ran DXdiag and din't get any error like you did.
              I use DirctX 8.1.
              The one thing I noticed is that "AGP texture acceleration" is not available. But that shouldn't cause the trouble.

              @aweather: Did Smoke 1.04 work while Netmeeting was running?

              Btw, I tried the new 1.05b, no luck.

              Otto

              Comment


              • #8
                I've also had no problem with previous versions but I've has similar problems with v1.05.

                Comment


                • #9
                  bibbouk,
                  try using v1.06. works good for me now.
                  cheers,
                  Otto

                  Comment

                  Working...
                  X