Announcement

Collapse
No announcement yet.

WaveEditor is slow with a lot of assets

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

  • WaveEditor is slow with a lot of assets

    So I just added roughly 200mb of assests to my project. I admit that most of them are just pngs, and will be doing some time of compression on them outside of editor, or moving them to spritesheets. I do not know exactly how long it takes since I usually stop watching it, but I would say it takes a good 15-30 minutes or more to load the project, and even now, I went to view a folder with 20mb of files, and has roughly taken 10-15minutes and still going. Currently, task manager shows that there 724mb in memory, and only using 0%-0.2%. I have 32 gb of ram in my machine.

    In fact, right now it is not responding just loading the 20mb folder to view.

    Now, I am sure there are things that I can do to speed it up, but is there something that you can do in WaveEditor to make it faster?

    Thanks,
    Last edited by zaryk; 09-16-2016, 12:46 AM.

  • #2
    So last night I was able to compress my images by 19mb. Today, I open up the WE project. Debug console shows the .winfo being exported. It took nearly 30 mins to finish exporting them. Clicking through the 20mb folder I mentioned before it is quicker, but after 3 folders, WE has a runtime error and craashes with the below. Eventvwr is not much help from my perspective:

    Version=1
    EventType=APPCRASH
    EventTime=131185388012303668
    ReportType=2
    Consent=1
    UploadTime=131185388015423402
    ReportIdentifier=91b8ee49-7c5d-11e6-8196-f0def1f1bf16
    IntegratorReportIdentifier=53887b6c-c7cd-422b-b631-6ac9affe50a6
    WOW64=1
    NsAppName=WaveEditor.exe
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=WaveEditor.exe
    Sig[1].Name=Application Version
    Sig[1].Value=2.2.1.85
    Sig[2].Name=Application Timestamp
    Sig[2].Value=57600154
    Sig[3].Name=Fault Module Name
    Sig[3].Value=KERNELBASE.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=10.0.10586.589
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=57cf9bf1
    Sig[6].Name=Exception Code
    Sig[6].Value=c0020001
    Sig[7].Name=Exception Offset
    Sig[7].Value=000bdb18
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.10586.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=f0aa
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=f0aadd6a0c7c0fc00fa8a7fc9801f28c
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=fb2e
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=fb2ea404078393ef5cee0417bc9afa15
    UI[2]=E:\Program Files (x86)\WaveEngine\v2.0\Tools\VisualEditor\WaveEdito r.exe
    UI[3]=WaveEditor.GTK Windows has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program

    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=WaveEditor.GTK Windows
    AppPath=E:\Program Files (x86)\WaveEngine\v2.0\Tools\VisualEditor\WaveEdito r.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=64B1ED384ED8A6ECBFA260EB86AB6A 74

    Comment


    • #3
      Hi zaryk

      Did you refer that it takes 30 minutes during assets conversion to wpk?
      While the project is loading you can see in the Wave Editor console a list of files being processed?

      The crash happen always with the same asset or it has no relation.

      Best regards,
      David Ávila

      Comment


      • #4
        I had compressed the files using PngGauntlet. When I loaded the project, the console mentioned exporting the .winfo. It took about 30 minutes before I could do anything in the project.

        Today, I opened the project, the console didn't mention anything about exporting, and it still took 26 minutes. While it was loading, cpu usage was up 12-17. Most of my other apps are < 5. It looks like the .generateinfo file was being modified. It changed to 0kb multiple times before returning back to the accurate size. Navigating the 3 folders it stops responding on the third one. Memory Usage was in the millions. Will do a another test just on the third one to see if it will stop responding by itself.

        1) 586 pngs - 18mb
        2) 1,198 pngs - 24mb
        3) 2,059 pngs - 16mb

        ---------------------------------------------------------------------------------------------------------------------------------------------
        BTW, can the loading panel be changed so that it can be minimized or moved out of the way?


        2016-09-19 20_03_43-Content.png

        2016-09-19 20_55_56-Task Manager.png

        2016-09-19 20_03_00-Content.png

        2016-09-19 18_58_27-Task Manager.png
        Last edited by zaryk; 09-20-2016, 01:19 AM.

        Comment


        • #5
          Total # of png assets in the project is 7,916 pngs.

          When I open the 3rd folder, memory goes from 142,000 to 918,000. It does not crash or stop responding by itself. Opening all 3 folders. It still did not crash or stop responding. Memory is 1,504,176. I opened a 4th folder, and memory is 1,521,748. This time I get an error message stating "failed to allocate 131072 bytes". Pressing ok, it crashes.


          Attached Files

          Comment


          • #6
            Looks like it's running out of RAM?

            Comment


            • #7
              Summary:

              1. 16-22% cpu is used during project start, and takes roughly 30 minutes before I can do anything.
              2. Total # of png assets in the project is 7,916 pngs.
              3. It takes navigating 3 - 4 folders before the WaveEditor crashes.
              4. Only 42% of memory is used at the time of WaveEditor crashing. 32GB total in machine
              5. WaveEditor using 1.5GB at time of crash.


              I think it is more related to bad memory/File management within WaveEditor.

              Comment


              • #8
                I just did an update on WaveEditor. I had to change some of the code based on your changes.

                starting debug takes 10 minutes. Most of the time is spent in packaging the wpk and copying the files over. This may be normal, but providing information.

                Today, the WaveEditor loaded in about 20 minutes! However, most of my prefabs had error during load, so I have to see about fixing those. Nagivating folder still ends up crashing WaveEditor.


                2016-09-22 05_22_52-Shinobi_Mono_2D_Windows - Microsoft Visual Studio.png
                image_919.png
                image_920.png
                image_921.png

                Attached Files
                Last edited by zaryk; 09-22-2016, 10:01 AM.

                Comment


                • #9
                  Hi zaryk,

                  The Editor runs in 32bit mode, and its normal that it crash when 1.5gb of ram is reached (http://stackoverflow.com/questions/5...reaches-1-5-gb)

                  We will work to improve the assets management. At the moment, we recomends you to use spritesheets or another way to avoid that huge number of assets are loaded.

                  Greetings.
                  Daniel Cáceres

                  Comment


                  • #10
                    Thanks for letting me know. I will see what I can do.

                    Comment

                    Working...
                    X