13 replies to this topic

[hmtinc]

People i have managed to get a cider 7467 wrapper
i posting the download link here for those who wish to use it .
Only problem its the eve wrapper so before u can use it u have to remove all the eve online stuff
Hope you like this wrapper

Enjoy


Click Here to download

[cluthz]

I think this was upped in "need all cider wrappers" post, but nice to have it here too.

I've found this framework to be a bit difficult, not found any real use for it yet.

Thanks a lot anyway! And keep'em comming!

[Battlefiler]

cluthz, on 03 February 2012 - 12:12 AM, said:

I think this was upped in "need all cider wrappers" post, but nice to have it here too.

I've found this framework to be a bit difficult, not found any real use for it yet.

Thanks a lot anyway! And keep'em comming!

do you know much about cider frameworks (i need help to distinguish the different frameworks)

[Drakulix]

Battlefiler, on 03 February 2012 - 07:28 PM, said:

do you know much about cider frameworks (i need help to distinguish the different frameworks)

One rule to remember.
Some frameworks are so special, that they are completely useless for the most games. They can only be helpful in custom engines.
All EVE Online Wrapper are in this category.

[Battlefiler]

Drakulix, on 03 February 2012 - 08:17 PM, said:

One rule to remember.
Some frameworks are so special, that they are completely useless for the most games. They can only be helpful in custom engines.
All EVE Online Wrapper are in this category.

thanks for the first rule

[cluthz]

Even tho a framework itself doesn't work it can contain valuable dylibs for another framework.
F.ex i hardly use dx9 dlls, because even if a framework are missing f.ex d3dx9_43.dylib, you can get that from another framework instead of using a windows dll. Same goes for libd3dxof.dylib which are often used and xaudio dlls.
Also different wrappers have different level of support for controllers and I've sometimes moving libxinput.dylibs from one framework to another to make controller work.

Maybe an idea for the new "cider tricks" is to install framework dylibs for some dx9 and some audio features since most wrappers miss some.

I see many porters (I did it myself a lot earlier too) is installing windows dlls where framework could be used instead.
My experience is that building custom frameworks are faster and more stable than dll swapping (and definitely much better than winetricks, with dx9 winetricks you override most of the libd3dx9.dylibs which slows the game down).

The problem is that there are currently no available documentation or info about what works and what does not and the whole process is pretty much trial and error.

Once CiderX2 is available I'm gonna start making an advanced guide for Cider porting which cover some ways to port I think only me and drakulix is using atm, because there is a lot more you can get working in cider, with better performance then people knows, because custom building frameworks is still an area we have explored very little.

I've also been thinking of building a cider knowledge database where unknown functions could be listed for people to use as there simply isn't any info.

[Drakulix]

cluthz, on 03 February 2012 - 10:35 PM, said:

I've also been thinking of building a cider knowledge database where unknown functions could be listed for people to use as there simply isn't any info.

Something like this would be nice.
Only writing down all experiences we had with our cider ports, would help a lot of people.

[Battlefiler]

Quote

F.ex i hardly use dx9 dlls, because even if a framework are missing f.ex d3dx9_43.dylib, you can get that from another framework instead of using a windows dll.

thanks for your reply and from witch cider wrapper du you use the dylib (i tryed it with one from 72XX (wont work))

[cluthz]

Battlefiler, on 04 February 2012 - 12:04 AM, said:

thanks for your reply and from witch cider wrapper du you use the dylib (i tryed it with one from 72XX (wont work))

It depends what your engine is.
If you have a 4k engine you preferably wanna use one from a 4k one, and a 7k engine, from another 7k engine.

I've used succesfully the dlls from 7113 in 7081 (skyrim port) and managed to shrink the sys32 folder from over 100mb to less than 25 mb, with replacing dx9 and xaudio dlls with dylibs.

[Battlefiler]

cluthz, on 04 February 2012 - 01:41 AM, said:

It depends what your engine is.
If you have a 4k engine you preferably wanna use one from a 4k one, and a 7k engine, from another 7k engine.

I've used succesfully the dlls from 7113 in 7081 (skyrim port) and managed to shrink the sys32 folder from over 100mb to less than 25 mb, with replacing dx9 and xaudio dlls with dylibs.

Thanks i will try if this work and can you explain me how to Installation .patch file in wineskin (i made a Topic in wineskin Custom engine)

Thanks you are a Great help

[elGrafico]

Hi cluthz / Drakulix,

Very interesting reading, wish I knew more, so I would really appreciate the resource you are discussing!

Does replacing the windows dll's with Cider port dll's and removing unnecessary dll's from the windows folder improve performance, if so what kind of gains are possible?

[DankoB]

I can understand the want to refine the wrapper down to as little as possible but when it really comes down to it 75MB isn't going to make a huge difference, especially now that a HD is 500GB standard.

I'm also interested in elGrafico's question.

@ Battlefiler

You can follow this old tutorial - http://portingteam.c...-custom-builds/ - to patch the wine source.....once the source has been successfully patched you ned to use Wineskin Winery to complete the Wineskin engine build....unfortunately patching Wine will not help with Cider ports.

[cluthz]

DankoB, on 09 February 2012 - 12:29 AM, said:

I can understand the want to refine the wrapper down to as little as possible but when it really comes down to it 75MB isn't going to make a huge difference, especially now that a HD is 500GB standard.

I think you misunderstood me.
The issue isn't that wrappers get big, but that you override functions that already are present in cider's own framework and thus slow things down.
There is a reason why most dll functions are built into framework instead of using dll files. Of course transgaming has quite a few dll files they use in the sys32 folder, but more and more functions are built into the framework instead.
If you do a full directX installation in a recent game in cider, instead of relying on the libd3dx9_x.dylibs and do a benchmark you'll notice the performance has dropped significantly, same with wine although wine is usually handling it better.

[Battlefiler]

DankoB, on 09 February 2012 - 12:29 AM, said:

I can understand the want to refine the wrapper down to as little as possible but when it really comes down to it 75MB isn't going to make a huge difference, especially now that a HD is 500GB standard.

I'm also interested in elGrafico's question.

@ Battlefiler

You can follow this old tutorial - http://portingteam.c...-custom-builds/ - to patch the wine source.....once the source has been successfully patched you ned to use Wineskin Winery to complete the Wineskin engine build....unfortunately patching Wine will not help with Cider ports.

thanks