Jump to content
You must now use your email address to sign in [click for more info] ×

simono

Members
 View Profile  See their activity

  • Posts

    132

  • Joined

  • Last visited

 Content Type 

Everything posted by simono

  1. simono
    In the meantime I have found out that you can actually click on a layer bar during macro recording and a pop-up comes up with possible navigation commands. This is not the way it used to work quite some time ago. In the old version you had to go into the menu system and use menu commands instead of point and click. In the current version the developers seem to have forgotten to bind in the now more or less obsolete menu commands for navigating the layer stack. And I might mention that these stack navigation command DID exist in the menu tree. I used them - more precisely - I had to use them - for all my macros. It used to be the only way.
  2. simono
    Navigating to various layers during macro recording does not work any more. For example - select top layer leads to the message "Cannot record "Set current selection" which does not make any sense. The same goes for other layer selection like select bottom, select next, select previous. This makes recording a new macro practically impossible.. If I switch off the recording, the various navigation commands in the menu for the layer stack actually work. But they do not work as soon as I switch on the recording operation. (Red button.) I might mention that I have recorded quite a few macros in the past. But not within the last two years, so I do not know how long this problem already exists. Old macros out of my library still seem to be running OK.
  3. simono
    I am experiencing the same problem.
  4. simono
    In the meantime we have figuered out where this strange mix of old lamps and new lampes has come from. This laptop was upgraded from Windows 8.1 to Windows 10. The promise given was new lamps for old. At the time, however, quite a lot of new lamps were simply not available and the new Windows did its best to accommodate old drivers. In the aftermath neither Microsoft, Intel nor Driver Easy managed to really rectify the situation. If we would have formatted the disk and installed Windows from scratch last week, the problem would have vanished. But if a user is on a single machine and is the proud owner of three dozen or more applications requiring three dozen or more activation codes this is not a feasible path. I expect that most of your trial customers using a machine that had been upgraded to Windows 10 will have had similiar problems and - rather unfortunately - decided not to buy a non-functioning product. But at least Affinity starts up now with your mod in place.
  5. simono
    Hi Mark DDU does resolve the issue. The only problem is that the average user will be scared to death by just looking at the 1980-type user interface with all its options, settings, warnings and disclaimers. If this hadn't been on my "old" system I probably wouldn't have plucked up the courage to start it myself. Having run it - it takes quite a long time - Affinity Photo started normally and even allowed using acceleration. After that, the Intel driver update utility told me to update my graphics driver to Feb 21, which I did. This also took a supiciously long time and had to be run in two stages. It seems that DDU is not quite up-to-date. At the end of the day - all was well. The latest driver was in place and Affinity Photo was running perfectly. There is just one funny thing. The DDU people present themselves as partners to Driver Easy and highly recommend Driver Easy. That's just the utility that I had in place and that did not suceed in keeping my graphics driver cum supporting stuff in running order. Just for your info, my "new" HP system is also up and running. The bluescreen of death problem when running Affinity went away after I performed a BIOS update. Also quite an adventure. 😊 Thanks for your help and info. (Please take heed of what I wrote about allowing the user to choose the graphics platform.)
  6. simono
    One can actually see which GPU is being used in the Task Manager.
  7. simono
    By the way, according to hearsay Topaz has a problem with GeForce. But Topaz needs Intel anyway because of openVINO. Without the latter, their stuff is too slow on most machines to be of much use. With openVINO - wow! That's why I need to keep Intel in the circuit.
  8. simono
    Sure, I realize that I am up against a driver cum Windows bug. However, using Affisity I cannot choose which platform to use - Intel or GeForce. Wondershare Filmora allows me to choose. Topaz Sharpen AI allows me to choose and even provides a "calibrate" to find out which platform is faster. Affinity Photo does not. It just tells me that two platforms happen to be there. However, the user may want to - or even need to - choose which platform to use. I do not even know which platform Affinity is using - which makes debugging driver problems in a mult-platform environment almost impossible. Having ditched my old laptop due to unresolved Intel driver issues, I am now on a brand new laptop and not getting one damn' jota any further. My bluescreens are all identical, according to Bluescreen Viewer. They come up over watchdog and seem to be all Direct X related. These bluescreens may be HP specific and the result of a particular Windows update. Up to now, they have only occurred when using Affinity Photo.
  9. simono
    This is off topic, but I do not know how I can otherwise reach out to @Mark Ingram. I am on a new system - see my thread Frequent Bluescreens of Death. The new system is an i7 and has an extra getforce graphics card - i.e. it has two graphics platforms. Affinity Photo 1.9.1 does not allow me to choose the graphics card to be used fyor acceleration. It list the cards as (approx.) "Intel, GetForce" or "GetForce, Intel" depending on various Windows settings. I cannot manually select GetForce. The other programs I have allow me to choose. Wondershare Filmora 10 lists both platforms, Topaz AI Sharpen list both platforms - and I can choose in both cases. You seem to be using the first in your horizontal single field "list". This is not the way to do it. I actually need Intel - because of openVINO - for Topaz and I probably need GetForce for Affinity. My suspicion is that the Intel driver is causing Affinity to crash. That is why I must be able to choose. I cannot simply disable the Intel driver, quite apart from the fact that I need the Intel platform to get a desktop using a lower resolution to get larger, more readable fonts under icons, in menus etc.
  10. simono
    That's why I included a sysinfo - with the event log. It is not really that probable that there's a hw failure. The only software displaying the problem is Affinity. Filmora along with Topaz Sharpen AI both work perfectly. And here's the appropriate Windows Memory Dump MEMORY.DMP
  11. simono
    Having invested infinite amounts of money to migrate to a modern system - my previous system had a bad Intel graphics driver and Affinity Photo had a problem in conjunction with opencl - my new confiiguration keeps getting a bluescreen using Affinity Photo 1.9.1.979. At some time in the middle of every edit the program crashes taking the system with it. I get the infamous Bluescreen followed by an automatic re-boot! When it happens and where it happens is completely unclear. Up to now this has happened at least half a dozen times over the past three or four days. Other programs I am using have not crashed up to now. These being mainly Filmora X and Smartshow3D. Affinity crashes in one out of four edit sessions. The memory RAM usage slider in Preferences is standing on 8191 MB A sysinfo is included. sysinfo2 Simon.Payne@t-online.de.txt
  12. simono
    Sure, but check dependencies was about the only useful thing I could do. I was hoping that there might be something missing that I could pull in.
  13. simono
    So there we have it. The other night a poltergeist came down the chimney and switched off all my file extension displays. Ergo - dependenciesGui.exe.config became dependenciesGui.exe. The real "dependenciesGui.exe" works. However I cannot find anything wrong. Nothing in the DLL hierarchies seems to be missing. In other words, all is well and any malfunction must be a fata morgana. Or at least, not the result of a missing component. To sum it up - all I really know is that all available Intel graphics drivers newer than 2018 do not work for openCL on my (old) machine. This statement holds for the latest driver pulled in by the special Intel utility I downloaded off their website for finding and installing Intel drivers.
  14. simono
    997 starts up ok. If you try to enable HW acc. in Pref. - note: the checkbox is enabled - you get a message telling the highly estimated user that he, she or it is sitting on a crappy Windows version. 😊 Hmm. Isn't that always the case?
  15. simono
    997 starts up ok. If you try to enable HW acc. in Pref. - note: the checkbox is enabled - you get a message telling the highly estimated user that he, she or it is sitting on a crappy Windows version. 😊 Hmm. Isn't that always the case?
  16. simono
    You're right. But I cannot get the new version to run. Visual Basic Express keeps coming up and displaying a config file when I click on dependenciesGui.exe in the unzipped directory.
  17. simono
    Here's a new piece of information, for what it's worth. 🙂 Dependancy Walker crashes on cltest.exe. On photo.exe it complains that modules are there, which are neither 32bit nor 64bit and then also crashes. Has to be hard terminated. Running on several DLLs, picked at random, DW produces as expected a load of information. Hmmm. This is funny because DW - IMHO - does not start anything at all. It's just checking entries made by the compiler about external references for the linker/builder.
  18. simono
    That's the version that Intel installed. "Latest version". 18.02.21 27.20.100.9316
  19. simono
    The new driver - Feb 2021 instead of Jan 2021 - displays exactly the same problem. Cltest croaks on the platform count and Affinity Photo deos not get past the squid. In the meantime I have migrated to a new laptop. 800 Euros. Interestingly enough Affinity sees the two graphics platforms - separated by a comma. However, the user has no choice option to select a specific card.. Peculiar. Of course, everything works - approx. twice as fast as before. Affinity, Filmora and even Topaz Sharpen.
  20. simono
    The problem is that on their new Affinity version Serif is now going through openCL to talk to the graphics chip, which is actually quite a good idea. However! Certain combinations of Intel + openCL will not always work as they should. If you had 1.9.1 up and running, you could have gone into Edit -> Preferences... -> Performance and switched off [ ] Enable OpenCL compute acceleration Then you might have had a few crashes less. Definitely still worth a try if you haven't already tried it. If Affinity - without OpenCL (Intel) acceleration enabled - still goes on crashing, at least you then know whose nose you have to punch!
  21. simono
    I suppose you set your int iReturnValue = -1 prior to calling iReturnValue = clTest() and put the call in a try - catch framework, just in case the call itself did not work - wrong path, installer misplaced it, wrong user, no execution permision, disk just gone down the drain, boris johnson didn't like it, etc., etc., ... But I have a feeling it is probably something a little more complicated. I wonder what Intel says to the dump and the fact that openCL has not worked on this quite common Lenovo Ideapad 110 (i5) for the last two years. Or ................ .......... you have a corona-fired module-compile-"Hermione wasn't in today"-build-balls-up. Your code is simply not in there. On the other hand, here is some interesting reading. https://stackoverflow.com/questions/43241488/opencl-clgetplatformids-causes-access-violation-only-when-ran-from-visual-studio4 (A son of mine is actually programming on .NET. These strange things happen when c# is calling routines in DLLs depending on DLLs depending on DLLs that don't happen to be there. I'll be trying the dependancy walker on my stuff here to see if any DLL is actually missing. I would like my openCL to work.)
  22. simono
    I suppose if you use two absolutely non-default error codes - e.g. 91 good and 92 bad - there should not be a problem. No matter how it croaks or does not croak - 92: successfully found to be bad, 91: successfully found to be good, 0, -1 or anything else: test did not succeed. We assume "bad". Just using a simple True or False could miss out. Internally we seem to have three states.
  23. simono
    I have now added a sysinfo file to my cloud. Windows is a moving target and there have been a few updates.
  24. simono
    I presume that you are returning an appropriate error code in your test exe. Maybe nobody is bothering to check it in the main application.
  25. simono
    But now we seem to have a driver problem. The event says "device not started". On the other hand, the device is reported as working perfectly. Beim Start des Geräts PCI\VEN_8086&DEV_5916&SUBSYS_39E817AA&REV_02\3&11583659&1&10 ist ein Problem aufgetreten. Treibername: oem91.inf Klassen-GUID: {4d36e968-e325-11ce-bfc1-08002be10318} Dienst: igfx Untere Filter: Obere Filter: Problem: 0x15 Problemstatus: 0x0
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

 Accept Cookies  Reject Cookies