FlightGear wiki - User contributions [en]

Scenery status meet Feb 2024

2024-01-31T17:46:48Z

Volador: /* Notes and Links on Projects */

Notes for a casual meeting for Scenery interested people held online on Feb 4th 2024. The contents just reflects status of different initiatives without specific commitments.

== Agenda ==
* Introduction to each other (who, areas of interest in FG, ...).
* Present purpose and/or status and/or future direction and/or dependencies on different projects (ca. 10 min per project - not mandatory)
* Discussion of common topics.
* Possible influence on NEXT.

== Notes and Links on Projects ==

{| class="wikitable"
|-
! Project/Initiative !! Links !! Owner(s) !! Status / Notes
|-
| osm2city || [[Osm2city.py|Osm2city on wiki]], [https://gitlab.com/osm2city repos on GitLab] || [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9140 vanosten], HB-VANO on FG Discord ||
* Support for WS 3.0 / NEXT = up-to-date
* Migration of land-use from Python to C++ = plausible generation of lacking buildings ongoing, rest done
* Docker image = available
* FGElev API and memory reduction = not started
* Integration of instanced scenery object = waiting
* Better textures for buildings = only conceptual level started
* Roads/railway bridges, embankments etc. = waiting for WS3.0 settle
|-
|Random Buildings update
|https://sourceforge.net/p/flightgear/fgdata/ci/random_buildings/tree/
|Volador on FG forum, volador_uk on FG Discord
|Summary of progress:

* TheFGFSEagle has a random buildings development fork with the current work

* Fahim solved roof texture coordinates that were skewing textures. We can now have skylights and solar panels on pitched roofs as well as tiles/surfaces with improved detail (more work required to avoid clipping roof features).
* Eagle and Gabo solved lightmap, reflection and normal map problems but still some final tweaks required.
* A new 4k regional texture atlas available based on the layout of the current atlas for simplicity (now 4k agreed with Stuart and Rick) for UK / maybe Northern Europe?, working on one for Southern Europe but need photo contributions.

Next steps:

* Enable normal maps (and maybe reflection maps) for roofs (to discuss effort vs return)
* Fahim to port texture coordinate solutions to the HDR shaders.
* Gather contributions from the community around the world to create regional textures (should be coordinated to avoid duplication) suggesting only a few key regions to start with.
* Assign new textures (once complete) to areas of the globe: Help required to implement this.

Resources available for other contributors:

* Blender project to automatically create roof planes of given tile shape collections with geometry nodes. Output can be texture and also a separate normal map. Basic Blender skills required.
* Photoshop .psd and gimp templates for rows of houses and shop/apartments ready to share with contributors who can take pics locally, tweak perspective, follow a grid and send them in for integration and slot into larger texture atlases.

|-
| Example || Example || Example || Example
|}

== Discussion Topics ==
Proposed topics:
* Scenery build for 2024.1: if based on WS2.0: use FGMS data to select areas with actual traffic to cut down on processing needs (e.g. for osm2city)? Do we change the default airport?
* Scenery build for WS3.0: which area(s) to pick with a commitment to "often" rebuild / adapt to latest changes in code/features

=== Topic X ===
* (Notes go here)

=== Topic Y ===
* (Notes go here)

[[Category:Scenery|Scenery]]

Scenery status meet Feb 2024

2024-01-31T17:38:23Z

Volador: /* Notes and Links on Projects */

Notes for a casual meeting for Scenery interested people held online on Feb 4th 2024. The contents just reflects status of different initiatives without specific commitments.

== Agenda ==
* Introduction to each other (who, areas of interest in FG, ...).
* Present purpose and/or status and/or future direction and/or dependencies on different projects (ca. 10 min per project - not mandatory)
* Discussion of common topics.
* Possible influence on NEXT.

== Notes and Links on Projects ==

{| class="wikitable"
|-
! Project/Initiative !! Links !! Owner(s) !! Status / Notes
|-
| osm2city || [[Osm2city.py|Osm2city on wiki]], [https://gitlab.com/osm2city repos on GitLab] || [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9140 vanosten], HB-VANO on FG Discord ||
* Support for WS 3.0 / NEXT = up-to-date
* Migration of land-use from Python to C++ = plausible generation of lacking buildings ongoing, rest done
* Docker image = available
* FGElev API and memory reduction = not started
* Integration of instanced scenery object = waiting
* Better textures for buildings = only conceptual level started
* Roads/railway bridges, embankments etc. = waiting for WS3.0 settle
|-
|Random Buildings update
|
|Volador on FG forum, volador_uk on FG Discord
|Summary of progress:

* TheFGFSEagle has a random buildings development fork with the current work

* Fahim solved roof texture coordinates that were skewing textures. We can now have skylights and solar panels on pitched roofs as well as tiles/surfaces with improved detail (more work required to avoid clipping roof features).
* Eagle and Gabo solved lightmap, reflection and normal map problems but still some final tweaks required.
* A new 4k regional texture atlas available based on the layout of the current atlas for simplicity (now 4k agreed with Stuart and Rick) for UK / maybe Northern Europe?, working on one for Southern Europe but need photo contributions.

Next steps:

* Enable normal maps (and maybe reflection maps) for roofs (to discuss effort vs return)
* Fahim to port texture coordinate solutions to the HDR shaders.
* Gather contributions from the community around the world to create regional textures (should be coordinated to avoid duplication) suggesting only a few key regions to start with.
* Assign new textures (once complete) to areas of the globe: Help required to implement this.

Resources available for other contributors:

* Blender project to automatically create roof planes of given tile shape collections with geometry nodes. Output can be texture and also a separate normal map. Basic Blender skills required.
* Photoshop .psd and gimp templates for rows of houses and shop/apartments ready to share with contributors who can take pics locally, tweak perspective, follow a grid and send them in for integration and slot into larger texture atlases.

|-
| Example || Example || Example || Example
|}

== Discussion Topics ==
Proposed topics:
* Scenery build for 2024.1: if based on WS2.0: use FGMS data to select areas with actual traffic to cut down on processing needs (e.g. for osm2city)? Do we change the default airport?
* Scenery build for WS3.0: which area(s) to pick with a commitment to "often" rebuild / adapt to latest changes in code/features

=== Topic X ===
* (Notes go here)

=== Topic Y ===
* (Notes go here)

[[Category:Scenery|Scenery]]

Scenery status meet Feb 2024

2024-01-31T17:30:00Z

Volador: Added random buildings update project

Notes for a casual meeting for Scenery interested people held online on Feb 4th 2024. The contents just reflects status of different initiatives without specific commitments.

== Agenda ==
* Introduction to each other (who, areas of interest in FG, ...).
* Present purpose and/or status and/or future direction and/or dependencies on different projects (ca. 10 min per project - not mandatory)
* Discussion of common topics.
* Possible influence on NEXT.

== Notes and Links on Projects ==

{| class="wikitable"
|-
! Project/Initiative !! Links !! Owner(s) !! Status / Notes
|-
| osm2city || [[Osm2city.py|Osm2city on wiki]], [https://gitlab.com/osm2city repos on GitLab] || [https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9140 vanosten], HB-VANO on FG Discord ||
* Support for WS 3.0 / NEXT = up-to-date
* Migration of land-use from Python to C++ = plausible generation of lacking buildings ongoing, rest done
* Docker image = available
* FGElev API and memory reduction = not started
* Integration of instanced scenery object = waiting
* Better textures for buildings = only conceptual level started
* Roads/railway bridges, embankments etc. = waiting for WS3.0 settle
|-
|Random Buildings update
|
|Volador on FG forum, volador_uk on FG Discord
|Folks involved in the random buildings development fork: Chris (me) (Volador), @TheEagle, Fahim and Gabo (Gabo not active for a while)
Summary of progress: Fahim solved roof texture coordinates that were skewing textures. We can now have skylights and solar panels on pitched roofs as well as tiles/surfaces with improved detail (more work required to avoid clipping roof features).

Eagle and Gabo solved lightmap, reflection and normal map problems but still some final tweaks required.

I have a new 4k regional texture atlas based on the layout of the current atlas (now 4k agreed with Stuart and Rick) for UK / maybe Northern Europe?, working on one for Southern Europe but need photo contributions.

Next steps: Enable normal maps (and maybe reflection maps) for roofs.

Gather contributions from the community around the world to create regional textures (should be coordinated to avoid duplication) suggesting only a few key regions to start with.

Resources available: Blender project to automatically create roof planes of given tile shape collections with geometry nodes. Output can be texture and also a separate normal map. Basic Blender skills required.

Photoshop .psd and gimp templates for rows of houses and shop/apartments ready to share with contributors who can take pics locally, tweak perspective, follow a grid and send them in for integration and slot into larger texture atlases.

Assign new textures to areas of the globe: Help required to implement this.

|-
| Example || Example || Example || Example
|}

== Discussion Topics ==
Proposed topics:
* Scenery build for 2024.1: if based on WS2.0: use FGMS data to select areas with actual traffic to cut down on processing needs (e.g. for osm2city)? Do we change the default airport?
* Scenery build for WS3.0: which area(s) to pick with a commitment to "often" rebuild / adapt to latest changes in code/features

=== Topic X ===
* (Notes go here)

=== Topic Y ===
* (Notes go here)

[[Category:Scenery|Scenery]]

Hackathon Proposa1 2023: Rail tracks and roofs reflect sunlight

2023-11-09T22:17:27Z

Volador:

{| class="wikitable"
|-

|Title||<big>Rail tracks and roofs reflect sunlight</big>

|-

|Sponsor||

|-

|Supporters||

|-

| Status||

|-

|Summary||Rail tracks and roofs reflect sunlight to enhance the visuals

|-

|Background||Reflective objects are visible for miles if the sun is at the right angle, this would enhance VFR flying and also add another layer of realism to the sim.

|-

|Details||

|-

|Skills||

|-

|Notes ||

|}

[[Category:Hackathon 2023 Ideas]]

Hackathon Proposa1 2023: Rail tracks and roofs reflect sunlight

2023-11-09T21:23:11Z

Volador:

.
{| class="wikitable"
|-

|Title||<big>Rail tracks and roofs reflect sunlight</big>

|-

|Sponsor||

|-

|Supporters||

|-

| Status||

|-

|Summary||Rail tracks and roofs reflect sunlight to enhance the visuals

|-

|Background||Reflective objects are visible for miles if the sun is at the right angle, this would enhance VFR flying and also add another layer of realism to the sim.

|-

|Details||

|-

|Skills||

|-

|Notes ||

|}

[[Category:Hackathon 2023 Ideas]]

Hackathon Proposa1 2023: Rail tracks and roofs reflect sunlight

2023-11-09T21:21:23Z

Volador:

Hackathon Proposa1 2023: Rail tracks and roofs reflect sunlight

2023-11-09T20:10:43Z

Volador:

Rail tracks and roofs reflect sunlight to enhance the visuals. Reflective objects are visible for miles if the sun is at the right angle, this would enhance VFR flying and also add another layer of realism to the sim.
{| class="wikitable"
|-

| Title ||<big>Rail tracks and roofs reflect sunlight</big>

|-

| Sponsor ||Volador

|-

| Supporters ||

|-

| Status ||

|-

| Summary ||

|-

| Background ||

|-

| Details ||

|-

| Skills ||

|-

| Notes ||

|}

[[Category:Hackathon 2023 Ideas]]

Hackathon Proposa1 2023: Rail tracks and roofs reflect sunlight

2023-11-09T20:09:50Z

Volador:

Rail tracks and roofs reflect sunlight to enhance the visuals. Reflective objects are visible for miles if the sun is at the right angle, this would enhance VFR flying and also add another layer of realism to the sim.
{| class="wikitable"
|-

| Title || '''<big>FIXME</big>'''

|-

| Sponsor ||

|-

| Supporters ||

|-

| Status ||

|-

| Summary ||

|-

| Background ||

|-

| Details ||

|-

| Skills ||

|-

| Notes ||

|}

[[Category:Hackathon 2023 Ideas]]

Hackathon Proposa1 2023: Rail tracks and roofs reflect sunlight

2023-11-09T20:07:43Z

Volador: Created page with "Rail tracks and roofs reflect sunlight to enhance the visuals. Reflective objects are visible for miles if the sun is at the right angle, this would enhance VFR flying and als..."

Hackathon Proposal:Update trees and buildings textures

2021-11-01T17:25:37Z

Volador:

EDIT 1-10-2021 : Unfortunately this idea will no longer be proposed for the 2021 Hackathon due to the sponsors other commitments. If anyone is interested in stepping in to work on this please contact Volador on the forum.

Building on Vanosten's initiative from the 2020 Hackathon: To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

{{Hackathon Proposal
|title=Update trees and buildings textures
|image =
|sponsor=
|supporters=
|background=
The regional textures for random buildings are generated from around only 3 texturemaps or atlases for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick (Vanosten) is doing on other OSM type buildings.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.
|skills= Gimp/photoshop/Illustrator/CorelDRAW etc Image scripting? ImageMagik?
|opportunities=

* Textures and image compositing/layering coding and tagging exporting (to discuss)
* 3D models? Blender? Ac3d?
* Cleaning up or replacing existing textures
}}

[[Category:Hackathon 2021 Ideas]]

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:34:30Z

Volador:

{| class="wikitable"
|-
| Title: || <big>{{{title|Add movement to boats using METAR plus default oscillation}}}</big> <p/> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || TheEagle
|-
| Interested Parties: || Volador
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || Many boats and ships are currently static or follow a path. Adding small default oscillations to axis would bring detail. Adding METAR conditions would further amplify these oscillations. There may be a simple solution that borrows ideas from the current trees movement.
|-
| Background: || {{{background|}}}
|-
| Details: || {{{details|n/a}}}
|-
| Required skills: || xml and possibly nasal. This must be lightweight on processing.
|-
| Learning Opportunities: || xml animation
|-
| Notes: || {{{notes|}}}

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

{{Appendix}}
<noinclude>
</noinclude><noinclude>
{{Informative template|1=
__NOTOC__

== Usage ==
Copy this into the new page with the proposal:
{{obr}}'''Hackathon Proposal 2021'''
{{!}} title = Add movement to boats using METAR
{{!}} image =
{{!}} caption =
{{!}} sponsor =
{{!}} supporters =
{{!}} status =
{{!}} summary = Low level default oscillation of ships and boats plus METAR conditions = subtle in-sim detail
{{!}} background =
{{!}} details =
{{!}} skills =
{{!}} opportunities = xml or light weight Nasal
{{!}} notes =
{{cbr}}

All parameters are optional.

; title
: Short but descriptive title.
; image
: Image excluding the <code>File:</code> namespace prefix.
; caption
: Image caption.
; sponsor
: Sponsors of the proposal
; supporters
: Supporters of the proposal
; status
; summary
: Description of what the proposal is about.
; background
: Background to and motivation for the proposal
; details
; skills
: Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc.
; opportunities
; notes

== Related templates ==

* {{tl|Hackathon Proposal}}

}}

[[Category:Hackathon 2021 Ideas]]

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:32:18Z

Volador:

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:30:31Z

Volador:

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:27:58Z

Volador:

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:26:19Z

Volador:

{| class="wikitable"
|-
| Title: || <big>{{{title|FIXME_RICK}}}</big> <p/> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || TheEagle
|-
| Interested Parties: || Volador
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || Many boats and ships are currently static or follow a path. Adding small default oscillations to axis would bring detail. Adding METAR conditions would further amplify these oscillations. There may be a simple solution that borrows ideas from the current trees movement.
|-
| Background: || {{{background|}}}
|-
| Details: || {{{details|n/a}}}
|-
| Required skills: || xml and possibly nasal. This must be lightweight on processing.
|-
| Learning Opportunities: || xml animation
|-
| Notes: || {{{notes|}}}

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

{{Appendix}}
<noinclude>
</noinclude><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==

This template can be used when describing proposals for the [[Virtual FSweekend Hackathon 2021]].

Adding this template to a page will automatically add [[:Category:Hackathon 2021 Ideas]] to that page.

== Usage ==
Copy this into the new page with the proposal:
{{obr}}'''Hackathon Proposal 2021'''
{{!}} title = Add movement to boats using METAR
{{!}} image =
{{!}} caption =
{{!}} sponsor =
{{!}} supporters =
{{!}} status =
{{!}} summary = Low level default oscillation of ships and boats plus METAR conditions = subtle in-sim detail
{{!}} background =
{{!}} details =
{{!}} skills =
{{!}} opportunities = xml or light weight Nasal
{{!}} notes =
{{cbr}}

All parameters are optional.

; title
: Short but descriptive title.
; image
: Image excluding the <code>File:</code> namespace prefix.
; caption
: Image caption.
; sponsor
: Sponsors of the proposal
; supporters
: Supporters of the proposal
; status
; summary
: Description of what the proposal is about.
; background
: Background to and motivation for the proposal
; details
; skills
: Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc.
; opportunities
; notes

== Related templates ==

* {{tl|Hackathon Proposal}}

}}

[[Category:Templates]]
<templatedata>
{
"params": {
"title": {
"label": "Title",
"description": "Short but descriptive title"
},
"image": {
"label": "Image",
"description": "Image excluding the File: namespace prefix.",
"example": "Canvas Path Profiling.png",
"autovalue": ""
},
"caption": {
"label": "Caption",
"description": "Image caption",
"example": "Google perftools profile showing the overhead of the property I/O when running the benchmark."
},
"sponsor": {
"label": "Sponsors"
},
"supporters": {
"label": "Supporters",
"description": "Supporters"
},
"status": {
"label": "Status",
"description": "Development status"
},
"summary": {
"label": "Summary",
"description": "Description of what the proposal is about"
},
"background": {
"label": "Background",
"description": "Backgroung to and motivation for the proposal."
},
"details": {
"label": "Details"
},
"skills": {
"label": "Skills",
"description": "Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc."
},
"opportunities": {},
"notes": {}
},
"description": "This template can be used when describing proposals for the Virtual FSweekend Hackathon 2021.",
"format": "block"
}
</templatedata></noinclude>

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:22:59Z

Volador:

{| class="wikitable"
|-
| Title: || <big>{{{title|FIXME_RICK}}}</big> <p/> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || TheEagle
|-
| Interested Parties: || Volador
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || Many boats and ships are currently static or follow a path. Adding small default oscillations to axis would bring detail. Adding METAR conditions would further amplify these oscillations. There may be a simple solution that borrows ideas from the current trees movement.
|-
| Background: || {{{background|}}}
|-
| Details: || {{{details|n/a}}}
|-
| Required skills: || xml and possibly nasal?
|-
| Learning Opportunities: || xml animation
|-
| Notes: || {{{notes|}}}

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

{{Appendix}}
<noinclude>
</noinclude><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==

This template can be used when describing proposals for the [[Virtual FSweekend Hackathon 2021]].

Adding this template to a page will automatically add [[:Category:Hackathon 2021 Ideas]] to that page.

== Usage ==
Copy this into the new page with the proposal:
{{obr}}'''Hackathon Proposal 2021'''
{{!}} title = Add movement to boats using METAR
{{!}} image =
{{!}} caption =
{{!}} sponsor =
{{!}} supporters =
{{!}} status =
{{!}} summary = Low level default oscillation of ships and boats plus METAR conditions = subtle in-sim detail
{{!}} background =
{{!}} details =
{{!}} skills =
{{!}} opportunities = xml or light weight Nasal
{{!}} notes =
{{cbr}}

All parameters are optional.

; title
: Short but descriptive title.
; image
: Image excluding the <code>File:</code> namespace prefix.
; caption
: Image caption.
; sponsor
: Sponsors of the proposal
; supporters
: Supporters of the proposal
; status
; summary
: Description of what the proposal is about.
; background
: Background to and motivation for the proposal
; details
; skills
: Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc.
; opportunities
; notes

== Related templates ==

* {{tl|Hackathon Proposal}}

}}

[[Category:Templates]]
<templatedata>
{
"params": {
"title": {
"label": "Title",
"description": "Short but descriptive title"
},
"image": {
"label": "Image",
"description": "Image excluding the File: namespace prefix.",
"example": "Canvas Path Profiling.png",
"autovalue": ""
},
"caption": {
"label": "Caption",
"description": "Image caption",
"example": "Google perftools profile showing the overhead of the property I/O when running the benchmark."
},
"sponsor": {
"label": "Sponsors"
},
"supporters": {
"label": "Supporters",
"description": "Supporters"
},
"status": {
"label": "Status",
"description": "Development status"
},
"summary": {
"label": "Summary",
"description": "Description of what the proposal is about"
},
"background": {
"label": "Background",
"description": "Backgroung to and motivation for the proposal."
},
"details": {
"label": "Details"
},
"skills": {
"label": "Skills",
"description": "Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc."
},
"opportunities": {},
"notes": {}
},
"description": "This template can be used when describing proposals for the Virtual FSweekend Hackathon 2021.",
"format": "block"
}
</templatedata></noinclude>

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:16:40Z

Volador:

{| class="wikitable"
|-
| Title: || <big>{{{title|FIXME_RICK}}}</big> <p/> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || TheEagle
|-
| Interested Parties: || Volador
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || Many boats and ships are currently static or follow a path. Adding small default oscillations to axis would bring detail. Adding METAR conditions would further amplify these oscillations. There may be a simple solution that borrows ideas from the current trees movement.
|-
| Background: || {{{background|}}}
|-
| Details: || {{{details|n/a}}}
|-
| Required skills: || xml and possibly nasal?
|-
| Learning Opportunities: || xml animation
|-
| Notes: || {{{notes|}}}

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

{{Appendix}}
<noinclude>
</noinclude><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==

This template can be used when describing proposals for the [[Virtual FSweekend Hackathon 2021]].

Adding this template to a page will automatically add [[:Category:Hackathon 2021 Ideas]] to that page.

== Usage ==
Copy this into the new page with the proposal:
{{obr}}'''Hackathon Proposal 2021'''
{{!}} title =
{{!}} image =
{{!}} caption =
{{!}} sponsor =
{{!}} supporters =
{{!}} status =
{{!}} summary =
{{!}} background =
{{!}} details =
{{!}} skills =
{{!}} opportunities =
{{!}} notes =
{{cbr}}

All parameters are optional.

; title
: Short but descriptive title.
; image
: Image excluding the <code>File:</code> namespace prefix.
; caption
: Image caption.
; sponsor
: Sponsors of the proposal
; supporters
: Supporters of the proposal
; status
; summary
: Description of what the proposal is about.
; background
: Background to and motivation for the proposal
; details
; skills
: Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc.
; opportunities
; notes

== Related templates ==

* {{tl|Hackathon Proposal}}

}}

[[Category:Templates]]
<templatedata>
{
"params": {
"title": {
"label": "Title",
"description": "Short but descriptive title"
},
"image": {
"label": "Image",
"description": "Image excluding the File: namespace prefix.",
"example": "Canvas Path Profiling.png",
"autovalue": ""
},
"caption": {
"label": "Caption",
"description": "Image caption",
"example": "Google perftools profile showing the overhead of the property I/O when running the benchmark."
},
"sponsor": {
"label": "Sponsors"
},
"supporters": {
"label": "Supporters",
"description": "Supporters"
},
"status": {
"label": "Status",
"description": "Development status"
},
"summary": {
"label": "Summary",
"description": "Description of what the proposal is about"
},
"background": {
"label": "Background",
"description": "Backgroung to and motivation for the proposal."
},
"details": {
"label": "Details"
},
"skills": {
"label": "Skills",
"description": "Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc."
},
"opportunities": {},
"notes": {}
},
"description": "This template can be used when describing proposals for the Virtual FSweekend Hackathon 2021.",
"format": "block"
}
</templatedata></noinclude>

Hackathon Proposal:Add movement to boats using METAR

2021-10-21T09:11:37Z

Volador: Created page with " {| class="wikitable" |- | Title: || <big>{{{title|FIXME_RICK}}}</big> <p/> {{#if: {{{image|}}} | File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}}..."

{| class="wikitable"
|-
| Title: || <big>{{{title|FIXME_RICK}}}</big> <p/> {{#if: {{{image|}}} | [[File:{{{image}}}{{!}}thumbnail{{#if: {{{caption|}}} | {{!}}{{{caption}}}}} ]]}}
|-
| Sponsors: || {{{sponsor|(Feel free to add yourself)}}}
|-
| Interested Parties: || {{{supporters|(Feel free to add yourself)}}}
|-
| Status:|| {{{status|n/a}}}
|-
| Summary: || {{{summary|n/a}}}
|-
| Background: || {{{background|}}}
|-
| Details: || {{{details|n/a}}}
|-
| Required skills: || {{{skills|}}}
|-
| Learning Opportunities: || {{{opportunities|}}}
|-
| Notes: || {{{notes|}}}

|}

<includeonly>[[Category:Hackathon_{{{year|2021}}}_Ideas]]</includeonly>

{{Appendix}}<noinclude>
</noinclude><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==

This template can be used when describing proposals for the [[Virtual FSweekend Hackathon 2021]].

Adding this template to a page will automatically add [[:Category:Hackathon 2021 Ideas]] to that page.

== Usage ==
Copy this into the new page with the proposal:
{{obr}}'''Hackathon Proposal 2021'''
{{!}} title =
{{!}} image =
{{!}} caption =
{{!}} sponsor =
{{!}} supporters =
{{!}} status =
{{!}} summary =
{{!}} background =
{{!}} details =
{{!}} skills =
{{!}} opportunities =
{{!}} notes =
{{cbr}}

All parameters are optional.

; title
: Short but descriptive title.
; image
: Image excluding the <code>File:</code> namespace prefix.
; caption
: Image caption.
; sponsor
: Sponsors of the proposal
; supporters
: Supporters of the proposal
; status
; summary
: Description of what the proposal is about.
; background
: Background to and motivation for the proposal
; details
; skills
: Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc.
; opportunities
; notes

== Related templates ==

* {{tl|Hackathon Proposal}}

}}

[[Category:Templates]]
<templatedata>
{
"params": {
"title": {
"label": "Title",
"description": "Short but descriptive title"
},
"image": {
"label": "Image",
"description": "Image excluding the File: namespace prefix.",
"example": "Canvas Path Profiling.png",
"autovalue": ""
},
"caption": {
"label": "Caption",
"description": "Image caption",
"example": "Google perftools profile showing the overhead of the property I/O when running the benchmark."
},
"sponsor": {
"label": "Sponsors"
},
"supporters": {
"label": "Supporters",
"description": "Supporters"
},
"status": {
"label": "Status",
"description": "Development status"
},
"summary": {
"label": "Summary",
"description": "Description of what the proposal is about"
},
"background": {
"label": "Background",
"description": "Backgroung to and motivation for the proposal."
},
"details": {
"label": "Details"
},
"skills": {
"label": "Skills",
"description": "Needed skills, for example C++, Nasal, XML, Inkspace, Blender, etc."
},
"opportunities": {},
"notes": {}
},
"description": "This template can be used when describing proposals for the Virtual FSweekend Hackathon 2021.",
"format": "block"
}
</templatedata></noinclude>

Hackathon Proposal:Update trees and buildings textures

2021-10-03T15:02:15Z

Volador:

Building on Vanosten's initiative from the 2020 Hackathon: To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

{{Hackathon Proposal
|title=Update trees and buildings textures
|image =
|sponsor=Chris
|supporters=
|background=
The regional textures for random buildings are generated from around only 3 texturemaps or atlases for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick (Vanosten) is doing on other OSM type buildings.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.
|skills= Gimp/photoshop/Illustrator/CorelDRAW etc Image scripting? ImageMagik?
|opportunities=

* Textures and image compositing/layering coding and tagging exporting (to discuss)
* 3D models? Blender? Ac3d?
* Cleaning up or replacing existing textures
}}

[[Category:Hackathon 2021 Ideas]]

Hackathon Proposal:Update trees and buildings textures

2021-10-03T15:00:13Z

Volador:

Hackathon Proposal:Update trees and buildings textures

2021-10-03T14:58:28Z

Volador:

Building on Vanosten's initiative from the 2020 Hackathon: To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

{{Hackathon Proposal
|title=Update trees and buildings textures
|image =
|sponsor=Chris
|supporters=
|background=
The regional textures for random buildings are generated from around only 3 texturemaps or atlases for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick (Vanosten) is doing on other OSM type buildings.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.
|skills= Gimp/photoshop/Illustrator/CorelDRAW
|opportunities=

* Textures and image compositing/layering coding and tagging exporting (to discuss)
* 3D models? Blender? Ac3d?
}}

[[Category:Hackathon 2021 Ideas]]

Hackathon Proposal:Update trees and buildings textures

2021-10-03T14:56:48Z

Volador:

Building on Vanosten's initiative from the 2020 Hackathon: To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.

Skills needed: Gimp/photoshop/Illustrator/CorelDRAW etc

{{Hackathon Proposal
|title=Update trees and buildings textures
|image =
|sponsor=Chris
|supporters=
|background=
The regional textures for random buildings are generated from around only 3 texturemaps or atlases for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick (Vanosten) is doing on other OSM type buildings.
|skills= Gimp/photoshop/Illustrator/CorelDRAW
|opportunities=

* Textures and image compositing/layering coding and tagging exporting (to discuss)
* 3D models? Blender? Ac3d?
}}

[[Category:Hackathon 2021 Ideas]]

Hackathon Proposal:Update trees and buildings textures

2021-10-01T16:43:34Z

Volador:

Building on Vanosten's initiative from the 2020 Hackathon: To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.

The regional textures for random buildings are generated from around only 3 texturemaps for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick is doing on other OSM type buildings.

Skills needed: Gimp/photoshop/Illustrator/CorelDRAW etc

'''Hackathon Proposal 2021'''
| title =
<nowiki>|</nowiki> image =
<nowiki>|</nowiki> caption =
<nowiki>|</nowiki> sponsor =
<nowiki>|</nowiki> supporters =
<nowiki>|</nowiki> status =
<nowiki>|</nowiki> summary =
<nowiki>|</nowiki> background =
<nowiki>|</nowiki> details =
<nowiki>|</nowiki> skills =
<nowiki>|</nowiki> opportunities =
<nowiki>|</nowiki> notes =

[[Category:Hackathon 2021 Ideas]]
[[Category:Hackathons]]

Hackathon Proposal:Update trees and buildings textures

2021-10-01T10:12:37Z

Volador:

Building on Vanosten's initiative from the 2020 Hackathon: To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.

The regional textures for random buildings are generated from around only 3 texturemaps for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick is doing on other OSM type buildings.

Skills needed: Gimp/photoshop/Illustrator/CorelDRAW etc

<nowiki>{{</nowiki>'''Hackathon Proposal 2021'''
| title =
<nowiki>|</nowiki> image =
<nowiki>|</nowiki> caption =
<nowiki>|</nowiki> sponsor =
<nowiki>|</nowiki> supporters =
<nowiki>|</nowiki> status =
<nowiki>|</nowiki> summary =
<nowiki>|</nowiki> background =
<nowiki>|</nowiki> details =
<nowiki>|</nowiki> skills =
<nowiki>|</nowiki> opportunities =
<nowiki>|</nowiki><nowiki> notes =
}}</nowiki>

[[Category:Hackathon 2021 Ideas]]
[[Category:Hackathons]]

Hackathon Proposal:Update trees and buildings textures

2021-10-01T07:47:50Z

Volador:

To update trees and/or buildings textures that are out of date or too low resolution to improve the visual experience while being efficient with CPU and GPU resources.

Forum members have discovered that in the absence of real world pictures of trees (very difficult to capture), recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.

The regional textures for random buildings are generated from around only 3 texturemaps for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick is doing on other OSM type buildings.

Skills needed: Gimp/photoshop/Illustrator/CorelDRAW etc

<nowiki>{{</nowiki>'''Hackathon Proposal 2021'''
| title =
<nowiki>|</nowiki> image =
<nowiki>|</nowiki> caption =
<nowiki>|</nowiki> sponsor =
<nowiki>|</nowiki> supporters =
<nowiki>|</nowiki> status =
<nowiki>|</nowiki> summary =
<nowiki>|</nowiki> background =
<nowiki>|</nowiki> details =
<nowiki>|</nowiki> skills =
<nowiki>|</nowiki> opportunities =
<nowiki>|</nowiki><nowiki> notes =
}}</nowiki>

[[Category:Hackathon 2021 Ideas]]
[[Category:Hackathons]]

Hackathon Proposal:Update trees and buildings textures

2021-10-01T07:43:38Z

Volador:

To update and trees or buildings textures that are out of date or too low resolution.

Forum members have discovered that in the absence of real world pictures of trees, recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.

The regional textures for random buildings are generated from around only 3 texturemaps for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick is doing on other OSM type buildings.

Skills needed: Gimp/photoshop/Illustrator/CorelDRAW

<nowiki>{{</nowiki>'''Hackathon Proposal 2021'''
| title =
<nowiki>|</nowiki> image =
<nowiki>|</nowiki> caption =
<nowiki>|</nowiki> sponsor =
<nowiki>|</nowiki> supporters =
<nowiki>|</nowiki> status =
<nowiki>|</nowiki> summary =
<nowiki>|</nowiki> background =
<nowiki>|</nowiki> details =
<nowiki>|</nowiki> skills =
<nowiki>|</nowiki> opportunities =
<nowiki>|</nowiki><nowiki> notes =
}}</nowiki>

[[Category:Hackathon 2021 Ideas]]
[[Category:Hackathons]]

Hackathon Proposal:Update trees and buildings textures

2021-10-01T07:42:16Z

Volador:

Hackathon Proposal:Update trees and buildings textures

2021-10-01T07:37:55Z

Volador:

To update and trees or buildings textures that are out of date or too low resolution.

Forum members have discovered that in the absence of real world pictures of trees, recent versions of photoshop can generate a wide variety. A small team to help generate and catalogue/tag new trees (variety of tree or region etc) will have a big impact on the scenery.

The regional textures for random buildings are generated from around only 3 texturemaps for the whole world. A team to generate new (larger more detailed) maps could improve the buildings and roofs for the world. This project may also contribute to work Rick is doing on other OSM type buildings.

Skills needed: Gimp/photoshop/Illustrator/CorelDRAW

<nowiki>{{</nowiki>'''Hackathon Proposal 2021'''
| title =
<nowiki>|</nowiki> image =
<nowiki>|</nowiki> caption =
<nowiki>|</nowiki> sponsor =
<nowiki>|</nowiki> supporters =
<nowiki>|</nowiki> status =
<nowiki>|</nowiki> summary =
<nowiki>|</nowiki> background =
<nowiki>|</nowiki> details =
<nowiki>|</nowiki> skills =
<nowiki>|</nowiki> opportunities =
<nowiki>|</nowiki><nowiki> notes =
}}</nowiki>

Category:Hackathon 2021 Ideas

<nowiki>[[Category:Hackathon 2021 Ideas]]</nowiki>

Virtual FSweekend Hackathon 2021

2021-10-01T07:35:34Z

Volador: /* Sign up */

This is the landing page for the '''Virtual FSweekend Hackathon 2021'''.

Normally in mid-November a group of FlightGear enthusiasts participate in [[FSWeekend]] in [https://www.aviodrome.nl/ Aviodrome] at the [https://www.lelystadairport.nl/ Lelystad Airport] in the Netherlands. Over the years this has been a focal point for both finishing existing development/releases and a catalyst for new ideas in FlightGear, as well as an opportunity for FlightGear enthusiasts to share a beer. Like in 2020 FSweekend 2021 was unfortunately cancelled due to COVID-19 uncertainties (it will maybe take place in March 2022). To keep the spirit alive and repeat the successful execution of the [[Virtual_FSweekend_Hackathon_2020|Virtual FSweekend Hackathon 2020]], we are planning to hold another Virtual FSweekend Hackathon on the weekend of 5/6/7 November 2021.

== Hackathon? ==
{{Hackathon Intro}}

== Only Core Development? ==
While the core of the hackathon incl. support previously has been dedicated to development in the very core of FlightGear (mostly C++, [[Nasal_scripting_language|Nasal]] and xml), you are also welcome to participate if you are developing stuff, which contributes to the general FlightGear ecosystem (e.g. [[Addon]], visual artwork or [[Osm2city.py|osm2city]]). However, in that case you might need to provide your own support.

== Sign up ==
{{Note|There is space for many participants, so don't be shy. Rick is happy for people to register right up to the Friday night, but we will not be able to help out with getting builds and git working if you leave it that late!}}

To register your participation, please contact Rick either on the {{forum link|t=39793|text=forum post}}, by PM on the [https://discord.gg/rzuV2DR FlightGear Discord server] or via the [https://sourceforge.net/p/flightgear/mailman/message/37358418/ devel list].

Confirmed participants (in alphabetical particular order):
{| class="wikitable"
|-
! Name
! aka.
! Remarks
|-
|Chris Boylan
|[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=24923 volador]
|Interested in contributing to textures of trees and buildings
|-
|Fernando García Liñán
|
|can provide help regarding core development and graphics (OSG, Compositor and shaders)
|-
|Julian Smith
|[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=19719 cgdae]
|can coach thread-safe properties, recording/replay, CompositeViewer, multiplayer
|-
|Marc Eberhard
|
|
|-
|
|[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=21618 merspieler]
|-
|Nishant Mishra
|
|
|-
|Rick Gruber-Riemer
|[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9140 vanosten]
|organiser; can coach osm2city and OSM data processing
|-
|Stuart Buchanan
|[https://forum.flightgear.org/memberlist.php?mode=viewprofile&u=9 stuart]
|As well as WS3.0, he can provide advices on a wide range of the codebase, as he has touched lots of different parts over the years
|}

== Ahead of the Hackathon ==

{{Hackathon Preparations|year=2021}}

== Schedule ==
With (hopefully) a world-wide group of participants, and varying real life constraints, at any given time over the weekend there will hopefully be a couple of people active.

We will have two big get-togethers:

=== Friday 5th November 2000-2200 UTC. Kick-off ===
* General welcome
* Introductions
* Hack pitches
* Team formation

This is the point at which participants will decide, which Hacks they want to work on. The sponsors of each of the Hacks proposed ahead of time will be invited to give a 5 minutes pitch to the group, with some questions from the audience. Slides/screenshots optional.

After all the Hacks have been pitched, we will have a little break for people to chat and work out which Hack they want to work on.

If a Hack ends up with fewer than 2 people wanting to work on it (including the sponsor), then it will normally be dropped. This is to encourage people to work in groups - larger teams can get more done in the time, and have more opportunities to learn from each other, plus it is more sociable!

=== Sunday 7th November 2000-2200 UTC. Wrap up and demos ===
At the end of the hackathon we will have a get together and have each team present the results of their hack.

Depending on the number of hacks, each team will have 5-15 minutes to demonstrate their hack, describe what they have learned, and what their next steps are.

We will finish with voting for the best hack of the weekend.

== FAQ ==
{{Hackathon FAQ}}

== References ==
{{Appendix}}

[[Category:Hackathon Materials]]
[[Category:Hackathons]]

Hackathon Proposal:Update trees and buildings textures

2021-10-01T07:32:55Z

Volador: Updated details

Hackathon Proposal:Update trees and buildings textures

2021-10-01T07:22:49Z

Volador: Preliminary details as a place holder

<nowiki>{{</nowiki>'''Hackathon Proposal 2021'''
| title =
<nowiki>|</nowiki> image =
<nowiki>|</nowiki> caption =
<nowiki>|</nowiki> sponsor =
<nowiki>|</nowiki> supporters =
<nowiki>|</nowiki> status =
<nowiki>|</nowiki> summary =
<nowiki>|</nowiki> background =
<nowiki>|</nowiki> details =
<nowiki>|</nowiki> skills =
<nowiki>|</nowiki> opportunities =
<nowiki>|</nowiki> notes =
}}

<nowiki>[[Category:Hackathon 2021 Ideas]]</nowiki>

FlightGear wiki:Village pump

2021-04-07T08:33:37Z

Volador: /* Basic question sub page/sandbox */ new section

{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.

Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

== MediaWiki updated to 1.35.1 ==
Hi all,

We've just updated MediaWiki (our wiki software) to version 1.35.1. The update comes with a couple of nice new features, such as [https://www.mediawiki.org/wiki/Extension:VisualEditor a visual editor] that considerably lowers the entry barrier (no need to learn wiki markup!). We've also fixed the issue that prevented users from [[FlightGear_wiki:Village_pump/Archive_2020#UTF-8_language_pages_cannot_be_edited_.28cont._from_2015.29|editing certain non-Latin articles]] and enabled TLS so your connection is now secured with HTTPS.

Although we've tested the update, chances are that we've missed certain scenarios. Please let me know if something isn't working as expected.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 16:59, 6 February 2021 (UTC)

PS: Now that we're back in sync, you may expect more frequent updates again.

: The only issues I have noted so far is that
:* It seems the visual editor, when editing discussion pages, can only be used when adding a new topic, but not when editing an existing one.
:* Section editing is off by default (though I think it might have been previously as well).
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:45, 7 February 2021 (UTC)

:: Hi Johan,
::* I believe that's the way they've designed it (it also works like that on Wikipedia), but I'll see if that can be changed.
::* What do you mean with "section editing"? I can see <code>[ edit | edit source ]</code> links at each section title?
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:57, 7 February 2021 (UTC)

::: Section editing was off by default for me after the update (at least when looking in the preferences; I did open the preferences before I went through any articles).
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:33, 8 February 2021 (UTC)

: Thank you very much! The 6 year old UTF-8 bug is finally gone!! Everything else is looking good to me. No strange Scribuntu/lua errors from the infoboxes, SyntaxHighlight works, collapsible boxes work. Great job!

: I did get one error: "Error contacting the Parsoid/RESTBase server: http-bad-status" when trying to edit. This was triggered by switching from the visual editor to the source editor using the menu bar that appears in the visual editor. But I fixed this by turning off the visual editor in my preferences.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:12, 16 February 2021 (UTC)

:: Hm, I cannot reproduce that here. Did it happen at a specific page? Can you try to reproduce it and provide a recipe?
::[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

: Oh, just one thing if this is possible, can we have a [https://www.mediawiki.org/wiki/Manual:$wgFavicon favicon] set like the forum and the [https://flightgear.org main website]?

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 21:23, 16 February 2021 (UTC)

:: Good one, done!
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:37, 18 February 2021 (UTC)

== Parameter listings in template documentation ==
I noted that the skeleton examples with all parameters have been removed in some cases.

I very much prefer to still having a copyable skeleton template (with prefilled month, year, and/or date when those parameters exist) before the listing of parameters, rather than having to copy a fully filled out filled out example and remove everything I do not need or have to change. It feels very unnecessary.

On the other hand I do like the template data stuff very much, even though it is few extra steps.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:41, 10 February 2021 (UTC)

: Hi Johan,
: I'm not sure if you know this, but you can now add templates through the VisualEditor. If you press "Insert > Template" from the toolbar, you get a nice popup to help you fill in the template and it can also pre-fill stuff for you (e.g., the date in [[:Template:Delete]]). The templatedata stuff on the template page is used to expand this popup form and drive the auto-fill, so most templates will not yet leverage it to the fullest. You can add/edit templatedata by clicking the "Manage TemplateData" button at the top of the edit page of templates. See the documentation at {{mediawiki|Help:TemplateData}} (that page is unfortunately quite messy, I know) and {{mediawiki|Extension:TemplateData}}.
: I feel like we should encourage people as much as possible to use the VisualEditor, as it can help prevent mistakes or incomplete templates. Would this remove the need to have copy & pastable templates? Maybe we'll just have to try and see. There's lots of new stuff to discover and tweak :-)
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Removing the "Goal" heading from template documentation ==
As we will likely go through and edit most of the template documentation to replace the current documentation of template parameters with template data, I would like to also remove the ''Goal'' heading from the template documentation and move that up to being a regular lead section.

I feel that the heading is largely redundant and have previously stuck to it mostly for consistency.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:48, 10 February 2021 (UTC)

: Agree!
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:20, 11 February 2021 (UTC)

== Basic question sub page/sandbox ==

Hi,
New to the wiki here and hoping to contribute in some small way. I don't see any instructions (or menu options) on how to crate a sub page or sandbox in order to start drafting an article. I'll also aim to update the wiki on how to crate a sub page as it might help others with the same question.
Many thanks
[[User:Volador|Volador]] ([[User talk:Volador|talk]]) 08:33, 7 April 2021 (UTC)

Howto:Use Arduino with FlightGear

2021-03-16T10:25:11Z

Volador:

Thanks to FlightGear's [[generic protocol]], [[:Category:Hardware|hardware]] can easily interface with [[FlightGear]]. This hardware can be used to improve the immersion and/or realism of the simulation. Arduino is no exception.

== About Arduino ==
'''[http://www.arduino.cc/ Arduino]''' is an open-source electronics prototyping platform based on flexible, easy-to-use hardware and software. The hardware is a microcontroller designed around an 8-bit or 32-bit microcontroller, with several digital and analog {{Abbr|I/O|Input/Output}} ports. The software is the [http://arduino.cc/en/Main/Software Arduino {{Abbr|IDE|Integrated Development Environment}}].

== Example 1: 2-axis joystick ==
<big>By ScottBouch</big>

This example demonstrates use of two potentiometers (2-axis joystic) with a simple calibration in arduino code. Example is done with Linux Mint. To see more detailed version of this quide go to [http://www.scottbouch.com/flightgear-sim-arduino-serial-hardware-2-axis-potentiometer-joystick.html 2-Axis Potentiometer Joystick:Integration With Flightgear Flight Sim].

=== Wiring ===
Connect 5V to other terminal of potentiometers and 0V to other terminal. Connect potentiometers wiper terminals to Arduino boards A0 and A1.

=== Arduino code ===
<syntaxhighlight lang="c">
/*
Flightgear hardware integration 01: Stick X and Y only so far.

Scott Bouchard UK www.scottbouch.com 14-06-2017
*/

const int stickxio = A0; //Define stick aileron (x) input
const int stickyio = A1; //Define stick elevator (y) input

float stickx = 0; //Start aileron (x) central
float sticky = 0; //Start elevator (y) central

void setup() {
Serial.begin(9600); //Open up serial communication to PC
}

void loop() {
stickx = (analogRead(stickxio)/512.0)-0.99; //Calibration span and offset
sticky = (analogRead(stickyio)/512.0)-0.99; //Calibration span and offset

Serial.print(stickx); //Send aileron position
Serial.print(","); //Variable (var) separator
Serial.print(sticky); //Send elevator position
Serial.print("\n"); //Line separator
}
</syntaxhighlight>
Slightly smoother control is possible if a third digit is added to the output by changing the print statements to <code>Serial.print(stickx, 3);</code> and <code>Serial.print(sticky, 3);</code>.

=== Calibration ===
Use Arduino serial monitor to see that serial data acquired from Arduino board is between -1.00...1.00 when potentiometers are rotated. Potentiometers middle position should send 0.00. If potentiometers are not giving good readings, modify Arduino code "Calibration span and offset" row to fix it.

=== Flightgear protocol code ===
Create a file called hardware.xml to /usr/share/games/flightgear/Protocol directory and paste following lines to it:

<syntaxhighlight lang="xml">
<?xml version="1.0"?>

<PropertyList>

<generic>

<input>
<line_separator>\n</line_separator>
<var_separator>,</var_separator>

<chunk>
<name>aileron</name>
<type>float</type>
<node>/controls/flight/aileron</node>
</chunk>

<chunk>
<name>elevator</name>
<type>float</type>
<node>/controls/flight/elevator</node>
</chunk>

</input>

</generic>

</PropertyList>
</syntaxhighlight>

=== Make Flightgear read serial data ===
Find the port where the Arduino is connected. Look for Arduino IDE Tools... Serial Port... Should be something like ttyACM0. (Note: Scott Bouch tutorial uses FGRUN which is not used anymore) Start Flightgear and paste following code to Settings... Additional settings... when starting Flightgear. Change serial port to correct port name. Note that the ".xml" extension for the protocol file should be omitted.

<syntaxhighlight>
--generic=serial,in,30,/dev/ttyACM0,9600,hardware
</syntaxhighlight>

== Example 2: Controlling internal properties ==
<big>By {{usr|Vaipe}}</big>

This example demonstrates the use of a switch and a potentiometer to control the [[Property Tree]].

=== Equipment and software ===
The following equipment was used for this example:
* [[Changelog_3.2|FlightGear 3.2]]
* [[FGRun]]
* [[Cessna 172P|Cessna 172P Skyhawk]] (default aircraft)
* [http://arduino.cc/en/Main/ArduinoBoardUno Arduino Uno]
* Linux ([http://en.wikipedia.org/wiki/List_of_Ubuntu_releases#Ubuntu_10.04_LTS_.28Lucid_Lynx.29 Ubuntu 14.04])
* Simple on/off switch
* Potentiometer

=== Input protocol file ===
Input protocol file is used to specify how serial information is read by Flightgear. In Ubuntu protocol files are found in:
<code>''/usr/share/games/flightgear/protocol''</code> directory.

==== Protocol file structure ====
Create <code>''controltest.xml''</code> file in your protocol folder and paste code from below to it.
<syntaxhighlight land="xml">
<?xml version="1.0"?>

<PropertyList>

<generic>
<input>
<line_separator>\n</line_separator>
<var_separator>,</var_separator>

<chunk>
<name>Strobe</name>
<node>/controls/lighting/strobe</node>
<type>bool</type>
</chunk>

<chunk>
<name>Throttle</name>
<node>/controls/engines/engine/throttle</node>
<type>float</type>
</chunk>

</input>
</generic>

</PropertyList>
</syntaxhighlight>
See [[Generic protocol]] for a description of the various XML tags.

=== Wiring and coding ===

==== Wiring ====
A potentiometer is connected to Arduinos ground and +5 volts. The potentiometer's middle connector is connected to A0 analoq input. Switch is connected to ground with 10 kOhms pull-down resistor and +5 and digital pin 7. The diagram below illustrates the setup.
[[File:Arduino switch and potentiometer wiring.png|frame|none|Wiring schematic for connecting the potentiometer and switch to Arduino]]

==== Code ====
Copy this C code to Arduino IDE and send it to the Arduino Uno:
<syntaxhighlight lang="c">
/*
FGFS Input Test
Reads a digital input on pin 7, prints the result to the serial port.
Reads a potentiometer input on A0 and print result to serial port.
This example code is in the public domain.
*/

int potPin = 0; // potentiometer on A0
int switchPin = 7; // switch on pin 7
float potValue = 0; // float variable to store potentiometer value

void setup() {
Serial.begin(9600); // open serial connection
pinMode(switchPin, INPUT); // pin 7 declared as input
}

void loop() {

Serial.print(digitalRead(switchPin)); // read and print switch state
Serial.print(","); // print ,
potValue = analogRead(potPin); // read potentiometer and store it to potValue
potValue = potValue / 1024; // divide potValue with 1024 to make it between 0 and 1
PrintDouble(potValue, 2); // pass potValue to PrintDouble-function, read from below what magic happens
Serial.print("\n"); // print new line
delay(500); // delay only for making this guide easier to follow on serial monitor

}

void PrintDouble(double val, byte precision){
// prints val with number of decimal places determine by precision
// precision is a number from 0 to 6 indicating the desired decimial places
// example: lcdPrintDouble( 3.1415, 2); // prints 3.14 (two decimal places)
// From http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1207226548

if(val < 0.0){
Serial.print('-');
val = -val;
}

Serial.print (int(val)); //prints the int part
if( precision > 0) {
Serial.print("."); // print the decimal point
unsigned long frac;
unsigned long mult = 1;
byte padding = precision -1;
while(precision--)
mult *=10;

if(val >= 0)
frac = (val - int(val)) * mult;
else
frac = (int(val)- val ) * mult;
unsigned long frac1 = frac;
while( frac1 /= 10 )
padding--;
while( padding--)
Serial.print("0");
Serial.print(frac,DEC) ;
}
}
</syntaxhighlight>

==== Testing serial output ====
Use Arduino IDE's serial monitor and you should see something like this:
[[File:Flightgear arduino serial monitor.png|frame|none|Arduino IDE's serial monitor output]]

The first number is switch data, so it's either 0 (switch off) or 1 (switch on). After the "," mark is our throttle data. First it's 0.00, which meaning idle throttle and then potentiometer is gradually turned until it reaches 0.99.

{{Note|Remember to '''unplug Arduino's USB cable and plug it back'''.

FlightGear will not be able to read serial without doing this!

You have to do this every time after you use the Arduino IDE.}}

{{Note|The above note may not be relevant to newer versions of the Arduino IDE software.}}

==== Starting FlightGear ====

===== Method 1: Command line =====
FlightGear needs to be started with a correct command line option for it to be able to read serial connection. This example uses following option:
<syntaxhighlight>
--generic=serial,in,30,/dev/ttyACM0,9600,controltest
</syntaxhighlight>

===== Method 2: FGRun =====
Alternatively, you can use FlightGear's graphical user interface (FGRun) to launch FlightGear. See the image below for the correct settings.
[[File:Starting Flightgear with input options enabled.jpg|thumb|none|Starting Flightgear with FGRun, selecting input/output options]]

If you don't know your correct port is , you can check it with a following command in terminal:
<syntaxhighlight>
dmesg | tail
</syntaxhighlight>
It should give you a message something like <code>ttyACM0: USB ACM device</code> or <code>ttyACM1: USB ACM device</code>.

{{Note|This command gives you the last event in the stack,

so you need to make sure you plug in or unplug your Arduino to the serial port

immediately prior to running the command.}}

That is your port. Finally, save setting by clicking "OK" and click "Run" to start FlightGear. For a more detailed guide, see [https://sites.google.com/site/flightgeararduinoandlinux/home Flightgear, Arduino and Linux]

{{Note|In some installations you need set permission for $user

to the groups tty and dialout or the Arduino will fail to

establish a connection to FlightGear.}}

== Example 3: Outputting properties ==
<big>By {{usr|Rubdos}}</big>
[[File:Arduinofgfs.jpg|thumb|270px|Arduino LCD panel displaying speed, heading and altitude.]]
This example uses the example using the [[Generic protocol]] and an [http://arduino.cc/en/Main/arduinoBoardMega2560 Arduino Mega 2560].
Below is the protocol XML file used to control the Arduino.
<syntaxhighlight lang="xml">
<?xml version="1.0"?>

<PropertyList>

<generic>
<output>
<binary_mode>false</binary_mode>
<line_separator>newline</line_separator>
<var_separator>newline</var_separator>
<preamble></preamble>
<postamble></postamble>

<chunk>
<name>Altitude</name>
<node>/position/altitude-ft</node>
<type>integer</type>
<format>altitude=%i</format>
</chunk>

<chunk>
<name>RPM</name>
<node>/engines/engine/rpm</node>
<type>integer</type>
<format>rpm=%i</format>
</chunk>

</output>



</generic>

</PropertyList>
</syntaxhighlight>

Below is the C code used for the example, taken from https://gist.github.com/rubdos/5422870.
<syntaxhighlight lang="c">
//PIN 0 -> 7 has positive segment part

// the setup routine runs once when you press reset:
void setup() {
// initialize the digital pin as an output.
pinMode(2, OUTPUT);
pinMode(3, OUTPUT);
pinMode(4, OUTPUT);
pinMode(5, OUTPUT);
pinMode(6, OUTPUT);
pinMode(7, OUTPUT);
pinMode(8, OUTPUT);
pinMode(9, OUTPUT);

pinMode(49, OUTPUT);
pinMode(50, OUTPUT);
pinMode(51, OUTPUT);
pinMode(52, OUTPUT);
pinMode(53, OUTPUT);

Serial.begin(9600);
}

void writeNumber(int nr)
{
if(nr == 0)
{
digitalWrite(2, LOW); // midden
digitalWrite(3, HIGH); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, HIGH); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 1)
{
digitalWrite(2, LOW); // midden
digitalWrite(3, LOW); // lt
digitalWrite(4, LOW); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, LOW); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 2)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, LOW); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, HIGH); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, LOW); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 3)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, LOW); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 4)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, HIGH); // lt
digitalWrite(4, LOW); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, LOW); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 5)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, HIGH); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, LOW); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 6)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, HIGH); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, LOW); // rt
digitalWrite(6, HIGH); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 7)
{
digitalWrite(2, LOW); // midden
digitalWrite(3, LOW); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, LOW); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 8)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, HIGH); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, HIGH); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else if(nr == 9)
{
digitalWrite(2, HIGH); // midden
digitalWrite(3, HIGH); // lt
digitalWrite(4, HIGH); // t
digitalWrite(5, HIGH); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, HIGH); // b
digitalWrite(8, HIGH); // rb
digitalWrite(9, LOW); // dot
}
else
{
digitalWrite(2, LOW); // midden
digitalWrite(3, LOW); // lt
digitalWrite(4, LOW); // t
digitalWrite(5, LOW); // rt
digitalWrite(6, LOW); // lb
digitalWrite(7, LOW); // b
digitalWrite(8, LOW); // rb
digitalWrite(9, LOW); // dot
}
}

// the loop routine runs over and over again forever
long number = 0;
int decimals[5] = {0, 0, 0, 0, 0};

void loop() {
for(int i = 49; i < 54; i++)
{
// Disable the incorrect segment displays
if(i == 49)
{
digitalWrite(53, HIGH);
}
else
{
digitalWrite(i - 1, HIGH);
}
digitalWrite(i, LOW);

// Enable the segments
writeNumber(decimals[4 - (i - 49)]);
delay(1);
}
if(Serial.available() > 14) // Wait until there are two bytes available. Then read them out.
{
String command;
String var;
char lastchar;

while(lastchar != '=')
{
lastchar = Serial.read();
if(lastchar != '=')
{
command += lastchar;
}
}
while(lastchar != '\n')
{
lastchar = Serial.read();
if(lastchar != '\n')
{
var += lastchar;
}
}

if(command == "altitude" )
{
char buf[50];
var.toCharArray(buf, 50);
number = atol(buf);
}

/*if(number == 10000)
{
number = 0;
}*/

long currentnumber = number;

int remainder = currentnumber % 10;
currentnumber = (currentnumber - remainder) / 10;
decimals[4] = remainder;

remainder = currentnumber % 10;
currentnumber = (currentnumber - remainder) / 10;
decimals[3] = remainder;

remainder = currentnumber % 10;
currentnumber = (currentnumber - remainder) / 10;
decimals[2] = remainder;

remainder = currentnumber % 10;
currentnumber = (currentnumber - remainder) / 10;
decimals[1] = remainder;

remainder = currentnumber % 10;
currentnumber = (currentnumber - remainder) / 10;
decimals[0] = remainder;
}
}
</syntaxhighlight>

The hardware used was five seven-segment displays, multiplexed straight on the Arduino device. Ideally, you'd rather use some 74HC595 or other shift register chips to drive them, to unload the Arduino and have more current.

Below is a demo uploaded to YouTube, with voiceover in which the display shows the RPM of [[Robin DR400]]'s single engine.
{{#ev:youtube|lVtV9-CgqBo}}

== Related content ==
* [[Input device]]

== External links ==
* [http://arduino.cc/ Official Arduino website]
* [http://playground.arduino.cc/Main/FlightGear FlightGear Serial Communications with Arduino] (tutorial)
* [http://forum.flightgear.org/viewtopic.php?f=18&t=11126 Arduino LCD and FlightGear] (FlightGear forum)
* [https://sites.google.com/site/flightgeararduinoandlinux/ Flightgear, Arduino and Linux] (potentiometer and switch interfacing tutorial)

[[Category:Cockpit building]]
[[Category:Hardware]]

User:Volador

2021-03-16T10:13:23Z

Volador: Blanked the page

User:Volador

2021-03-16T10:05:09Z

Volador: Created page with "Interfacing: Use Arduino serial interface, generic protocol .XML to activate cockpit controls"

Interfacing: Use Arduino serial interface, generic protocol .XML to activate cockpit controls