Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search





This page contains information for modeling users of Papyrus for Real Time.

Papyrus for Real Time (Papyrus-RT) is continually evolving in an agile way, where improvements can occur frequently.

Papyrus-RT is built upon the Papyrus platform, which is also evolving along with the Eclipse Release Train.

Papyrus-RT is also being used as the base for the creation of a domain-specific language and associated tooling.

Our approach is to use an agile way of working to continually drive towards implementing a succession of minimal viable products (MVPs) that build on each other. In order for this to work, we rely on our users to provide feedback on the tool. This feedback is what drives us forward while continually improving and innovating in a way to meet our users’ needs, expectations, and goals.

Users can provide feedback through the creation of bugs in Bugzilla and posts in the community forum.


There are three approaches that can be taken to install Papyrus for Real Time, depending on your needs and level of expertise. A quick way to select an installation approach is indicated below. If you are you are still wondering which is the best way for you to install Papyrus-RT in your environment and would like more details (pros and cons), then read "Which installation for me"!
The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider installing in a directory closer to the root of your system!





  • Content being planned...please be patient

Tips, Tricks, useful modeling patterns, and code snippets

Discussion Forum

If you need help with using Papyrus for Real Time, you can submit your question on the Papyrus-RT forum.

Back to the top