|
bemused0
Artist
Posts: 22
|
<class XFW::OSCallError> ::SetFocus(handle 003B0514)(window <class Controls::Form>@0012CB44) failed with error code 0x0000007E: The specified module could not be found.
Error is repeatable.
Condition:
The result node is currently selected, clicking on "Actual Pixels"
without all of the required inputs causes an abrupt crash, and does not trigger the error report assert.
-Should throw an error yelling at me for not having a full set of inputs.
|
| Posted: May 28, 2006 1:14 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
Can't repeat it -- could you describe it step by step? Here's an example:
1. Create a new filter
2. Select the Result component
3. Choose View > Actual Pixels from the main menu
4. ...
5. ...
and so on, you get the idea.
|
| Posted: May 28, 2006 1:48 pm |
Details
E-Mail
|
|
bemused0
Artist
Posts: 22
|
sorry was in a rush should have been more detailed.
1. Create a new filter
2. Set type to 'Surface'
3. plug anything into 'Surface Color' (ie gradient).
4. nothing is plugged into height
5. zoom (making the 'Actual Pixels' button available)
6. Click ' Actual Pixels'
7. crash
Also tried step 4. with something plugged into height, also crashed.
It doesnt seem to matter much what I plug into the Surface Color and Height inputs, it still crashes when I hit 'actual pixels'.
After trying some variations, I can crash it by hitting 'Actual Pixels' on almost any 'Surface' I pull up...
I'll reinstall, see what happens.
|
| Posted: May 28, 2006 2:04 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
bemused0 wrote:
I'll reinstall, see what happens. |
No need to reinstall, it won't help. Two questions:
1. What were the pixel dimensions of the image you were using?
2. Photoshop or Standalone?
|
| Posted: May 28, 2006 2:28 pm |
Details
E-Mail
|
|
bemused0
Artist
Posts: 22
|
Standalone.
As far as size, I hadn't opened an Image first, (so 600x600 I would assume?)....
However, I can produce a crash pretty much anytime I hit actual pixels now (in the standalone).
Example:
1. Open filterforge
2. Select any surface (maybe, Building > Decorative Tiles 2)
3. Open Filter Editor (current)
4. click ' Actual Pixels'
5. Crash
On a dual p4 3.2ghz (sitting next to the athlon I'm reporting from).
The same problem is NOT repeatable... so its something about this computer's config to be sure.
|
| Posted: May 28, 2006 2:49 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
Can't reproduce it on my P4. Anyway, the guys will look into it tomorrow -- thank you for reporting it!
|
| Posted: May 28, 2006 2:57 pm |
Details
E-Mail
|
|
onyXMaster
Filter Forge, Inc.
Posts: 350
|
Do you use some appearance customization software (i.e. WindowsBlinds) or a custom XP theme?
|
| Posted: May 29, 2006 2:51 am |
Details
E-Mail
|
|
bemused0
Artist
Posts: 22
|
Nope on both of those, in XP I have the style set back to 'Classic Look' ala windows 95 (the bubbly stuff annoys me).
No appearance customization software, but I do use Nvidia's desktop manager(the one built into the driver).
|
| Posted: May 29, 2006 3:21 pm |
Details
E-Mail
|
|
onyXMaster
Filter Forge, Inc.
Posts: 350
|
Dual-monitor setup?
|
| Posted: May 30, 2006 12:50 am |
Details
E-Mail
|
|
bemused0
Artist
Posts: 22
|
Yes, but the computer I produced this crash on is:
Single Monitor
1.8ghz Athlon XP
Windows XP 5.1 SP2
1Gig Ram
Radeon 7900
Very different specs from my work machine..
(I think it may be an issue with that computer however, I havent been able to reproduce this crash..try as I might... on any other computer I use).
sorry 
-nicholas |
| Posted: May 30, 2006 2:32 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
This bug is fixed, expect the fix in the next update.
|
| Posted: June 20, 2006 8:11 am |
Details
E-Mail
|
