Ya im a windows user, I eventually figured out it needed a unix, but even after emulating a ubuntu it got to a point that exceeded my limited knowledge.
Sorry to hear that. If you can tell me exactly where you got stuck I can try to help spell it out. It's easy for me to forget how hard it was for me to get comfortable in Unixes back when all I knew was win32, and my build env has some complicated stuff going on (particularly for mobile builds).
as for the image pack the official one works for me but the one provided in this thread does not, and im windows 10.
Have you checked the debug logs? My flash builds are always made with debugging code enabled.
(for future reference, I got this info from Adobe's site,
You must be registered to see the links
To get a log, you'll need to create an mm.cfg file and use
You must be registered to see the links
. On that page, it's called "the Flash Player projector content debugger."
Your 'mm.cfg' should contain:
Code:
TraceOutputFileEnable=1
ErrorReportingEnable=1
You should put 'mm.cfg' in:
Windows:
(example: C:\users\username\mm.cfg)
Mac OS (OS X):
Code:
/Library/Application Support/Macromedia/mm.cfg
Most Linux distros:
All messages will be recorded in 'flashlog.txt,' which is located in:
In windows:
Code:
%APPDATA%\Macromedia\Flash Player\Logs\flashlog.txt
(in Vista and up, that'd translate to C:\Users\username\AppData\Roaming\Macromedia\Flash Player\Logs\flashlog.txt)
In Mac OS/OS X:
Code:
/Users/username/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt
Most Linux distros:
Code:
/home/username/.macromedia/Flash_Player/Logs/flashlog.txt
One more thing; I'm curious how much ram you have. I compress my builds differently so it's possible you don't have enough ram for the flash player to uncompress it successfully.
