OAC:Project

by the OAC Project Team

Project info

Welcome to the OAC project - OFP ArmA Conversion.

Hosted by

• Page hosted by armaholic: OAC project page (temporary design)
  

Our earnest thanks to the armaholic team for hosting our page and projects!

• FTP hosted by MISSING
• SVN hosted by assembla.com
• Bug-tracker (mantis) hosted by MISSING
• Build scripts hosted by MISSING
• YomaTools hosted by MISSING

Purpose of this project

• Playable content. Now. Much. Enjoyable. Good quality.
• In the form of: Get any OFP missions or campaigns playable in ArmA with little or no
  modification of the mission file.
• Use community made addons alongside to improve the visual aspects, sounds or
  gameplay.
• Easy access to the content.
• Automated update and delivery system.
• Open system, focus on compatibility with community addons and MODs.
• Open source project - every can contribute very easily.

NOT the purpose

• Make custom models, textures, sounds.
• Change the gameplay itself.

In other words it has no relation to CWR, has different goals and follows a
different approach.

How does it work

You cannot run OFP missions or campaigns in ArmA for a few technical reasons.
Actually it is quite simple to solve these.

Foremost it is about the missing units (classes).
The other problem is that the script syntax change a bit from OFP to ArmA
(strict string-code requirement).

The solution.

For the first problem only a simple compatibility addon is needed the maps the missing classes
to existing ArmA classes.
With a few simple config tricks it also auto embeds models missing in plain ArmA like the
Bradley if the community addon is loaded alongside.

For the CWC and Res campaign and mission a few additional content addons come
along that contain the music, speech files and similar content.

Now this approach is not limited to BI content, yet the starting version also
allows to load WGL5 missions or campaign conversions and it is easily expandable
to virtually any other OFP addon or MOD.

Most missions that do not involve much scripting can already be loaded with only the
compatibility addon.

For missions that do not work out of the box there is an almost completely
automated process to convert any mission to ArmA scripting standards in a few seconds.
The process already works very well, yet it is easily expandable if necessary.

Last very rare and 'complicated' problems can easily be fixed by hand by any
fair scripter.

More technical details below.

Open source project

The basic idea is that everything is easily accessible for anyone.

In extension to that anyone interested can contribute in different ways to the
project.

For example by

• improving this wiki page
• reporting bugs on the missions or the addons
• try new missions and see if they mission file needs to be updated
• convert missions themselves and add them to the public hub
• improve the compatibility addon yourself by adding new class mappings of yet missing
  OFP addons or MODs.
  

To support this process the project heavily relies on tools that support collaboration.

The wiki, SVN, automated build scripts and YomaTools for project and mission delivery.

Only a very loose organization will keep the project on track and ensure the
quality and success of the project.

So overall it will be an easy access and easy to contribute focus to deliver
content as easily and as much as possible!

The seven roads to OAC

# I. Consumer

Not meant in a negative way. Simply plays the missions and campaigns provided.
Silent epicure.

Details: Download and play.

# II. Promoter

Tells his mates or other people about the project. Given he likes it of course. :)

Details: Tells us about promotions.

# III. Feedback

Shares his opinion about the project.
Makes suggestions how to improve any aspect of the project.
Suggests missions or campaigns for conversion.
Suggests OFP addons or MODs to be included in the compatibility addon.

Details: Where to post feedback.

# IV. Bug-reporting

Reports bugs in converted missions or campaigns or bugs in the compatibility
addon itself at the bug-tracker in a decent way (steps to reproduce, arma.rpt
error, screenshots/videos of the problem).

Details: Where to post bugs.

# V. Contributer

Helps to improve the wiki page.
Makes screenshots or videos to promote the project.
Helps maintaining the infrastructure of the project (SVN, build process,
YomaTools, bug-tracker).
Supports the project with infrastructure (SVN server host, YomaTools server host,
bug-tracker host, hosts a mailing list, hosts the project page).

Details: How to contribute.

# VI. Missions converter

Either you help to improve already converted missions or campaigns by fixing bugs
or improving the gameplay by altering the mission file itself to a limited degree.
Or you convert new missions or campaigns yourself and add them to the public sharing system.

Details: How to convert missions and share.

# VII. Core developer

You are already into config editing or want to learn something about it.
If so, this one is for you.
You can either improve the existing compatibility addon by improving the class
mapping in different ways or add new mappings for yet missing OFP addons or MODs.

Details: How to improve the compatibility addon.

The seven roads to OAC - details

# I. Download and play

Not yet available. Soon available via a YomaTools server.

# II. Tells us about promotions

Best point your friends and other community member to the OAC BIKI page.
Good supplements are the OAC page and the OAC thread in the BI forum.

Please always add these three sources to threads and news posts.

A request to news writers:
Please add news about OAC at your page to his section for us to know so that
we can help with questions and gather feedback from the comments.

Thank you!

News and threads about OAC:
LINK MISSING

# III. Where to post feedback

Until the OAC bug-tracker is online, the thread in the BI forum is the best place to
share your thoughts and suggestions.

• Suggestion for mission or campaign conversions will be gathered ONLY on this ticket.

• Suggestion about addons or MODs to be included in the compatibility addons will
  be gathered ONLY on this ticket.

# IV. Where to post bugs

Please post bugs related to OAC project only at the bug-tracker (not yet online).

The problems can be:

• Non working missions or campaigns
• Problems with the installation
• Problems with the updating

Please keep your bug reports as specific and as precise as possible.
Adding screenshots, videos or the errors from the arma.RPT help to visualize the problem.

A rough description of the steps to reproduce or the mission and its savegame
are another good addition to track the problem down.

Recommended tools for recording:

• GameCam
• Fraps
• Howie's Quick Screen Capture Tool

Support need here

• Nice banner for the project.
• Promotion screenshots.
• Promotion trailers.
• Look for MISSING tag on this page.

Project team

Add yourself if you want to contribute.

• Members:
  • kju (project manager)
  • The-F (island conversion)
• Contact:
  • MISSING
  • Skype group chat room: MISSING
• Page:
  • OAC project page

Change log

Link to the SVN changelog in the trac timeline: MISSING