List of issuesList of issues

#938 parallel feature keeps setting to low number, not default 20
Date created:
Type: bug
Visibility: Everybody
Assigned to: admin JPEXS
Labels: Performance
State: upgraded Help

> What steps will reproduce the problem? just opening the program. > What is the expected output? What do you see instead? when i click advance settings i see parallel is set to 2....not 20 by default > What version of the product are you using? Is it "nighlty build"? Which operating system do you have? most recent > Please provide any additional information below. If the problem is related to a SWF file, attach it here, otherwise we can't help you. I know alot of people who use this program. I literally talked to 18 people about it. Every single person had a low setting for the parallel setting. Every single person who changed it to the default 20 say the program is much faster now and they love it. Its like night and day. So why does it set it to a low number? how to keep the default setting of 20? thanks. BeStPRoGiE
just so that its clear.....not all 18 people had it set to two. But all 18 had it set to some low number. 2, 4, 5, etc..etc..
one other thing....i did search for the bug already and found one instance of parallel. Unfortunately the person figured it out themselves and it was not posted on how to fix it.
Please try nightly version 674 or later, it should be fixed. I also set default value to 10. You can increase it.
State: new→upgraded
Assigned:admin JPEXS
Thanks for the quick response....I love what you guys do here. Im going to go ahead and try the new version now and will let others know that the newest update addresses the problem. Will let you know how it goes after a day or two. Thanks again.
Hi, I have read your "If you are using jpex free flash decompiler then read" post on the fh forum now and saw people complaining about us fixing one bug while introducing another. It makes me sad a bit :-(. I know we create new bugs while implementing new features. We have unit tests for some basic stuff like AS decompilation and direct editation so this part is relatively safe. But unfortunately we cannot write tests for GUI. These problems must be "tested" manually. It would be better if more of FFDec features had unit tests, but everything which depends on GUI is very hard to test. If you have any idea how we can improve the release/testing system then please tell us! I don't like people using old versions of FFDec, because we do our best to improve our product and fix all bugs and we spend a lot of time with it (and nobody pays us) and if people then do not use it I feel like I wasted my time :-(. We have nightly builds which are compiled right from our repository and then at some point we release "stable" version. When we find critical bugs in stable, we released fixed stable as soon as possible. Then we continue with nightly builds. Do you know any better system? If yes, then do not hesitate and tell us. I would like people to use more up-to-date versions, not to be stuck with "v1.7.4 or 4.1.1". But I know... you need just edit the SWF, not to experiment with FFDec versions which one would work...
Google Translate: Translate to Czech Translate to Slovak Translate to Russian Translate to Hungarian Translate to Swedish Translate to French Translate to German Translate to Spanish Translate to Italian
Change style: oceanic classic