https://www.wings3d.com/forum/ Thu, 07 May 2026 21:08:20 +0000 MyBB https://www.wings3d.com/forum/showthread.php?tid=3129 Thu, 14 Sep 2023 09:53:21 +0000 Drakan1955]]> https://www.wings3d.com/forum/showthread.php?tid=3129 I'm fairly new to using Wings 3D and definitely have a lot to learn. To better understand how the software works, I decided to complete and improve the Italian translation of the program, soon realizing that there were notable differences in the arrangement of the lines between the main file in English and the one in Italian, so I started almost from the beginning and now the files in English and those in Italian are mirrored
Now the first draft is complete even if it is a work in continuous evolution because as I understand the various functions well (and there are many), I improve the translation of the terms and related descriptions.
Naturally I expect reports of errors and clarifications, which are always welcome, especially if accompanied by the correct translation of the incorrect term.
I will not stop refining and improving the files, periodically releasing new translations when the number of corrections becomes significant.
As for the current version, you can download it from here:
Just unzip the file in the main Wings 3D folder and allow overwriting to have all the translation files in place.
Finally, some advice for those who want to translate or correct the translation of files, which I would like to add to the very precious ones found here.

1 - Let's remember that the translation files are written in a programming language that has its own rules and reserved special characters, so I used an editor (Notepad++) that highlights the strings in a different color, in order to understand what can be changed with safety.
2 - Test the translation regularly: it is easier to look for an error in groups of a few lines than in groups of hundreds.
3 - Before testing a new translation block, make a backup copy of the last known working file.
4 - Pay particular attention to terms such as ~p or ~s~s that are interspersed with strings: an extra space is enough to create problems.
5 - Google translator sometimes transforms double quotes (") into single quotes ('), which is absolutely not allowed, so by copying and pasting avoid the quotes at the beginning and end of the string. If this happens, restore the quotes manually.

An error with the quotation marks or, in general, an involuntary modification to the Erlang code causes the non-application of all the translation contained in the file (even thousands of lines) and the program seem to revert to English (Putting your head against the wall, like I did it, it doesn't solve the problem).

There are still untranslated parts, such as the properties of the Torus Knot for which there are no voices to translate or many plugins that do not have .lang files.

I hope that my translation will encourage more people to approach this software with infinite capabilities.

  Italiano per Wings 2.2.9 v1.0.zip (Size: 79.5 KB / Downloads: 0) ]]> I'm fairly new to using Wings 3D and definitely have a lot to learn. To better understand how the software works, I decided to complete and improve the Italian translation of the program, soon realizing that there were notable differences in the arrangement of the lines between the main file in English and the one in Italian, so I started almost from the beginning and now the files in English and those in Italian are mirrored
Now the first draft is complete even if it is a work in continuous evolution because as I understand the various functions well (and there are many), I improve the translation of the terms and related descriptions.
Naturally I expect reports of errors and clarifications, which are always welcome, especially if accompanied by the correct translation of the incorrect term.
I will not stop refining and improving the files, periodically releasing new translations when the number of corrections becomes significant.
As for the current version, you can download it from here:
Just unzip the file in the main Wings 3D folder and allow overwriting to have all the translation files in place.
Finally, some advice for those who want to translate or correct the translation of files, which I would like to add to the very precious ones found here.

1 - Let's remember that the translation files are written in a programming language that has its own rules and reserved special characters, so I used an editor (Notepad++) that highlights the strings in a different color, in order to understand what can be changed with safety.
2 - Test the translation regularly: it is easier to look for an error in groups of a few lines than in groups of hundreds.
3 - Before testing a new translation block, make a backup copy of the last known working file.
4 - Pay particular attention to terms such as ~p or ~s~s that are interspersed with strings: an extra space is enough to create problems.
5 - Google translator sometimes transforms double quotes (") into single quotes ('), which is absolutely not allowed, so by copying and pasting avoid the quotes at the beginning and end of the string. If this happens, restore the quotes manually.

An error with the quotation marks or, in general, an involuntary modification to the Erlang code causes the non-application of all the translation contained in the file (even thousands of lines) and the program seem to revert to English (Putting your head against the wall, like I did it, it doesn't solve the problem).

There are still untranslated parts, such as the properties of the Torus Knot for which there are no voices to translate or many plugins that do not have .lang files.

I hope that my translation will encourage more people to approach this software with infinite capabilities.

  Italiano per Wings 2.2.9 v1.0.zip (Size: 79.5 KB / Downloads: 0) ]]> https://www.wings3d.com/forum/showthread.php?tid=442 Sun, 27 Oct 2013 01:09:16 +0000 JohnXZ]]> https://www.wings3d.com/forum/showthread.php?tid=442
Ok, I know I'm new here, and never used wings 3d before, but I wanna use and learn it, so, I don't see Spanish here http://www.wings3d.com/?page_id=81

I can translate to Spanish the documentation, and other stuff while I'm learning... Can someone help me with this? I mean, how can collaborate? I already use dokuwiki for me personal use, I am familiar with this... nice choice.

I use latex for pdf, which do you use?

A little background, I'm sysadmin (linux, win, db's, services, etc) and programmer, not 3d modeller but I like it, I can help whatever you need.

Best regards,
John]]>
Ok, I know I'm new here, and never used wings 3d before, but I wanna use and learn it, so, I don't see Spanish here http://www.wings3d.com/?page_id=81

I can translate to Spanish the documentation, and other stuff while I'm learning... Can someone help me with this? I mean, how can collaborate? I already use dokuwiki for me personal use, I am familiar with this... nice choice.

I use latex for pdf, which do you use?

A little background, I'm sysadmin (linux, win, db's, services, etc) and programmer, not 3d modeller but I like it, I can help whatever you need.

Best regards,
John]]> https://www.wings3d.com/forum/showthread.php?tid=73 Thu, 29 Nov 2012 03:16:11 +0000 oort]]> https://www.wings3d.com/forum/showthread.php?tid=73
The Wings3D Handbook

Edit: I need to point out that it was written in 2009 (newer than the original manual but still old) so newer features are not covered, some things in the preferences dialogs have changed, and OpenGL Rendering is no longer available... never mind the fact that it was never finished. It should help get new users started though...

Edit2: tkbd has created an HTML version of the Wings3D Handbook. It is at the top of my Wings3D page. It is hoped that it can be updated in the not too distant future. Wings3D Handbook HTML Version

oort]]>
The Wings3D Handbook

Edit: I need to point out that it was written in 2009 (newer than the original manual but still old) so newer features are not covered, some things in the preferences dialogs have changed, and OpenGL Rendering is no longer available... never mind the fact that it was never finished. It should help get new users started though...

Edit2: tkbd has created an HTML version of the Wings3D Handbook. It is at the top of my Wings3D page. It is hoped that it can be updated in the not too distant future. Wings3D Handbook HTML Version

oort]]> https://www.wings3d.com/forum/showthread.php?tid=43 Tue, 20 Nov 2012 22:35:19 +0000 optigon]]> https://www.wings3d.com/forum/showthread.php?tid=43
If someone wants to learn to use Wings where do they start?

The Official Manual is sadly out of date and the main problem with writing a new one is that Wings 3d is a moving target.

I've thought about the problem for a long time and the best solution in my opinion is to write a General Overview on how to use Wings 3D.
The other options are:

1. An exhaustive list of features and options going command by command and feature by feature.
   
2. A series of modeling tutorials that show a user how to make something.
   

Also there is the question of medium.
The two most common contenders these days are:

1. Video
   
2. Text plus images
   

Videos are great and can be easy to learn from but keeping video documentation current is hard work. If a feature or workflow changes, then the video has to be reshot or edited to maintain its authority. For this reason video documentation is better for static projects where procedures are unlikely to change.

Wings is a dynamic project at its periphery and slightly more stable at its core, but still too much of a moving target to officially adopt a reliance on video documentation.
Text documentation, on the other hand, can be edited quite quickly and can have sections inserted or deleted without having to rewrite everything. The main issue with a text document is it initial production. Writing a long technical manual is a difficult task. A successful manual depends on an agile content strategy. I don't think an exhaustive feature by feature list is the way to go. So I suggest an overview approach.

The advantage of an overview approach to a technical manual for Wings, is that it highlights the important aspects and general philosophy of how to use Wings. Instead of trying to describe every single feature of Wings, an overview would focus on the methodology of wings by describing a selection of key features. The goal of the documentation would be to engender the user with all they need to know to figure out the rest on their own.

An over view approach is easier to maintain and much shorter than an a feature by feature manual, though it would compliment and lend context to a feature by feature manual if one were to be constructed synchronously.

Here is an outline of what I've come up with. Just wondering what people think of this approach.

General Overview

1. Subdivision Modeling
   
2. Make a Cube
   
3. Using the Camera
   • Rotate
     
   • Pan
     
   • Zoom
     
   • Aiming the Camera
     
   • Viewing Along an Axis
     
4. Viewing Modes
   • Smoothed Preview
     
   • Wireframe
     
   • Orthographic
     
5. Selection Basics
   • Selection Modes
     
   • Mouse Selection and Deselection
     
   • Deselect Using the Spacebar
     
   • Bounding Box Selection
     
   • Increase and Decrease Selection
     
   • Edge Loops and Rings
     
6. Basic Commands
   • Move, Rotate, and Scale
     
   • Extrude
     
   • Smooth
     
   • Cut
     
   • Connect
     
   • Bridge
     
7. Advanced Selections
   • Infoline
     
   • Secondary Selections
     
   • Move Along Vector
     
   • Rotate Around User Defined Centre
     
   • Magnets
     
8. Advanced Commands
   • Flatten
     
   • Intersect
     
   • Bend
     
   • Circularise
     
9. Advanced Features
   • Virtual Mirror
     
   • Tweak
     
   • Sculpt
     
   • Magnet Mask
     
   • AutoUV
     
10. 3D Coordinate System Basics
    • Axes
      
    • Coordinates
      
    • Points
      
    • Vectors
      
    • Planes
      
    • Normals
      

In addition, none of these headings would be dsicussed exhaustively. Just enough info to figure it out. So for those familiar with the doc I wrote for Tweak on the website -- that is too much info and at best, could be added as a link towards the end of a much briefer summary.]]>
If someone wants to learn to use Wings where do they start?

The Official Manual is sadly out of date and the main problem with writing a new one is that Wings 3d is a moving target.

I've thought about the problem for a long time and the best solution in my opinion is to write a General Overview on how to use Wings 3D.
The other options are:

1. An exhaustive list of features and options going command by command and feature by feature.
   
2. A series of modeling tutorials that show a user how to make something.
   

Also there is the question of medium.
The two most common contenders these days are:

1. Video
   
2. Text plus images
   

Videos are great and can be easy to learn from but keeping video documentation current is hard work. If a feature or workflow changes, then the video has to be reshot or edited to maintain its authority. For this reason video documentation is better for static projects where procedures are unlikely to change.

Wings is a dynamic project at its periphery and slightly more stable at its core, but still too much of a moving target to officially adopt a reliance on video documentation.
Text documentation, on the other hand, can be edited quite quickly and can have sections inserted or deleted without having to rewrite everything. The main issue with a text document is it initial production. Writing a long technical manual is a difficult task. A successful manual depends on an agile content strategy. I don't think an exhaustive feature by feature list is the way to go. So I suggest an overview approach.

The advantage of an overview approach to a technical manual for Wings, is that it highlights the important aspects and general philosophy of how to use Wings. Instead of trying to describe every single feature of Wings, an overview would focus on the methodology of wings by describing a selection of key features. The goal of the documentation would be to engender the user with all they need to know to figure out the rest on their own.

An over view approach is easier to maintain and much shorter than an a feature by feature manual, though it would compliment and lend context to a feature by feature manual if one were to be constructed synchronously.

Here is an outline of what I've come up with. Just wondering what people think of this approach.

General Overview

1. Subdivision Modeling
   
2. Make a Cube
   
3. Using the Camera
   • Rotate
     
   • Pan
     
   • Zoom
     
   • Aiming the Camera
     
   • Viewing Along an Axis
     
4. Viewing Modes
   • Smoothed Preview
     
   • Wireframe
     
   • Orthographic
     
5. Selection Basics
   • Selection Modes
     
   • Mouse Selection and Deselection
     
   • Deselect Using the Spacebar
     
   • Bounding Box Selection
     
   • Increase and Decrease Selection
     
   • Edge Loops and Rings
     
6. Basic Commands
   • Move, Rotate, and Scale
     
   • Extrude
     
   • Smooth
     
   • Cut
     
   • Connect
     
   • Bridge
     
7. Advanced Selections
   • Infoline
     
   • Secondary Selections
     
   • Move Along Vector
     
   • Rotate Around User Defined Centre
     
   • Magnets
     
8. Advanced Commands
   • Flatten
     
   • Intersect
     
   • Bend
     
   • Circularise
     
9. Advanced Features
   • Virtual Mirror
     
   • Tweak
     
   • Sculpt
     
   • Magnet Mask
     
   • AutoUV
     
10. 3D Coordinate System Basics
    • Axes
      
    • Coordinates
      
    • Points
      
    • Vectors
      
    • Planes
      
    • Normals
      

In addition, none of these headings would be dsicussed exhaustively. Just enough info to figure it out. So for those familiar with the doc I wrote for Tweak on the website -- that is too much info and at best, could be added as a link towards the end of a much briefer summary.]]> https://www.wings3d.com/forum/showthread.php?tid=27 Sat, 17 Nov 2012 00:55:00 +0000 tkbd]]> https://www.wings3d.com/forum/showthread.php?tid=27 I'm making a help documentation to assist in Wings3D.
It is database-like,I named it "WINGS 3D Help Dictionary "
URL is here




This database based on the wings's lang file resource,covers the information-line, Hotkeys and many Commands.
I'm glad if will help to learn how to use Wings3d for English and non-English both user.

Usage:
Check "Control" floating panel at Right, and you can change "Language" from pulldown menu.
It is tested on Safari6.02 and Firefox16 (MacOSX).
If there are any mistakes, then please tell me know.

P.S
On making a dictionary, at the old yuku forum, it is found out who's the translator.
Thanks to all translators for each language.]]> I'm making a help documentation to assist in Wings3D.
It is database-like,I named it "WINGS 3D Help Dictionary "
URL is here




This database based on the wings's lang file resource,covers the information-line, Hotkeys and many Commands.
I'm glad if will help to learn how to use Wings3d for English and non-English both user.

Usage:
Check "Control" floating panel at Right, and you can change "Language" from pulldown menu.
It is tested on Safari6.02 and Firefox16 (MacOSX).
If there are any mistakes, then please tell me know.

P.S
On making a dictionary, at the old yuku forum, it is found out who's the translator.
Thanks to all translators for each language.]]>