Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Unknown's avatar

    Juan Farias 11:01 pm on September 4, 2019 Permalink | Reply  

    ||||| Code Reviews ||||| 

    Let the reviews begin..

     
  • Unknown's avatar

    Juan Farias 8:57 pm on September 4, 2019 Permalink | Reply  

    ================================================================ ============ Chat board for general glider discussion etc. ============= ================================================================

    Tasty, crunchy, salty, goodness..

     
  • Unknown's avatar

    Horst Evans 3:16 pm on August 27, 2019 Permalink | Reply  

    JSON Tree Viewer 

    Note: This project utilizes the NuGet package Newtonsoft.(https://www.newtonsoft.com/json) also known as Json.NET

    This tool takes XML generated by Reflect, converts that XML to JSON, and converts that JSON into a Tree Structure. The tree structure can be modified. After modification, the Tree Structure can be converted back into JSON, and this JSON is then passed on to a Rest API Documentation Website.

    NOTE: Currently, the tool is not connected to the pipeline and does not interface with Reflect or Rest API. It also does not convert the Tree Structure back into JSON.

    The tool currently runs in a windows form, and the XML is taken in as a text input. This will ideally be automated via interface. The text input does allow for corrections in the XML and JSON, although this would ideally be handled only in the Tree Structure. The conversions are handled via buttons. There is an option to convert XML to JSON, JSON, to Tree, and XML to Tree that handled both previous conversions at once.

    The Tree Structure can be modified through four interactions: adding a node, deleting a node, changing the text in a node, or moving a node. The New Node button creates a new node at the root level, so the new node will not have a parent. The Del Node button deletes a highlighted node. Nodes can be highlighted by being clicked on. Deleting a node will also delete all of the child nodes. Renaming a node is done by double-clicking on a node. Moving a node is done through dragging a selected node and placing it on top of that node. The selected node will become a child of the node it is placed on top of, and it is always placed as the last child in that level.

    The Windows Form for the Tool
    Code Flow Chart
    User Flow Chart
     
  • Unknown's avatar

    Jacob Keffer 8:26 pm on August 12, 2019 Permalink | Reply
    Tags: Dev Updates   

    PIMP – Procedural Iterative Mesh Processing Editor/ Tool 

    The purpose of the Procedural Iterative Mesh Processing Tool, better known as P. I. M. P., is to help facilitate the need for procedural collision mapping based on the comparative mesh. This tool will help by generating “mesh like” collisions but with significantly less polygons than Unity’s Mesh Collider and more accurate shapes than primitive collision types (i.e. cubes, cylinders, spheres, and etc.). Examples of similar tools can be found below:

    These example images provided above are from Unreal Engine 4 and a demonstration on how the engine tries to map mesh collisions using reduced polygons procedurally. The engine provides an array of options to try to map the mesh to a more accurate representation of colliders, each index in this array of options provides a better and more closely mapped collision to the mesh, but at the expense of more polygons. However each option that is provided is more performant than just using all the polygons on the mesh, or mesh collider.

    By abstracting away the tedious process of mapping colliders onto complex meshes, or really any mesh for that matter upon unity imports, we are able reduce time spent on such processes for any 3D Artist who would otherwise be tasked with it. Additional, the benefit in making such a tool is the added level of granularity we may achieve in regards to optimization. Things like spatial partitioning of the polygons and the need to reduce calculations on a per polygon basis, like for instance the heavy processing for mesh colliders, can all be additively handled within our application.

    P. I. M. P. will help benefit Engineers and 3D Artists by easing the process of mapping colliders and to see significant boosts in frame rates and the general process of creating a complex meshes to using them in Unity. The hope as well is to help build an easier pipeline for 3D Models and generate many other tools or systems to help facilitate more complex collisions and what can expand on top of Unity’s collision engine.

     
  • Unknown's avatar

    Juan Farias 7:22 pm on August 8, 2019 Permalink | Reply  

    Change log 8/8/19 

     
  • Unknown's avatar

    Juan Farias 8:26 pm on July 12, 2019 Permalink | Reply
    Tags:   

    Reflection C# Resources 

    Below you will find a list of resources on the topic of Reflection in c#. As we compile more documentation on the topic we will add to the list and possibly abstract it out of a blog post, but for now we will work off of this post.

     
  • Unknown's avatar

    Juan Farias 8:02 pm on July 12, 2019 Permalink | Reply
    Tags:   

    Helpful Links on Assembly Loading in C# 

    Below you will find a pretty good starting point for researching assembly related loading in c#. There are many more links to come, but until we can converge on what we (the tools team) decide are the de facto list we should use this as a starting point.

     

c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel
Design a site like this with WordPress.com
Get started