http://wiki.aqsis.org/ 2010-09-06T13:02:06+00:00 http://wiki.aqsis.org/ http://wiki.aqsis.org/lib/images/favicon.ico text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/3dsmax_plugin?rev=1263804298 Overview ??? Proposal To create a plugin, in a similar vein to the Blender script, based around CGKit. text/html 2008-04-13T06:02:07+00:00 http://wiki.aqsis.org/dev/animal?rev=1208066527 [project logo|] Overview Project “animal” is an umbrella project designed to organise and focus development efforts toward new, exciting and, useful features. Given that our development resources are rather limited, this project is an attempt to make the best use of what we've got. text/html 2007-01-04T14:35:32+00:00 http://wiki.aqsis.org/dev/api_coverage?rev=1167921332 Key Supported Not Supported, will cause a RIB processing error Supported but not implemented, will be quietly ignored Supported but not implemented, will issue a warning RI Call Status Notes RiArchiveRecord RiAreaLightSource RiAtmosphere RiAttribute RiAttributeBegin RiAttributeEnd RiBasis RiBegin RiBesselFilter RiBlobby RiBound RiBoxFilter RiCatmullRomFilter RiClipping … text/html 2008-08-06T14:37:06+00:00 http://wiki.aqsis.org/dev/aqsistex?rev=1218033426 Overview The old aqsis texturing code had become stale and difficult to work with, while also having significant quality problems. An initial effort by Chris Foster to rewrite some parts of the code ended up turning into a full-blown rewrite of the entire texturing subsystem. text/html 2009-06-08T12:13:05+00:00 http://wiki.aqsis.org/dev/beaker?rev=1244463185 Overview The goal of this project is to address the perception that Aqsis is too slow to be useful. Many previous attempts have been made to address this, all failing to provide any worthwhile improvement. This project is an umbrella project for all work to improve speed and memory use of Aqsis. text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/blender_plugin?rev=1263804298 Overview BtoR is a Blender 2.40 (and higher) plugin that is designed to close the gap between Blender and the Renderman world, specifically Aqsis. Proposal Rather than creating its own set of controls for everything, our plugin should use Blender's general interface and options when/where ever possible (the widgets within the script window itself should be kept to a minimum). text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/boost_shared_pointers?rev=1263804298 Using Boost's reference counted pointers Using Boost's reference counted pointers are fairly straightforward once you've gotten the hang of them. The secret is knowing what pointers are “owning” pointers and what pointers are not. Read on for details... text/html 2008-05-26T07:22:27+00:00 http://wiki.aqsis.org/dev/build_aqsis?rev=1211786547 Aqsis uses cmake as a build system. See the build page in the main documentation for instructions relevant to the latest stable version. unstable ---------- OLD System Specific Details Win32 - MinGW Prerequisites MinGW Install MinGW, the latest version of all packages should be OK, unless otherwise specified. text/html 2008-05-26T06:57:07+00:00 http://wiki.aqsis.org/dev/build_aqsis_cmake?rev=1211785027 Deprecated page. See build. text/html 2007-02-19T08:51:26+00:00 http://wiki.aqsis.org/dev/changes_1_2_0?rev=1171875086 ENHENHENHFIXFIXFIXFIXENHENHFIXFIXFIXENHFIXFIXFIXFIXFIX“”1×1FIXFIX“”“”ENHENHENHFIXENHENHENH--””ENH--ENHENHENHFIXFIXFIXFIXFIXFIXFIXENHENHFIXFIXENHFIXENHFIXENHFIXENHENHENHFIXENHFIXENHFIXENH“”FIXFIXFIXFIXFIXFIXFIXENH“”“”FIXFIXENHFIXFIXFIXENHFIXFIX“”FIXFIXENHENHAPIFIXENH--ENHENHFIXENHFIXFIXFIXFIXENHFIX text/html 2008-04-13T23:36:15+00:00 http://wiki.aqsis.org/dev/code_guidelines?rev=1208129775 File Naming Convention To avoid any problems with non-case sensitive filesystems, such as Windows, all filenames should follow the following rules where possible. The only allowable exception is for files sourced from a third-party that are not under the direct control of the project, such as header files for a third-party library. text/html 2007-04-02T09:05:32+00:00 http://wiki.aqsis.org/dev/code_review?rev=1175504732 Goals The goal of this project is to conduct a full, module by module, class by class, review of the Aqsis code. It will be conducted in several stages. Ideally the outcome of the project will be... Tools To ensure a thorough and methodical approach we will need to consider a proper strcutured approach to doing the review and should probably consider where extra tools might help. text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/data_storage?rev=1263804297 Refactored data storage Introduction Most of the data types handled in the aqsis pipeline (floats, vectors, hpoints, matrices, colors and arrays of these) can be represented at the most basic level by an array of floats. For instance, a vector can be represented with an array of three floats, a matrix with an array of 16 floats, etc. text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/dev_documentation?rev=1263804298 Beyond the Aqsis Internals section which describes Aqsis inner workings, Doxygen's comment formatting rules are used to automatically generate source code documentation. The ouput is available online. Doxygen is a nice tool used by an impressive number of projects, read its documentation block syntax to help improve Aqsis code comments. text/html 2010-06-27T22:52:21+00:00 http://wiki.aqsis.org/dev/devstatus?rev=1277679141 This page will detail the work currently underway by the various developers contributing to Aqsis. It is very fluid, and purposely does not include any time-line details. The developers working on Aqsis are generally doing so in their free time, so it is not possible to define strict time-lines. text/html 2009-05-17T21:22:58+00:00 http://wiki.aqsis.org/dev/distributed_rendering?rev=1242595378 Overview I propose an integrated distributed rendering system across a network to distribute and reassemble aqsis renders without the assistance of third party software. This system will allow acceleration of rendering and increase scalability through the use of parallel processing. text/html 2008-03-01T21:26:56+00:00 http://wiki.aqsis.org/dev/eqshibit?rev=1204406816 Introduction The current framebuffer that Aqsis uses is very simplistic, more importantly, it's blocking, that is, you have to manually close it to complete the render. This proposal is to create a replacement that provides an advanced display server that runs in a separate process and communicates with Aqsis via an Interprocess Communications (IPC) mechanism. Being a separate process opens up a lot of other opportunities for the display to provide additional functionality, mostly based around… text/html 2009-04-24T07:32:46+00:00 http://wiki.aqsis.org/dev/events?rev=1240558366 This is an embedded, read only, view of the Aqsis events calendar. Only project administrators have write access to the calendar, if you feel there is an important event that should be listed in the calendar, contact one of the administrators, or alternatively make the suggestion on IRC or the mailing list. text/html 2007-06-14T16:30:17+00:00 http://wiki.aqsis.org/dev/exceptions?rev=1181838617 This document describes the goal of the new exception system in Aqsis, plus guidelines how and when to use the exceptions. Categories The exception classes should allow to distinguish the following set of base cases: XqInternal “”XqValidationXqInternalAPIXqEnvironmentOSOS Issues User errors (especially for users which use the Ri C-API directly) must not pass the API boundary. It should be possible to have that fully automatic by extending the XSL to add catch clauses. The only drawback is … text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/feature_details_2_0?rev=1263804297 Major Speed Improvements Raytracing Core Multi-threading Support text/html 2007-01-03T15:14:34+00:00 http://wiki.aqsis.org/dev/feature_planning_2_0?rev=1167837274 Introduction This page is for the design and discussion of planned features for the 2.0 release of Aqsis. Please do not edit this list unless you are a member of the developer team, discussions should be help on the discussion tab. 2.0+ Feature Ideas Feature Target References 2.0 2.0 2.0 text/html 2007-04-29T07:52:42+00:00 http://wiki.aqsis.org/dev/file_spec?rev=1177833162 Specification 0.1 Description The Aqsis File Format (AQF) is a generic file format for handling chunk-based data. Revision History 0.1 Original draft Design Criteria The file format shall fit the following criteria: “”“”“” In addition, the following non-restrictions will be kept in mind: text/html 2009-05-20T10:41:27+00:00 http://wiki.aqsis.org/dev/general_guidelines?rev=1242816087 Submitting Patches So, you've identified a simple problem, and you're about to post a message to the mailing list to let us know ... well hold on there, buckaroo! Have you considered just submitting a patch? “”“” Creating a patch from a tarball If you obtained the source from a tarball, or you only need to patch a single file, manually running diff is sufficient: text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/giselle?rev=1263804297 Giselle Introduction Giselle (working title) is a procedural animation system engineered to the principles outlined in Stephen May's 1998 PhD thesis "Encapsulated Models: Procedural Representations for Computer Animation" and his resulting project AL. It is based around the Lua language, there are many reasons for this choice, among them... text/html 2007-11-16T08:47:10+00:00 http://wiki.aqsis.org/dev/gonzo?rev=1195202830 Project renamed to Beaker text/html 2008-09-30T07:47:40+00:00 http://wiki.aqsis.org/dev/grid_crack?rev=1222760860 initial version of this page by Matthias Baas Introduction This page is an introduction and summary of the development forum discussion entitled “Grid crack solutions” which is about the black spots that appear in rendered images once in a while. text/html 2010-02-28T22:49:41+00:00 http://wiki.aqsis.org/dev/how_to_contribute?rev=1267397381 All Aqsis developers are volunteers, and we always welcome new contributors. We have a process of authorisation that allows new developers to begin contributing immediately, without compromising the stability of the code. The reason for this process is that the Aqsis codebase is a very complicated thing, and can sometimes trip up the unwary and unfamiliar. The process for new developers is as follows... text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/howto?rev=1263804297 How to output log messages? text/html 2010-03-07T21:12:42+00:00 http://wiki.aqsis.org/dev/index?rev=1267996362 This section contains links to pages covering all developement topics, from obtaining and building the source, to the papers describing the internal workings of Aqsis itself. It's also intended to be a place for discussing implementation of features. text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/instrumentation?rev=1263804297 There are many circumstances whereby the user of Aqsis, be they an artist or a developer, needs to know more about what is actually going on inside. Developers need this information in order to identify problems and area's for improvement, artists need it in order to improve what they produce, and how long it takes. text/html 2007-02-12T23:18:38+00:00 http://wiki.aqsis.org/dev/libraries?rev=1171322318 RIB Client Library (ri2rib) Windows Version 1.0 (stable) There are three versions of the library provided as part of the developer install for the 1.0.x stable release. Each of these is linked against a different Microsoft runtime library, the choice of which to use will be driven by any external requirements. For instance if you are using another thirdparty library that is only available in one flavor, then you should use the same one from Aqsis to ensure the use of a common runtime thro… text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/log_messages?rev=1263804298 Writing log messages is done via C++ IO streams. This means writing messages is almost identical to your regular usage of cout and cerr. The only additional thing you have to do is specifying the priority of the message. Here are some examples: std::cerr << info << "Informational message" << std::endl; std::cerr << warning << "Warning message" << std::endl; std::cerr << error << "A descriptive error message goes here" << std::endl; text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/maya_plugin?rev=1263804297 Overview ??? Proposal To create a plugin, in a similar vein to the Blender script, either based around Liquid or CGKit. text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/mb?rev=1263804298 text/html 2010-09-05T20:38:01+00:00 http://wiki.aqsis.org/dev/meeting?rev=1283719081 Here you will find the summaries of our weekly developer meetings, held on the official #aqsis IRC channel (irc.freenode.net) every Sunday at 21:00 (UTC): <http://chat.aqsis.org> Archive 2010 September Sunday, 5th September August Sunday, 29th AugustSunday, 15th AugustSunday, 8th AugustSunday, 1st August July Sunday, 25th JulySunday, 18th JulySunday, 11th July June Sunday, 27th JuneSunday, 20th JuneSunday, 13th JuneSunday, 6th June May Sunday, 30th MaySunday, 23rd MaySunday, 16th MaySunday, … text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/metric?rev=1263804297 Why Aqsis? Aqsis is more than just software, it's a community! and a community which has continued to grow over the years, resulting in a very stable and trusted project: Codebase The breakdown of the project sources are as follows: Click here to browse the sourcecode. text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/mp_dump?rev=1263804297 It is possible to compile a special version of Aqsis that creates a file containing all micro polygons that have been generated during rendering. This file can then be inspected by a separate tool to identify bugs. For example, you can determine whether a black spot in an image stems from a patch crack or from invalid shading. text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/multithreading?rev=1263804297 This page is for discussion of multi-threading. Initially for supporting shading of multiple grids simultaneously and ray tracing. Important issues to discuss... The initial goal is to get shader execution and grid handling multithreaded. We want this before implementing ray tracing since it will basically force us into doing ray tracing properly. text/html 2010-06-27T22:53:29+00:00 http://wiki.aqsis.org/dev/newcore?rev=1277679209 Introduction The underlying framework of the aqsis core in versions 1.6 and below has been around for a while now and is showing its age in places. During the speed optimizations for aqsis-1.6 it became increasingly clear that some major changes are desirable for two major reasons. First, a lot of functionality in the old core has been added slowly over time and outgrown some of the original design decisions. Second, additional speedups are difficult within the constraints of some of the al… text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/objectallocationtracking?rev=1263804298 Proposal Title: Object Allocation Tracking Proposer: Paul Gregory Date: 2006/06/06 Status: Under discussion History: text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/old_display_device_system?rev=1263804298 The method for displaying rendered data is in two parts. Firstly there is a Display Device Manager (DDM) and this in turn controls Display Devices. In the current version of Aqsis there are two examples of DDM functionality, the DDMSimple, and the DDMSock. The former is an extremely simple implementation that has only one type of display device that is internally implemented within the manager, it writes images as TIFF files, it has no support for shadow map generation, and is really only useful… text/html 2009-04-12T05:11:20+00:00 http://wiki.aqsis.org/dev/performance_testing?rev=1239513080 This page provides guidlines on how to identify performance bottlenecks in the aqsis codebase. There's sections on how to compile aqsis for profiling, available test cases, and an overview of some of the tools we have used for profiling both speed and memory usage. text/html 2009-03-31T10:55:58+00:00 http://wiki.aqsis.org/dev/pipeline?rev=1238496958 Here you can read how Aqsis processes a .rib file. This information will be very important for you if you want to understand what happens when, and which classes are involved. This is a brief overview of the rendering process: Parsing Not documented yet text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/piqsl?rev=1263804297 Introduction Piqsl is an advanced display driver that provides all the combined functionality of the standard displays and more. It is a standalone application capable of managing images from various sources. The sources currently include images/image sequences and image data piped into Piqsl directly from Aqsis (or any other compatible renderer that conforms to the same display interface). It can organise images into conceptual groupings, called books. It allows multiple images to remain open… text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/projects?rev=1263804298 Project Protocols As the focused projects are open to all developers, a more rigid structure must be in place to ensure that the work that is done is worthwhile. As such, a sub-project authorisation scheme will be used. All sub-projects will be discussed and defined here on the project wiki page. Each sub-project will require some empirical evidence of the advantages of the work. When a satisfactory design has been completed, and the data provided to prove the worth, one of the primary develop… text/html 2009-08-01T14:37:00+00:00 http://wiki.aqsis.org/dev/regression_testing?rev=1249137420 Introduction The Aqsis SVN repository contains a regression test suite that can be used to do test renderings which can be compared to reference images or to compare the output of different renderers. Each test consists of at least a RIB file or a program that outputs a RIB file. Additionally a test may contain any number of shaders, texturemaps, archive files, etc. The output of a test is one or more image files. text/html 2008-09-15T07:30:56+00:00 http://wiki.aqsis.org/dev/release_cycle?rev=1221463856 Introduction At any time there are two official versions of Aqsis available for use, the stable version, and the development version. They are differentiated by the version numbering, and the release procedure. The numbering system is described below, the example illustrates the version 1.4.0. text/html 2008-09-15T07:33:54+00:00 http://wiki.aqsis.org/dev/release_procedure?rev=1221464034 Product Release Procedure Major Release ChangeLog.txtsvn2cl<http://ch.tudelft.nl/~arthur/svn2cl/><http://www.cosmo-system.jp/iwasa/svn2clwin.html>svn2cl.sh -o ChangeLog.txt <https://aqsis.svn.sourceforge.net/svnroot/aqsis/trunk>...cscript svn2cl.vbs -o ChangeLog.txt <https://aqsis.svn.sourceforge.net/svnroot/aqsis/trunk>“”svn commit -m “Update to version 1.2 for release”trunkaqsis-<MAJVER>.<MINVER>aqsis-<MAJVER>.<MINVER>.<BUILD>svn copy <https://aqsis.svn.sourceforge.net/svnroot/aqsis/trunk> <h… text/html 2010-06-14T19:14:21+00:00 http://wiki.aqsis.org/dev/releases?rev=1276542861 Releases The following information details an overview of the area's of improvement for each planned release. This information is meant only to provide a high level picture of the release, please refer to the various design pages for more detail on the planned changes. text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/rib_parser_rewrite?rev=1263804298 RIB Parser Rewrite Aqsis needs a new RIB parser to replace the current limited implementation based on yacc and lex. Problems with the current implementation New functionality tcolgate wrote the following on the mailing list, I'll let someone with some actual knowledge about this (not me at the current time) elaborate: text/html 2010-06-14T19:21:46+00:00 http://wiki.aqsis.org/dev/roadmap?rev=1276543306 This document describes the hight level roadmap of the Aqsis product line. We have gathered user and developer input via a survey, this roadmap defines the upcoming releases based on that feedback. Milestones This is subject to change. 2008 2009 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Aqsis 1.4.0 … text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/rt?rev=1263804297 This page is to record details of the raytracing subsystem as they are discussed. Multi Threading is a pre-requisite for doing this properly. The following represents a basic outline of a possible approach to implementing RayTracing withing aqsis with some of the following goals bourne in mind... text/html 2007-03-07T21:42:39+00:00 http://wiki.aqsis.org/dev/sampling?rev=1173303759 Sampling Overview The reader is directed to the pipeline page, specifically the section on sampling data related to buckets here for a primer on the sample point structures, and their initialisation. This section is dedicated to a more thorough, in-depth explanation of the sampling process, so will skip much of the introductory information presented there. text/html 2007-10-01T22:10:12+00:00 http://wiki.aqsis.org/dev/sampling_rewrite?rev=1191276612 Overview The sampling of micropolygons has been identified as one of the causes of performance problems with Aqsis. The current system is too costly to implement properly, and is very difficult to performance tune. A new system, based on the previous method is in progress on the sampling branch. This page serves to record the design of the rewrite, consider and discuss improvements, and compare with the current approach. text/html 2010-01-18T08:44:58+00:00 http://wiki.aqsis.org/dev/scons?rev=1263804298 SCons Build System Task Breakdown: Replace the current individual build systems (AutoBuild, MSDev, XCode) with a single common build system.Cross platform, with support for adding other platforms easily.Provide functionality of AutoBuild system to generate 'dist' packages for source distribution.Allow debug/release builds. text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/shared_rib_parser?rev=1263804297 Refactor RIB Parser as Shared Library Rationale: The RIB parser is currently a statically included component of the projects that use it (aqsis.dll/libaqsis.so & aqsis/aqsis.exe). It would be generally useful, both for the Aqsis project, and for third party developers to have a shared library for the purpose of parsing RIB files. text/html 2010-03-13T17:06:33+00:00 http://wiki.aqsis.org/dev/soc?rev=1268499993 March 12 March 29 Google SoC timeline Introduction Google's Summer of Code initiative allows budding academic developers to work with established open source teams as an alternative to a typical summer-job, helping improve projects and maintaining the OSS ecosystem. text/html 2007-04-12T11:07:39+00:00 http://wiki.aqsis.org/dev/soc_2007?rev=1176376059 Overview We have, for the first time, secured a place within Google's latest SoC initiative to aid in the development of Aqsis, helping to improve our solution(s) for those interested in advanced professional 3D rendering. This page will act as the hub/repository for this year's SoC activities, from proposal through to implementation - Simplifying maintenance and monitoring (single 'Bookmark'). text/html 2008-03-13T06:19:00+00:00 http://wiki.aqsis.org/dev/soc_2008?rev=1205389140 Overview Last year the aqsis developers mentored two students for Google's Summer of Code 2007; we'd like be involved as a project again this year! This page contains outlines of the possible projects and a discussion of how we'd like to run things this year. The page will also act as the hub/repository for this year's SoC activities, from proposal through to initial ideas for implementations. Accepted student projects will get their own page on the wiki to flesh out the details of the impl… text/html 2009-04-22T03:36:12+00:00 http://wiki.aqsis.org/dev/soc_2009?rev=1240371372 Overview Google's Summer of Code initiative allows budding academic developers to work with established open source teams as an alternative to a typical summer-job, helping improve projects and maintaining the OSS ecosystem. This page contains a list of project ideas and some information on how we expect the mentoring process to work this year. As previously, each accepted student will have their own wiki page to flesh-out ideas and implementation details. text/html 2010-03-13T17:06:33+00:00 http://wiki.aqsis.org/dev/soc_2010?rev=1268499993 March 12 March 29 Google SoC timeline Introduction Google's Summer of Code initiative allows budding academic developers to work with established open source teams as an alternative to a typical summer-job, helping improve projects and maintaining the OSS ecosystem. text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/soc_dicing_optimisation?rev=1263804297 text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/soc_distributed_rendering?rev=1263804297 text/html 2007-08-23T08:15:01+00:00 http://wiki.aqsis.org/dev/soc_dsm?rev=1187856901 Rendering a deep shadow map The following is an overview of the DSM theory. My current understanding of the DSM algorithm is based on the paper by Lokovic and Veach, and a website posted by Benjamin F. Gregorski. Psuedonym has a wiki page on DSM here. text/html 2009-06-05T19:48:53+00:00 http://wiki.aqsis.org/dev/soc_geometry_cache?rev=1244231333 Project Details Aqsis is a REYES-based renderer adhering to the RenderMan(r) Interface and it is subject to the architecture’s limitations, which motivates the implementation of a hybrid solution that can take advantage of both REYES and Ray Tracing best features. Ray Tracing can compute accurate shadows, and supports complex lighting, realistic surface reflection models and global illumination. However, Ray Tracing algorithms require random access to the entire scene since rays can pass throu… text/html 2007-08-20T23:14:38+00:00 http://wiki.aqsis.org/dev/soc_multithreading?rev=1187651678 Abstract With the advent of multi-core computers even for basic desktops, parallelizing an application which needs huge amounts of CPU power can bring big performance benefits. Using threads in applications to listen for incoming data (e.g. via sockets) has the benefits of not blocking the rest of application or not having to poll in a loop; but with N CPUs/cores an application with huge CPU usage can run up to N times faster (using a fraction 1/N of the time compared with single-threaded imp… text/html 2009-06-05T05:23:29+00:00 http://wiki.aqsis.org/dev/source_tree?rev=1244179409 This page contains a developer's guide to the aqsis source tree layout in aqsis-1.5 and above, along with guidelines on how to extend it. Introduction In aqsis-1.4 and below, the source tree organisation made it difficult to add new components, and difficult to #include the C++ parts of the aqsis libraries which were distributed to the end user. During the 1.5 development cycle, a new source tree structure was implemented with the following goals in mind: text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/template_tricks?rev=1263804297 This page contains a discussion of several neat template tricks which have been used in parts of the Aqsis codebase. At the moment there's no overarching theme, but feel free to add to the page. Heterogeneous containers boost::any Sometimes it's useful to hold many different types in the same container. There are a number of ways this can be done in C++. The most obvious is to derive all the types from some generic parent class, however this isn't very convenient for a number of reasons: text/html 2007-09-03T05:35:39+00:00 http://wiki.aqsis.org/dev/texture_filtering?rev=1188797739 The problem We have had some issues with texture filtering and mipmap generation, as illustrated in the forum thread Mipmap generation comparison, and notes and bug #1669850. In general it doesn't seem like the quality of our texture filtering is as good as it could be. This page details my investigation into the problem --CJF text/html 2007-09-22T06:55:35+00:00 http://wiki.aqsis.org/dev/texture_library?rev=1190444135 Scope of the library The library will be focussed directly at texturing, and include the following functionality: ... Source location, library name The library will live in the source tree at aqsis/texturing/texlib/ and have the name aqsistex (eg, libaqsistex.so on unix). text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/tree_refactor?rev=1263804297 Project Structure Current Structure The current project layout is messy and disorganised, it's about time for some serious housekeeping. Below is the current project layout as of 23rd August 2005. renderer content ├───all ├───rib │ └───AdditionalDeveloperLibs │ ├───features ├───api │ │ ├───aov ├───aqsis │ │ ├───deformation_mb ├───aqsl … text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/website?rev=1263804297 Overview <SUMMARY_GOES_HERE> Project Lead: renderguy Structure With a focus on modularity the site itself will use a componentised approach, allowing greater flexiblity and scope for future growth: aqsis.org./blog.aqsis.org./community.aqsis.org./liveIRC./forum./metrics./wikidownload.aqsis.org./FTP./projectfoundation.aqsis.org./gallery.aqsis.org./lab.aqsis.org./build./doc./metrics./project./testing./wikilogin.aqsis.org./store.aqsis.org./ Services One of the major goals for the new site i… text/html 2010-01-18T08:44:57+00:00 http://wiki.aqsis.org/dev/xsi_plugin?rev=1263804297 Overview ??? Proposal To create a plugin, in a similar vein to the Blender script, based around CGKit. Resources XSI Wiki