Search results

  1. DarkWanderer

    Roadmap proposal - Orbiter development

    Please note that what I'm suggesting isn't "git-flow", but a model which combines "mainline" development - where features are merged into main - with branches cut off for specific releases. This allows both to patch old releases if necessary, and maintain tempo of development in main In the...
  2. DarkWanderer

    Roadmap proposal - Orbiter development

    This works well in following cases: You have comprehensive test coverage which gives you close to 100% confidence nothing is broken You can rollback releases really rapidly - e.g. just redeploy from previous commit You have low cost of error - e.g. a button of wrong color is not a show-stopper...
  3. DarkWanderer

    Discussion "Orbiter Council" to guide open-source development

    Would like to propose this as a starting point to discuss roadmap: https://www.orbiter-forum.com/threads/roadmap-proposal-orbiter-development.40423/
  4. DarkWanderer

    Roadmap proposal - Orbiter development

    Hi, Given the positive reception proposals outlined in Council thread, I think we may be able to move forward and start outlining possible future directions in Orbiter development. Below text first and foremost describes my personal vision of how the project may progress - but I am hoping that...
  5. DarkWanderer

    Discussion "Orbiter Council" to guide open-source development

    Greetings Given that @martins - most understandably - may not have time to dedicate to constant development of Orbiter, I think it might be worth discussing whether and how the community itself may help the project to progress. I think everyone would agree that having a single person be a gate...
  6. DarkWanderer

    Guide: Orbiter development in Visual Studio 2019

    I don't experience that, what is the error message? For .cfg files - I guess the correct way to solve it would be to have a customized "install" command for CMake which mimics "copy if newer" Visual Studio behavior. I know it is possible in theory, will need to dedicate some time to implement
  7. DarkWanderer

    Guide: Orbiter development in Visual Studio 2019

    Yes, that is correct. In make/CMake terms the "build" directory is a temporary scratchpad and the "install" is the one with final product (although personally I would still install into separate dir to be in the safe side). The target model withCMake is that you have source dirs in safety and...
  8. DarkWanderer

    Guide: Orbiter development in Visual Studio 2019

    Sorry to hear that - did you have build dir in your Orbiter directory, however? That has potential for failure regardless of whether you use Visual Studio or command line. If you need a "merged" install, at the very least it should be "install" dir which is pointing to an active installation...
  9. DarkWanderer

    Guide: Orbiter development in Visual Studio 2019

    XRSound is part of Orbiter repository already - you need to download irrKlang SDK for it separately because of licensing issues (@dbeachy1 can probably comment on it more) D3D9Client will be integrated soon™ - there's a WIP branch to merge it
  10. DarkWanderer

    Guide: Orbiter development in Visual Studio 2019

    You can adjust build and "install" directory to your liking in your CMakeSettings. Not entirely clear what do you mean by "keeping installation up to date" - you mean updating the repository? This can be done either by "git pull" command, or by using Git Changes window in Visual Studio - it has...
  11. DarkWanderer

    Guide: Orbiter development in Visual Studio 2019

    Hi, Seeing a lot of questions pertaining to how to develop Orbiter using Visual Studio 2019, I've decided to share the setup I use Steps: 1.Install latest version of Visual Studio 2019 Required components: "Desktop Development with C++" package "MFC for latest build tools" component under...
  12. DarkWanderer

    Discussion Building OpenOrbiter under Linux

    Checkout this branch: https://github.com/DarkWanderer/orbiter/tree/linux Then: mkdir -p out/build cd out/build cmake -G Ninja ../.. -DCMAKE_CXX_COMPILER=/usr/bin/wineg++ cmake --build . -- -k0 There's a ton of errors at the moment, of course, due to non-POSIX functions being used in some...
  13. DarkWanderer

    Problem Trouble getting orbiter graphics to work.

    GitHub orbiter installation does not have textures. Do you have Orbiter 2016 installation on your machine? You need to set ORBITER_PLANET_TEXTURE_INSTALL_DIR variable for CMake when configuring so that your freshly-built Orbiter version can correctly init graphics
  14. DarkWanderer

    Discussion Building OpenOrbiter under Linux

    winegcc/wineg++ does exactly that if I'm not mistaken?
  15. DarkWanderer

    SDK Question API compatibility strategy?

    Out of curiosity, why would this method require non-const operations in your use case? From the signature, it should only change state of objects passed to it (no critique, trying to understand the reasons)
  16. DarkWanderer

    Discussion Building OpenOrbiter under Linux

    I don't have anything advanced just yet - just the fact of compilation itself. Yes, I've tried wineg++ and regular gcc. wineg++ is more promising but has a number of changes to be made for "Windows" and std headers to be compatible with each other If you want to try it as well - attached is a...
  17. DarkWanderer

    D3D9Client (semi-native) + Orbiter test build

    Do you plan to PR the new APIs into main Orbiter repo?
  18. DarkWanderer

    SDK Question API compatibility strategy?

    What is the strategy for API compatibility in OpenOrbiter? Is the objective to maintain compatibility with Orbiter 2016 as much as possible, or is it possible to make breaking* changes? Specific issues I'm looking to address are: return types of some functions - int vs intptr_t, int vs size_t...
  19. DarkWanderer

    General Question Orbiter/CMake with Visual Studio 2019 16.11.2

    16.11.2 works for me without issues for me, I've even managed to start compiling Orbiter under Linux (failing now, obviously)
  20. DarkWanderer

    Testing in Open Source Orbiter

    Had to align a lot of moving parts, but it's available now: PR#109. "Integration" (Scenario) tests are runnable from Visual Studio Test Explorer alongside .cpp-based unit tests
Top