Pockenfresse
-
Posts
30 -
Joined
-
Last visited
Posts posted by Pockenfresse
-
-
-
59 minutes ago, Sean P said:
Have you tried this in the latest 1.8.4.676 beta? We was able to replicate the issue with a non-display Huion tablet which has now been fixed. I don't have access to a Kamvas, but do know the Q11K v2 I have is now working.
Works perfectly fine again on the Huion Kamvas 20 Pro.
It seems also the issues with the overly sensitive anchorpoints is fixed now. Good work!
-
My bad. I meant Pen Displays. Not normal Pen Tablets. Sorry.
-
-
Mouse/Cursor dont move anymore when pointing on the pen surface. UI is still working. The Canvas is like dead. The last stable version of AD still works.
- Recent Hunion driver installed: 14.8.90.1126
- Hunion Kamvas 20 Pro
- Windows 10 Version 1909 x64
- NVidia GTX 1050 Ti
- 16 MiB of RAM (For more info see SystemInfo.txt)
Unfortantly I cant attach any files because even the forum is buggy and just shows me "7" when i want to upload files. So heres the Log.txt:
Loading colour profiles Monitors Name: BenQ GL2450 Adapter: NVIDIA GeForce GTX 1050 Ti Primary: Yes Has user profile: Yes Profile name: sRGB Color Space Profile.icm Name: Generic PnP Monitor Adapter: NVIDIA GeForce GTX 1050 Ti Primary: No Has user profile: Yes Profile name: sRGB Color Space Profile.icm System Found 11 system profiles (parsed 11) Loading colour profile (system): wsRGB.cdmp Loading colour profile (system): wscRGB.cdmp Loading colour profile (system): sRGB Color Space Profile.icm Loading colour profile (system): RSWOP.icm Skipping colour profile (system): Proofing.gmmp Skipping colour profile (system): Photo.gmmp Skipping colour profile (system): MediaSim.gmmp Skipping colour profile (system): Graphics.gmmp Skipping colour profile (system): D65.camp Skipping colour profile (system): D50.camp Loading colour profile (system): BenQ GL2450.ICM Found 11 user profiles (parsed 11) Loading colour profile (user): wsRGB.cdmp Loading colour profile (user): wscRGB.cdmp Loading colour profile (user): sRGB Color Space Profile.icm Loading colour profile (user): RSWOP.icm Skipping colour profile (user): Proofing.gmmp Skipping colour profile (user): Photo.gmmp Skipping colour profile (user): MediaSim.gmmp Skipping colour profile (user): Graphics.gmmp Skipping colour profile (user): D65.camp Skipping colour profile (user): D50.camp Loading colour profile (user): BenQ GL2450.ICM Installed Loading colour profile: AdobeRGB1998.icc Loading colour profile: AppleRGB.icc Loading colour profile: CoatedFOGRA27.icc Loading colour profile: CoatedFOGRA39.icc Loading colour profile: ColorMatchRGB.icc Loading colour profile: Display P3.icc Loading colour profile: JapanColor2001Coated.icc Loading colour profile: JapanColor2001Uncoated.icc Loading colour profile: JapanColor2002Newspaper.icc Loading colour profile: JapanWebCoated.icc Loading colour profile: ROMM RGB.icc Loading colour profile: UncoatedFOGRA29.icc Loading colour profile: USSheetfedCoated.icc Loading colour profile: USSheetfedUncoated.icc Loading colour profile: USWebCoatedSWOP.icc Loading colour profile: USWebUncoated.icc Loading colour profile: WebCoatedFOGRA28.icc Imported -- 363.1087ms TabletContext::Create: original queue size is 0 Wintab: Failed to set queue size Attempting to create Direct3D device on default adapter Setting screen DPI to 112.888888888889 (scale = 1.0) Exit
SystemInformation.txt:
Win32_OperatingSystem \\DAGOBERT\root\cimv2:Win32_OperatingSystem=@ BootDevice = \Device\HarddiskVolume3 BuildNumber = 17763 BuildType = Multiprocessor Free Caption = Microsoft Windows 10 Pro CodeSet = 1252 CountryCode = 49 CreationClassName = Win32_OperatingSystem CSCreationClassName = Win32_ComputerSystem CSName = DAGOBERT CurrentTimeZone = 120 DataExecutionPrevention_32BitApplications = True DataExecutionPrevention_Available = True DataExecutionPrevention_Drivers = True DataExecutionPrevention_SupportPolicy = 2 Debug = False Description = Intel Core i5 7600 Distributed = False EncryptionLevel = 256 ForegroundApplicationBoost = 2 FreePhysicalMemory = 12215040 FreeSpaceInPagingFiles = 2469060 FreeVirtualMemory = 11927752 InstallDate = 20181211153747.000000+120 LastBootUpTime = 20190420091837.605724+120 LocalDateTime = 20190502130406.721000+120 Locale = 0407 Manufacturer = Microsoft Corporation MaxNumberOfProcesses = 4294967295 MaxProcessMemorySize = 137438953344 MUILanguages = System.String[] Name = Microsoft Windows 10 Pro|C:\WINDOWS|\Device\Harddisk1\Partition4 NumberOfProcesses = 210 NumberOfUsers = 20 OperatingSystemSKU = 48 OSArchitecture = 64-Bit OSLanguage = 1031 OSProductSuite = 256 OSType = 18 PortableOperatingSystem = False Primary = True ProductType = 1 RegisteredUser = Windows-Benutzer SerialNumber = 00330-80000-00000-AA473 ServicePackMajorVersion = 0 ServicePackMinorVersion = 0 SizeStoredInPagingFiles = 2490368 Status = OK SuiteMask = 272 SystemDevice = \Device\HarddiskVolume5 SystemDirectory = C:\WINDOWS\system32 SystemDrive = C: TotalVirtualMemorySize = 19208816 TotalVisibleMemorySize = 16718448 Version = 10.0.17763 WindowsDirectory = C:\WINDOWS Win32_Processor \\DAGOBERT\root\cimv2:Win32_Processor.DeviceID="CPU0" AddressWidth = 64 Architecture = 9 AssetTag = To Be Filled By O.E.M. Availability = 3 Caption = Intel64 Family 6 Model 158 Stepping 9 Characteristics = 236 CpuStatus = 1 CreationClassName = Win32_Processor CurrentClockSpeed = 3501 CurrentVoltage = 11 DataWidth = 64 Description = Intel64 Family 6 Model 158 Stepping 9 DeviceID = CPU0 ExtClock = 100 Family = 205 L2CacheSize = 1024 L3CacheSize = 6144 L3CacheSpeed = 0 Level = 6 LoadPercentage = 13 Manufacturer = GenuineIntel MaxClockSpeed = 3501 Name = Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz NumberOfCores = 4 NumberOfEnabledCore = 4 NumberOfLogicalProcessors = 4 PartNumber = To Be Filled By O.E.M. PowerManagementSupported = False ProcessorId = BFEBFBFF000906E9 ProcessorType = 3 Role = CPU SecondLevelAddressTranslationExtensions = True SerialNumber = To Be Filled By O.E.M. SocketDesignation = LGA1151 Status = OK StatusInfo = 3 SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT ThreadCount = 4 UpgradeMethod = 1 VirtualizationFirmwareEnabled = True VMMonitorModeExtensions = True Win32_VideoController \\DAGOBERT\root\cimv2:Win32_VideoController.DeviceID="VideoController1" AdapterCompatibility = NVIDIA AdapterDACType = Integrated RAMDAC AdapterRAM = 4293918720 Availability = 3 Caption = NVIDIA GeForce GTX 1050 Ti ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_VideoController CurrentBitsPerPixel = 32 CurrentHorizontalResolution = 1920 CurrentNumberOfColors = 4294967296 CurrentNumberOfColumns = 0 CurrentNumberOfRows = 0 CurrentRefreshRate = 60 CurrentScanMode = 4 CurrentVerticalResolution = 1080 Description = NVIDIA GeForce GTX 1050 Ti DeviceID = VideoController1 DitherType = 0 DriverDate = 20190317000000.000000-000 DriverVersion = 25.21.14.1967 InfFilename = oem30.inf InfSection = Section106 InstalledDisplayDrivers = C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispci.inf_amd64_b87987c5cf0d5bfa\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispci.inf_amd64_b87987c5cf0d5bfa\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispci.inf_amd64_b87987c5cf0d5bfa\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispci.inf_amd64_b87987c5cf0d5bfa\nvldumdx.dll MaxRefreshRate = 75 MinRefreshRate = 59 Monochrome = False Name = NVIDIA GeForce GTX 1050 Ti PNPDeviceID = PCI\VEN_10DE&DEV_1C82&SUBSYS_85CD1043&REV_A1\4&38AB2860&0&0008 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT VideoArchitecture = 5 VideoMemoryType = 2 VideoModeDescription = 1920 x 1080 x 4294967296 Farben VideoProcessor = GeForce GTX 1050 Ti Win32_PhysicalMemory \\DAGOBERT\root\cimv2:Win32_PhysicalMemory.Tag="Physical Memory 1" Attributes = 1 BankLabel = BANK 1 Capacity = 8589934592 Caption = Physikalischer Speicher ConfiguredClockSpeed = 2133 ConfiguredVoltage = 1200 CreationClassName = Win32_PhysicalMemory DataWidth = 64 Description = Physikalischer Speicher DeviceLocator = ChannelA-DIMM2 FormFactor = 8 InterleaveDataDepth = 2 InterleavePosition = 1 Manufacturer = Corsair MaxVoltage = 0 MemoryType = 0 MinVoltage = 0 Name = Physikalischer Speicher PartNumber = CMK16GX4M2A2400C16 SerialNumber = 00000000 SMBIOSMemoryType = 26 Speed = 2133 Tag = Physical Memory 1 TotalWidth = 64 TypeDetail = 16512 \\DAGOBERT\root\cimv2:Win32_PhysicalMemory.Tag="Physical Memory 3" Attributes = 1 BankLabel = BANK 3 Capacity = 8589934592 Caption = Physikalischer Speicher ConfiguredClockSpeed = 2133 ConfiguredVoltage = 1200 CreationClassName = Win32_PhysicalMemory DataWidth = 64 Description = Physikalischer Speicher DeviceLocator = ChannelB-DIMM2 FormFactor = 8 InterleaveDataDepth = 2 InterleavePosition = 2 Manufacturer = Corsair MaxVoltage = 0 MemoryType = 0 MinVoltage = 0 Name = Physikalischer Speicher PartNumber = CMK16GX4M2A2400C16 SerialNumber = 00000000 SMBIOSMemoryType = 26 Speed = 2133 Tag = Physical Memory 3 TotalWidth = 64 TypeDetail = 16512 Win32_DiskDrive \\DAGOBERT\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE4" Caption = Generic- SD/MMC USB Device ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_DiskDrive Description = Laufwerk DeviceID = \\.\PHYSICALDRIVE4 FirmwareRevision = 1.00 Index = 4 InterfaceType = USB Manufacturer = (Standardlaufwerke) MediaLoaded = True Model = Generic- SD/MMC USB Device Name = \\.\PHYSICALDRIVE4 Partitions = 0 PNPDeviceID = USBSTOR\DISK&VEN_GENERIC-&PROD_SD/MMC&REV_1.00\20021111153705700&2 SCSIBus = 0 SCSILogicalUnit = 2 SCSIPort = 0 SCSITargetId = 0 SerialNumber = 20021111153705702 Signature = 0 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT \\DAGOBERT\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE1" BytesPerSector = 512 Capabilities = System.UInt16[] CapabilityDescriptions = System.String[] Caption = Samsung SSD 850 EVO 250GB ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_DiskDrive Description = Laufwerk DeviceID = \\.\PHYSICALDRIVE1 FirmwareRevision = EMT02B6Q Index = 1 InterfaceType = IDE Manufacturer = (Standardlaufwerke) MediaLoaded = True MediaType = Fixed hard disk media Model = Samsung SSD 850 EVO 250GB Name = \\.\PHYSICALDRIVE1 Partitions = 4 PNPDeviceID = SCSI\DISK&VEN_SAMSUNG&PROD_SSD\4&BFDEFCD&0&000300 SCSIBus = 0 SCSILogicalUnit = 0 SCSIPort = 0 SCSITargetId = 3 SectorsPerTrack = 63 SerialNumber = S2R6NX0HC39988J Size = 250056737280 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT TotalCylinders = 30401 TotalHeads = 255 TotalSectors = 488392065 TotalTracks = 7752255 TracksPerCylinder = 255 \\DAGOBERT\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE2" Caption = Generic- Compact Flash USB Device ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_DiskDrive Description = Laufwerk DeviceID = \\.\PHYSICALDRIVE2 FirmwareRevision = 1.00 Index = 2 InterfaceType = USB Manufacturer = (Standardlaufwerke) MediaLoaded = True Model = Generic- Compact Flash USB Device Name = \\.\PHYSICALDRIVE2 Partitions = 0 PNPDeviceID = USBSTOR\DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.00\20021111153705700&0 SCSIBus = 0 SCSILogicalUnit = 0 SCSIPort = 0 SCSITargetId = 0 SerialNumber = 20021111153705700 Signature = 0 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT \\DAGOBERT\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0" BytesPerSector = 512 Capabilities = System.UInt16[] CapabilityDescriptions = System.String[] Caption = WDC WD40EFRX-68WT0N0 ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_DiskDrive Description = Laufwerk DeviceID = \\.\PHYSICALDRIVE0 FirmwareRevision = 82.00A82 Index = 0 InterfaceType = IDE Manufacturer = (Standardlaufwerke) MediaLoaded = True MediaType = Fixed hard disk media Model = WDC WD40EFRX-68WT0N0 Name = \\.\PHYSICALDRIVE0 Partitions = 1 PNPDeviceID = SCSI\DISK&VEN_WDC&PROD_WD40EFRX-68WT0N0\4&BFDEFCD&0&000200 SCSIBus = 0 SCSILogicalUnit = 0 SCSIPort = 0 SCSITargetId = 2 SectorsPerTrack = 63 SerialNumber = WD-WCC4E3HX8FZP Size = 4000784417280 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT TotalCylinders = 486401 TotalHeads = 255 TotalSectors = 7814032065 TotalTracks = 124032255 TracksPerCylinder = 255 \\DAGOBERT\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE5" Caption = Generic- MS/MS-Pro USB Device ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_DiskDrive Description = Laufwerk DeviceID = \\.\PHYSICALDRIVE5 FirmwareRevision = 1.00 Index = 5 InterfaceType = USB Manufacturer = (Standardlaufwerke) MediaLoaded = True Model = Generic- MS/MS-Pro USB Device Name = \\.\PHYSICALDRIVE5 Partitions = 0 PNPDeviceID = USBSTOR\DISK&VEN_GENERIC-&PROD_MS/MS-PRO&REV_1.00\20021111153705700&3 SCSIBus = 0 SCSILogicalUnit = 3 SCSIPort = 0 SCSITargetId = 0 SerialNumber = 20021111153705703 Signature = 0 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT \\DAGOBERT\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE3" Caption = Generic- SM/xD-Picture USB Device ConfigManagerErrorCode = 0 ConfigManagerUserConfig = False CreationClassName = Win32_DiskDrive Description = Laufwerk DeviceID = \\.\PHYSICALDRIVE3 FirmwareRevision = 1.00 Index = 3 InterfaceType = USB Manufacturer = (Standardlaufwerke) MediaLoaded = True Model = Generic- SM/xD-Picture USB Device Name = \\.\PHYSICALDRIVE3 Partitions = 0 PNPDeviceID = USBSTOR\DISK&VEN_GENERIC-&PROD_SM/XD-PICTURE&REV_1.00\20021111153705700&1 SCSIBus = 0 SCSILogicalUnit = 1 SCSIPort = 0 SCSITargetId = 0 SerialNumber = 20021111153705701 Signature = 0 Status = OK SystemCreationClassName = Win32_ComputerSystem SystemName = DAGOBERT Win32_ComputerSystem \\DAGOBERT\root\cimv2:Win32_ComputerSystem.Name="DAGOBERT" AdminPasswordStatus = 3 AutomaticManagedPagefile = False AutomaticResetBootOption = False AutomaticResetCapability = True BootROMSupported = True BootStatus = System.UInt16[] BootupState = Normal boot Caption = DAGOBERT ChassisBootupState = 3 ChassisSKUNumber = Default string CreationClassName = Win32_ComputerSystem CurrentTimeZone = 120 DaylightInEffect = True Description = AT/AT COMPATIBLE DNSHostName = dagobert Domain = fairy.intra DomainRole = 1 EnableDaylightSavingsTime = True FrontPanelResetStatus = 3 HypervisorPresent = False InfraredSupported = False KeyboardPasswordStatus = 3 Manufacturer = System manufacturer Model = System Product Name Name = DAGOBERT NetworkServerModeEnabled = True NumberOfLogicalProcessors = 4 NumberOfProcessors = 1 OEMStringArray = System.String[] PartOfDomain = True PauseAfterReset = -1 PCSystemType = 1 PCSystemTypeEx = 1 PowerOnPasswordStatus = 3 PowerState = 0 PowerSupplyState = 3 PrimaryOwnerName = Windows-Benutzer ResetCapability = 1 ResetCount = -1 ResetLimit = -1 Roles = System.String[] Status = OK SystemFamily = To be filled by O.E.M. SystemSKUNumber = SKU SystemType = x64-based PC ThermalState = 3 TotalPhysicalMemory = 17119690752 UserName = DAGOBERT\fairy WakeUpType = 6
-
Now my Tablet doesnt work at all anymore with the current Beta (1.8.4.665). No cursor recocnized, nothing. Bugreport send.
Quote -
I just hope that this problem is fixed in the next version. The last release is a while ago and I still have hope for a fix. If this doesnt get fixed i think its time to looking for another software. Since theres no really alternatives to Affinity for Vectors I guess the old torrent version of CS6 needs to do the job again 🤷♂️ Sounds harsh but right now Affinity Designer is just unusable with those issues and Inkscape is a nightmare from the UI.
-
Sounds like not a problem of Affinity to me. More a problem with your color settings or a wrong color profile. Try to use the same color profile in every program you use. sRGB IEC61966-2.1 is the default one in the most cases and totally okay for web graphics. Set it up in the old Windows control panel and also in your programs so that every program uses this profile.
Hört sich für mich nicht nach einem Problem von Affinity an sondern eher nach einem falsch eingestelltem ICC-Farbprofil. Versuch mal auf allen beiden Programmen das gleiche Farbprofil zu nutzen. Versuche mal in Windows in der alten Systemsteuerung das Farbprofil sRGB IEC61966-2.1 zu aktivieren und auch in deinen Programmen unter Einstellungen das einzustellen. Natürlich kannst du auch das von Adobe weiter benutzen, musst es danna ber auch in Affinity und co. dementsprechend, einstellen
-
Yeah highly anyoing as well if you want to move layers and this stupid windows ink freehand input thingy pops up everytime. And a lag when trying to grab the bar for the stroke thickness also results into a big lag evenwith Windows Ink enabled. Unusable for me, sorry.
-
-
I just bought a wacom graphics display recently. Working with AF is currently a pain in the.. you know where... with this pentool problem. One version later its still not fixed. Guys I'd had a lot of patience and I understand its rough times but... What are you doing the whole day? Working on new features? Please for god sake, please make the latest stable run good first! I don't need a Template browser! I need a proper workflow! It's a nightmare:
Disable Windows Ink and you have a lag on the whole system with every stroke where working is impossible.
Enabling Windows Ink makes your cursor is hyper sensitive and you even cant add a ancorpoints correctly. Yes I use the Beta - problem still exsist. Every beta update I hope.. but no... I'm disappointed!I mean you have this nice forum here were people can write bugs and other things down but whats the point when the major bugs which really interrupting the main workflow and productivity, still exsist in every update? Im aware that the pentool bug is addressed and known to the dev team but it seems the priority isnt that high for it. Why something like such a major bug gets ignored everytime? Some people do more in AD rather than just drawing cycles or creating logos. I illustrate comics, I do commissioned works and thats my job. I need to pay my bills with it. I actually put a lot of trust into Affinity when I changed from AI to AD.
So I need your Software and I dont want to miss the other pros this great program has. But now It's impossible to work with AD if the workflow is a nightmare!I need double the time to finish one work than before with AD 1.7.x which also had anyoing bugs which were partly fixed in 1.8.
-
If you guys are aware why you dont fix those problems?
-
-
Your workaround helps so far.
Thank you very much for your work guys even in this hard times. Please take care of each other guys!
-
Gotta need to add something to the bugs: Again keystrokes dont working anymore after a while inactive window. Zoom tool and the other tools are working this time just the keystrokes dont react.. Another bug that exsist since 1.6.x.
-
7 hours ago, LCamachoDesign said:
@Pockenfresse are you able to edit the title of this topic to mention this is related to the Windows Ink option? So QA and developers can track this more easily? Thanks!
Done.
Disabling the Windows Ink option in the settings works out for me. Pentool is working now as disired.
-
-
Version 1.8.2 runns fine so far but the behavior of the pentool is very strange. By adding starting ancors I always accidently make curve grips which causing strange effects. It only happens when I use my Wacom tablet. I also noticed that I cant adding new ancors anymore in already exsisting paths. In the old version I simply could click with the pentool into the path. With the Mouse its no problem but as soon I use my graphic Tablet it is impossible.
-
Sorry this is unacceptable thing. Sure Software has bugs but if I pay 60 bucks i also want that bugs getting fixed as soon as possible. Instead those bugs are existent since 1.6.x and It's just unacceptable that they werend fixed. Instead having an new fancy "new" dialgue or several new tools that are also buggy acording to the other posts im the forum. The same problem I had when my streaming software werent able to window-capture the canvas. Instead investigating the whole problem they said i should visit the developer forum of my streaming program, because its 100% not affinitys fault.
You actually can reproduce the issue when you minimize the Affinity window while having an document opened. After some surfing or longer inactivity of the window, Keystrokes, Tools and Zoom dont work properly anymore. Every now and then its enough to just change the window for a short time and everything locks up. Sometimes its enough to close the document and reload it and sometimes you need to restart the whole program. When streaming for the customer (without window capture) it is really not the best advertizement for the Affinity series if the artist needs to close the program every 5 minutes because I need to change the window to talk with my customer and the whole stuff is stuck or locked again.
-
Hi again
AP 1.8.0.585
Windows 10 Version 1909, nVidia GTX1050, 16 GiB RAM
Another bug I found is if you use the Select brush after raster the picture, and deleting several selected areas with the DEL key, the hand tool dont work anymore. It locks the whole selection (cant move or change the position of the picture anymore) and only a restart of the software makes it work again. Happens with Tablet and also Mouse only.
Also the switch to Windows Ink is a heavy backfall that will makes me using another software for sketching unfortantly. Simply unusable. Its not a bug its a feature it seems but its a feature I dont need actually. The same problems with Affinity designer also here with Brush selection that it sometimes dont make a stroke at all.. only when I make the wacom control panel in the foregorund. But then the other bug happens that i cant use the zoom anymore and also invisible strokes without any control..
-
Hi there.
AD 1.8.0
Windows 10 Version 1909, 16 GiB RAM, nVidia GTX1050, Wacom Intous Medium (2012) Driver version: 6.3-38-2
Same as the previous 3 major releases the zoom and also the Pentool is unusable when leaving the window sometimes and come back after it. It locks for some strange reason and I cant make any storke anymore. (Only invisibe ones without any control) Also in the Pixel Persona working is still impossible if I need everytime restart several times the whole software just to make my tools working again. No proper workflow possible anymore and i cant hold in my deadlines.
Normally im not that disappointed but I actually need those programs to earn money. I also spend money to use them and I would love to use the programs as desired and without any problems. Right now it seems those major bugs are getting ignored with every release. I really hoped this issue got fixed in the new version. Sadly this didnt happend. If you guys need anything form me, logs or other stuff just tell me what you need and I'll send it.
-
I am using one monitor at 1920x1080 res., No scaling.
-
Sysinfo: Windows 10 Version 1903 (Build 18362.295), Affinity Designer: 1.7.2.471
I found a strange behavior when using the navigator to scroll around in a huge project file with several artboards. It's not possible to navigate with the navigator properly. Size of each artboard: 6372 x 3624 Px.
-
Again... I do not record videos. I do stream my desktop to my customers while I work on the product which actually works fine if I capture all (The whole display). Just the window capture makes trouble because it does not show the canvas.. What it shows is the preview window of the navigator. Why is this an issue for me? Because I do not want to capture my whole Desktop to the whole world seeing my wallpaper with my ugly wife, folders or whole documents if I want to change the program, open my mailbox or messaging with other customers. Also called known as GDPR.
Those OBS guys said ask the affinity guy and now you say go to OBS.
Thank you anyway for the help I will see what I can do and if I can find a workaround for this issue. Maybe a second monitor would help - another 200 bucks. Let's hope the wacom pen issue at least gets fixed soon.
It seems also the issues with the overly sensitive anchorpoints is fixed now. Good work!
Designer crash to desktop (ntdll.dll)
in V1 Bugs found on Windows
Posted
By working on a more complex lineart (Pentool) designer crashes to desktop without warning.
Eventlog screenshot attached.
Used Desinger version: 1.10.5.1342
Graphics driver: 30.0.15.1215 (nVidia Game Ready Driver 512.15)
GPU: NVidia 1050Ti
OS: Windows 10 x64
Memory: 32 GiB
(Btw your broad is broken! I cant upload anything and the whole Javastuff is not loading properly. Console says some stuff were deprecated. No scriptblocker or adblocker used.)
Eventlog output for the Designer:
Name der fehlerhaften Anwendung: Designer.exe, Version: 1.10.5.1342, Zeitstempel: 0x622266de
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.1566, Zeitstempel: 0x1be73aa8
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff249
ID des fehlerhaften Prozesses: 0x5698
Startzeit der fehlerhaften Anwendung: 0x01d848ebbb95cafe
Pfad der fehlerhaften Anwendung: C:\Program Files\Affinity\Affinity Designer\Designer.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: b5f20b82-eb17-4bd2-a28c-1c9a9e74d72d
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: