Skip to content
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

can the direct X versoin of monogame be used with this for windows? #8

Open
damian-666 opened this issue Nov 12, 2023 · 2 comments
Open

Comments

@damian-666
Copy link

And can it be moved to net8?
and windows desktops
for Web ( via Angle maybe) ,, and windows desktops

from looking at the code it seems so..if no one hs tried i might have a go at it..
And can it be moved to net8?

@OmidID
Copy link
Contributor

OmidID commented Nov 12, 2023

Hello @damian-666
If you can create a PR it would be great.
I expect we should be able to do it.

@damian-666
Copy link
Author

damian-666 commented Nov 19, 2023

i'm on the dock branch now so ill try get back to it.. i;m not that good at git when there's multiple forks..ill have to make a new branch , i'm forked from the dock version. its probably a matter of just linking the other monogame package and since you are using a render target. the copy might be faster in net8, ...don't think performance should be bad, its working on mac and https://twitter.com/wieslawsoltes/status/1621277580316884998?s=20

might be able to do this: if somehow is getting horrible performance... i dont..

-noteit gets recreated on the resize..
-but i think best to got to net 8 first if anyone is getting bad frame rates. dx for win, gl for other.
pthen do a thread stack traces and breakALL a few times and see what's hangin up( its always -stops where is semaphore is hanging.) fi its a real bottle neck like 5 fps.
-then maybe to consider unsafe.. ( not having to build MG i hope)
i-m build UI around teh MG windows so.. i don't need to put UI in that...
-the windowing way will not make that easy.. ( ui will fill areas that it shouldn't)
-then i saw that marc stan was using a screen full buffer for multiple tabs. that was enough to set different viewports since there are no transparency from one tab to another.. that kept it more efficient.
-i only plan to have one tab working.

https://stackoverflow.com/questions/17549123/c-sharp-performance-using-unsafe-pointers-instead-of-intptr-and-marshal

i'm using only one tab with the view.. and i stay off the ui thread. im seeing a lot of flux in Avalonia right now... and i'm interested in blazer hosting but probably don't need avalonia for that , not sure yet..KNI will support it but maybe with issues. this way might be better. just not using the dock.. but i could get to it next week.. right now i'm swamped..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants