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

Thorsten Zimmermann

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. %TEMP%\AffinitySetup was not found I then retried the install and it went through. *shrug* Maybe the reboot (had the PC turned off over night) did the trick. Was just baffled because Photo and Designer updated flawlessly, without the need for a reboot. Publisher, as third in this sequence of updates, showed the described behavior. As said, all good now. Thanks for the input all. It might come in handy at a future time.
  2. I re-downloaded the exe-installer multiple times. The Error persists. Setup File may be corrupter on Server Side. Windows 10 64 Bit Professional
  3. it's over a year now. still can't work with Stream Deck and exe recognition. Had to come here to find a work around for even the simplest thing: LAUNCHING affinity apps. **push**
  4. the files are auto named by Stable Diffusion according to their prompts - you invested a lot of mind reading into your lengthy answer. mind reading isn't a basis on which tackling tech-issues seems a worthwhile endeavor. v2 can't deal with >256 chars filenames. full stop. I said from the get go that a discussion about how and why and why not the filenames are lengthy is not leading towards a technical solution. yes, filenames can be altered, they can be lengthened, shortened, renamed, recomposed, translated, turned into a rhyme, turned into numerics, uppercases, lowercases. why are we having this discussion, I already said it's stupid. v2 needs a fix to handle these filenames, since much inferior "windows" applications do not seem to have an issue with them, there's no argument to be made why the awesome Affinity v2 Suite should be the incapable standout.
  5. no other program seems to have a problem loading these files. just the affinity v2 suite. that's all I'm saying. So saying "that's a windows thing", just doesn't sound correct, when no other 'Windows Application' seems to have a problem loading these exact files.
  6. I think I solved it: It appears to be the filename length. Files with a filename longer than 256 Chars cannot be dragged and dropped into the v2 Suite, nor can they be opened via Ctrl+O open dialogue. If you adjust the filename to be shorter than 256 Chars, then files can be drag'n'dropped and also open fine via Ctrl+O. Of course it would be nice to get this fixes, as those files have long filenames for a reason and truncating the descriptive Filename isn't really an acceptable workaround.
  7. I can confirm this behavior. I can't drag and drop any images into v2 Testversions. Neither from Total commander nor from regular Windows Explorer. This applies to all Applications. Photo v2, Designer v2, Publisher v2. No Program is running as Admin. Windows 10 64bit Professional
  8. incredible that this still hasnt been done... 15 Month later now... and still just a warning, without a "take me to issue" button...
×
×
  • 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.