SERGYI

3D-Coat Developer
  • Content count

    162
  • Joined

  • Last visited

Community Reputation

16 Good

About SERGYI

  • Rank
    Developer

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,349 profile views
  1. To make the effect like you have described in "3D-Coat" you have to: run "3D-Coat" > select "Voxel Sculpting" > "Big sphere" > do big stroke with "Grow" brush > click "V" near label "VolumeX" to switch into surface mode > in upper comboboxes for "SHIFT" (or "CTRL-SHIFT") select "Anti Bump" (instead of "Smooth"). Now when you press SHIFT (or CTRL-SHIFT) the changes are very noticeable on big areas (see the attached screenshot).
  2. Hello, Karsten! There is one thing that is surely guaranteed: your Surface Book's Pen correctly sends pressure information into "3D-Coat"! Because you complained only to "Smoothing" brush I suspect maybe you expect some other behaviour of "Smoothing" brush? Can you compare the behaviour of Surface Book's Pen with mouse? When I run "3D-Coat", select "Voxel Sculpting > Big sphere", then do big stroke with "Grow" brush and then select "Smooth" brush it really seems like it doesn't do too much changes on the model (from mouse and from Wacom tablet too). But if I do many small strokes (like grid) and then apply to them "Smooth" brush the result is very noticeable (from mouse and from Wacom tablet). Please see the attached screenshot.
  3. Because smoothing doesn't work even with mouse this is clear sign that this is not because of missing pressure information from Surface Book's Pen but because of some settings inside "3D-Coat". The most reliable and the quickest way to localize the problem is to rename (or backup and then delete) "3D-Coat" user data folder "This PC > Documents > 3D-CoatV47". That folder contains your already created scenes and all custom settings. Please remove/rename that folder (with previous backup if necessary) and then run "3D-Coat" and test the suspicious brushes on standard models with mouse and with Surface Books's Pen. Compare the behaviour with desktop results. Regarding the separate application "Pressure Test". That application shows does the Surface Book's Pen send pressure information into the "3D-Coat" and what value does it send?! The maximum is 650 (hard pressure) and about 300 is medium (soft pressure). Between the WinTab driver and "3D-Coat" only that value is exchanged. The absence of that value inside the separate "Pressure Test" application means that the problem is with WinTab driver which should be (re)installed. The presence of that value means that the problem is inside inner "3D-Coat" transformations which can be reset to defaults by removing/renaming/backuping the mentioned above user data folder.
  4. To separate low-level input from Surface Book's Pen and inner "3D-Coat" settings please use this test: http://www.3d-coat.com/~sergyi/Tests/3D-Coat-Pressure-Test.zip At any moment this test shows does "3D-Coat" receive low-level input with pressure from Surface Book's Pen. This application is the engine of "Tablet Pen" input used by "3D-Coat". The input is not affected by any "3D-Coat" settings and therefore the test shoes is the problem with pen caused by low-level input (i.e. by driver) or by inner "3D-Coat" settings. As you mentioned the pressure is receiving correctly: "When I use the suggested Pen pressure Test tool, the Pen gets recognized as Left Tablet Button, pressure is around 300, when I just press it soft and up to 600 when pressing hard." Then at any moment you can rename/delete/backup (if you have created some scenes already) your user data folder "This PC > Documents > 3D-CoatV47" to see how any brush reacts on pressure using default inner "3D-Coat" settings on default models. This way will help to debug specific brush (because your custom settings will not affect on behavior).
  5. Please install optional WinTab driver for "Surface Book" (files "Wintab_x32_1.0.0.20.zip" or "Wintab_x64_1.0.0.20.zip"): https://www.microsoft.com/en-us/download/details.aspx?id=49497 Also we have separate Pen pressure test which is the engine of "3D-Coat" tablet input. It shows does the pen send pressure information to the application: http://www.3d-coat.com/~sergyi/Tests/3D-Coat-Pressure-Test.zip
  6. Please install optional WinTab driver for "Surface Book" (files "Wintab_x32_1.0.0.20.zip" or "Wintab_x64_1.0.0.20.zip"): https://www.microsoft.com/en-us/download/details.aspx?id=49497 Also we have separate Pen pressure test which is the engine of "3D-Coat" tablet input. It shows does the pen send pressure information to the application: http://www.3d-coat.com/~sergyi/Tests/3D-Coat-Pressure-Test.zip
  7. Please install optional WinTab driver for "Surface Book" (files "Wintab_x32_1.0.0.20.zip" or "Wintab_x64_1.0.0.20.zip"): https://www.microsoft.com/en-us/download/details.aspx?id=49497 Also we have separate Pen pressure test which is the engine of "3D-Coat" tablet input. It shows does the pen send pressure information to the application: http://www.3d-coat.com/~sergyi/Tests/3D-Coat-Pressure-Test.zip
  8. Please perform these steps: start 3D-Coat > Voxel Sculpting > select model "small sphere" > select tool "Transform" > drag along X axis > control+Z moves the sphere back > control+Z removes the sphere > control+Y shows the sphere > control+Y moves the sphere > control+Z moves the sphere back again > control+Z removes the sphere Please perform these steps. Is the behaviour the same as on my machine? Also please try to remove (or backup if you have created some scenes already) folder "This PC > Documents > 3D-CoatV47".
  9. I have built separate Wacom tablet test. Please download and try this test: http://www.3d-coat.com/~sergyi/Tests/3D-Coat-Pressure-Test.zip This is the engine of "3D-Coat" tablet input. It will show does the pen send pressure information to the application and you can see how application behaves during Wacom input. That zip file besides executables also contains two screenshots which show how it should look like. Please look at FPS. Please try both executables (DX - DirectX, and GL - OpenGL). Do you see similar problems? Please contact me directly "support DOT linux AT 3dcoat DOT com".
  10. Local license server "FServer" should be running only on one machine. There should be only one instance of "FServer" with the same serial number. The other instance will not acquire your license from our global license server 188.138.0.46 using port 80. Looking at your IP addresses again I have noticed that they are all global. There is no local IP address like 10.0.1.7. Is there router which connects all machines in your office and assigns them local IP addresses? Because all listed IP addresses are external that means that one of the listed combinations (192.168.100.1:8888, 192.168.70.1:8888, 192.168.178.75:8888) will work only if Firewall (or antivirus software) on your server machine with local license server "FServer" doesn't block external requests through port 8888. Open port 8888 in your Firewall (or antivirus software). Try to change port between local license server "FServer" and "3D-Coat" clients (create plain text file "port.dat" with another port number, for example 9999, in the same folder as the file "license.dat" is located and re-run "FServer", after that use combinations 192.168.100.1:9999, 192.168.70.1:9999, 192.168.178.75:9999). If for some reason security settings or network structure will not allow you to connect locally to "FServer" then the best way is to exchange your floating serial number on standalone (which should be entered directly into "3D-Coat" client). Please contact me directly "support DOT linux AT 3dcoat DOT com".
  11. According to the screenshot all possible combinations of IP:PORT for "3D-Coat" client which should be entered instead of serial number are: 192.168.100.1:8888 127.0.0.1:8888 (this is for local installation, that is "FServer" and "3D-Coat" are on the same machine) 192.168.70.1:8888 192.168.178.75:8888 To choose right IP:PORT combination try to enter them one-by-one in web-browser instead of "3D-Coat" client on your user machine.
  12. To resolve artifacts on "Retina" displays (aliasing and flickering) download 3D-Coat starting from "4.7.24" for macOS and uncheck "3D-Coat > Geometry > Incremental Render": http://3dcoat.com/forum/index.php?/topic/19525-3d-coat-47-beta-tesing-thread/
  13. The pressure on "Surface Pro 4" will work in "3D-Coat" if you will install optional WinTab driver for "Surface Pro 4". For example, from here (files "Wintab_x64_1.0.0.20.zip" and "Wintab_x32_1.0.0.20.zip"): https://www.microsoft.com/en-us/download/details.aspx?id=49498
  14. This is how "3D-Coat" currently supports "Retina Display". The support is not yet finished. Currently "3D-Coat" supports "Retina Display" only inside "On-screen framebuffer", but it doesn't support "Retina Display" inside "Off-screen render targets". When you are navigating or holding [ALT] then "3D-Coat" renders scene into "On-screen framebuffer" which supports "Retina Display". But on idle "3D-Coat" is displaying "Off-screen render target" which currently doesn't support "Retina Display". In the next BETA-build this behaviour will be disabled because we need some more time to implement support for "Retina Display" inside "Off-screen render targets".
  15. Because as you have noticed this problem is specific to the particular file(s) please send me all involved files to the support DOT linux AT 3dcoat DOT com