New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ogre 2.1 #76
Ogre 2.1 #76
Conversation
I am not very familiar with Ogre 2.1, so unfortunately not in the best position to review this. Perhaps we could ask the Ogre community to provide some testing and feedback? I'm thinking the new rendersystem should be named Ogre21 platform, since it only supports 2.1 and not 2.0, correct? We already have a Ogre 2.0 rendersystem in a separate branch. |
Hey scrawl, I'm part of the team who made the port, we'll change the platform name to Ogre21Platform as requested, also we posted a thread on Ogre forums, hopefully someone there will help review the pull req. We tested it here with the raw Ogre 2.1 branch (just initialized MyGUI in one of the samples)and the results are the following: we tested simple widgets; widgets composed of multiple sub widgets; font rendering; and scissor test. All of those worked perfectly, exactly how they work with the OgrePlatform from MyGUI master and Ogre 1.9 / 1.10. Also, we made an effort to leave the Ogre21Platform code style in accordance with the MyGUI code style. And we edited the CMake already to leave everything as easy as it can be to build and use the new platform. Let us know if there's anything else we can do to move forward the review process. :) |
The changes to FilterNoneSkin break the build when compiling with the Ogre 1.x platform. See the travis build log. |
That file wasn't supposed to be changed, our bad, we'll fix it tomorrow. |
Fixed MyGUI_FilterNoneSkin.cpp errors.
- updated cmake - added HLMS shdaers
FYI, I have looked at the code and there are a couple of things I have recommended, |
I have to disagree with the rename of Ogre2Platform to Ogre21Platform. I appreciate there is already an Ogre 2 version in a separate branch, but thats not really going to be used. We can easily add an error message in Cmake that warns if not using >=2.1. This issue is that it supports anything above Ogre 2.1, and you dont want to have to change the cmake scripts every new Ogre version, or add a new platform for that matter! |
I agree, that having 2.1 name might be bad idea. |
Makes sense, since Ogre 2.0 won't even be released as stable. Should we rename it back to Ogre2Platform scrawl? |
True. And I'm starting to think that having 2.0 and 2.1 platforms in the main branch at this point might not be a good idea after all. This is how I see it:
IMO, we should merge your work to a new ogre2.1 branch and keep it there, until there is a stable release. Just fix the merge conflicts and we should be good to go. |
…ng added during renderQueueStarted - Please note the custom compositor pass is effectively grafted from Scrawl's Ogre2 branch
I agree, backout the rename changset and for now just have a separate branch for Ogre 2.1 as it is not 'stable'. I have a number of changes that can be found here; |
On a side note, how do you request a pull request to go into a new branch in github!? |
You can't, AFAIK. |
Hey al2950, We are renaming the platform today, can you create your pull request so we can merge in our fork? Also, scrawl, we discovered we can change the base our fork is using, so we can actually set the pull request to go into any branch, what I need is a clean Ogre2.1 branch in MyGUI rep so we can redirect our fork to it and create a new pull request. |
Done. |
I have just noticed another issue regarding how the dummy movable object is created, this needs to be fixed but is not an immediate issue. Would you like me to create a pull request on what I have done, or are you happy to wait until I have sorted it? |
We can wait, let us know once you finish it, meanwhile we'll fix the merge conflicts. |
…r which means it would be processed as if it was a scene object on every pass. -Fixed minor memory leak
Please can you reverse the 'Renamed to Ogre21Plataform' commit? NB I have fixed the MyGUI_FilterNoneSkin.cpp issues in my local fork It causes too many headaches when merging with my stuff, and I dont get GIT as every time I try and revert the commit in my local repo the revert commit disappears when changing back to my branch. I really dont understand why so many people prefer GIT over Hg!! |
@al2950 It's done, we renamed everything back to Ogre2. We didn't revert the commit because there were files that weren't named correctly before that commit. |
Conflicts: CMake/Utils/MyGUIConfigTargets.cmake
Conflicts: CMake/Utils/MyGUIConfigTargets.cmake
I created a pull request a few days ago to DotWolff fork , but seems no activity. I could create a pull request directly to this fork if people wanted? |
MyGUI Ogre 2.1 updates
Could you create a new pull request to pull these changes into the new Ogre2.1 branch instead of the master? (Or edit this one) |
New Pull Request created: |
Can we close this pull request, since #86 was accepted? |
Support for ogre 2.x using OpenGL3.x+ and DirectX11.
Check option 8 in platforms for Ogre 2.x.
http://www.ogre3d.org/forums/viewtopic.php?f=25&t=83569