You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I kind of don’t know where I should address it but there are a few changes to this engine since 2007 my project is old and linked to an older version of Axiom. I wanted to get my client upgraded to DirectX11.
I been looking for a change log to see how to address my internal errors making calls to obsolete functions. BUT that is one of the smaller issues.
Okay, I have the current Git cpp version of Ogre which I build my C# exports and then I added some function to the library source and recompile it to a new library. I made headwind into the old multiverse files until I needed to access the buffer.
The library Image.cs needs to create a buffer. I pass it as byte[] * but the Image
Error CS1503 Argument 1: cannot convert from 'byte[]' to 'org.ogre.SWIGTYPE_p_unsigned_char'
Error CS1503 Argument 1: cannot convert from 'byte[]' to 'org.ogre.SWIGTYPE_p_unsigned_char'
Okay so of course suck = new SWIGTYPE_p_unsigned_char();
Error CS0122 'SWIGTYPE_p_unsigned_char.SWIGTYPE_p_unsigned_char()' is inaccessible due to its protection level.
If you get the Type of SWIGTYPE_p_unsignedchar_chr it does come back as byte[] and not a pointer to byte[]
I kind of don’t know swig that much. I’m trying to decide if it’s in the Swig compile files or if it is addressable inside the cs source. Actually I am a little concerned on how much the conversion is going to hamstring Ogre output to the frame buffer. Almost tempted to rip that out and use the old library and make using statements to point to that section.
Anyway, I thought it may be a issue addressable on your end.
The text was updated successfully, but these errors were encountered:
I think I'll rip the provokes and do direct access to stream. Like I said this reduces the clock cycles and since MV controls the library uses its own scene manager, it does this every frame. I don't think it will affect the Ogre threading since I'm calling Ogre allocation to get my pointers anyway.
paroj
changed the title
Pointer issue
Image::loadDynamicImage not correctly wrapped
Jan 13, 2024
paroj
changed the title
Image::loadDynamicImage not correctly wrapped
Image::loadDynamicImage not correctly wrapped in C#
Jan 13, 2024
I kind of don’t know where I should address it but there are a few changes to this engine since 2007 my project is old and linked to an older version of Axiom. I wanted to get my client upgraded to DirectX11.
I been looking for a change log to see how to address my internal errors making calls to obsolete functions. BUT that is one of the smaller issues.
Okay, I have the current Git cpp version of Ogre which I build my C# exports and then I added some function to the library source and recompile it to a new library. I made headwind into the old multiverse files until I needed to access the buffer.
The library Image.cs needs to create a buffer. I pass it as byte[] * but the Image
Error CS1503 Argument 1: cannot convert from 'byte[]' to 'org.ogre.SWIGTYPE_p_unsigned_char'
Ok so that is easy fix??
SWIGTYPE_p_unsigned_char sucks;
image.loadDynamicImage(sucks, (uint)pageSize, (uint)pageSize, PixelFormat.PF_A8);
Error CS1503 Argument 1: cannot convert from 'byte[]' to 'org.ogre.SWIGTYPE_p_unsigned_char'
Okay so of course suck = new SWIGTYPE_p_unsigned_char();
Error CS0122 'SWIGTYPE_p_unsigned_char.SWIGTYPE_p_unsigned_char()' is inaccessible due to its protection level.
If you get the Type of SWIGTYPE_p_unsignedchar_chr it does come back as byte[] and not a pointer to byte[]
I kind of don’t know swig that much. I’m trying to decide if it’s in the Swig compile files or if it is addressable inside the cs source. Actually I am a little concerned on how much the conversion is going to hamstring Ogre output to the frame buffer. Almost tempted to rip that out and use the old library and make using statements to point to that section.
Anyway, I thought it may be a issue addressable on your end.
The text was updated successfully, but these errors were encountered: