- The Porting Team
- → Most Liked Content
Most Liked Content
Posted devilhunter on 31 May 2011 - 07:37 PM
Get this Update via the Version Check & Automatic Update button.
+ CXEx Central (2.2.5)
feature: 'Did you know' Tips feature
change: CXx Upgrade also upgrades CXEx v6.x Wrappers
change: Grim Reaper now native with Quotes
bugfix: changed some message dialogues
+ CXEx Wrapper(6.2)
feature: Wrapper Checklist
feature: Startup Tools (eConsole and Explorer)
feature: Startup Screen Settings now has Icon preview
feature: Startup Screen Settings can now be refreshed
The Wrapper checklist feature is just a little reminder gimmick, but since it's frontmost on the settingsapp, it should be very helpful to people.
Also click the 'Did you know...' Idea Blub in Central to get some tips. Click for random notes. May not be obvious to click it now, but i'll get that more obvious-er somehow.
Grim Reaper also has a nice Window with some nice quotes about him ^_^
Posted mengchhorn on 30 March 2011 - 05:51 AM
Posted Darklord6229 on 07 December 2011 - 07:38 PM
The error says word for word:
Failed to find a supported hardware rendering device. Ensure that your system meets the minmum requirements for Company of Heroes\. Verify that DirectX is properly installed and that you have the latest drivers for your system.
Thank you in advance,
Travis Cohen aka Darklord6229
Posted thanoulas on 25 April 2012 - 11:20 AM
I've made a lot of progress, but there are a few things that still need to be done, the most important being the installation of the game without the need for windows or a VM.
This launcher is used by HiRez Studios for their other games as well, and the result could end up being a fully featured Launcher for all of them (Smite, Tribes Ascend, Global Agenda).
Here is a screenshot of the Work In Progress:
The project is being developed in Objective-C# / Mono 2.9 and Wineskin
It's a pretty big project, so any help would be appreciated.
A private and a public beta will follow, before the release.
You will need to download approximately 3GB from the net!
Oh, and admins / mods I'd appreciate a Member's project thread! Thanks!
Final List of Private Beta Testers:
Special Message for the Private testers:
Please, do NOT redistribute the files that you will receive once the private beta starts. Their purpose is to make a stable enough version to share it with everyone, and the private beta is not going to be anything like that. If you do share the file with anyone and that comes into my attention, you will receive my eternal fury
and I will make sure that the launcher won't work in your machine again
Once the first working version is ready, you will receive a PM with instructions and the link to the file.
You will then need to post here your results.
Please document everything you do step by step, in proper readable english (blinx )
You will need to go through the setup process at least 3 times, each time doing something different. Random keypresses and attempts to f%^k up the launcher are more than welcome. Please, try and break it
MAY 2, 2012
The first test is underway! Instructions and links have been sent to the private testers!
I am going on, trying to find a way to decompress the archive! After that, it's just a matter of porting!
ACTIVE BUGS/TASKS LIST that need to be resolved BEFORE the PUBLIC BETA:
- CRC check the downloaded file(s)
- Retry download if CRC fails
- Timeout download and retry
Extract the .dfc file
- Make the wrapper
Posted olive77 on 30 June 2011 - 10:27 AM
I've try using CXEx Central update version to install CXEx Black Diamond, but than when i try to open left4dead2 it keep telling me Engine requirement CXZ Black Diamond Engine was not installed.
I didn't want to trouble you, but if you would link me up some free site i could load without having the site benign band or couldn't get thought.
Posted devilhunter on 13 May 2011 - 02:00 PM
Get this Update via the Version Check & Automatic Update button.
Bugfix: fixed the error message from some dialogues when pressing the 'cancel' Button
Change: changed the Interface slightly for the Compression Utilities
New: Legacy Upgrades - CXEx to CXZ Engine Linker. This option allows you tolink over your existing CXEx Engines to the old CXZ path.
This allows you to run CXZ ports with the new CXEx Engines.
(Administrator User Password required, since the CXZ Engines were on the root Volume)
First Update to CXEx Central.
Testing out the new Update system, but it should work flawlessly.
Posted jaki on 02 February 2011 - 01:56 PM
Posted devilhunter on 03 December 2010 - 12:32 AM
About the CXEx Project:
CXEx is basically the successor of CXZ, but with a lot of modifications that make it a better system than CXZ or CXS ever was.
The Idea of CXZ was slimming down the huge Wine Wrappers that could go into the 160+ Megabyte range, without any Application or Game files.
This system proved to be very effective and popular, but it also split the Userbase in two groups, one that preferred CXZ (external Engine) for it's small footprint and effective Engine sharing capabilities; and the other Group preferred the 'complete' Package that was still possible with CXS (internal Engine), where the Engine was integrated and you didn't have to install an Engine to make it work.
Both systems had positive and negative aspects in this sense, but what if there was a system that would fuse both CXZ and CXS together and eliminate all of the negative aspects?
CXEx is now the result of this fusion.
All CXEx Wrappers carry their Engine inside the Wrapper (like CXS), but in a compressed format.
Also all CXEx Wrappers can share a single Engine on a system (like CXZ).
Every CXEx Wrapper has now also a built-in Startup Screen where a Port displays the Wrapper technology it is using and Information about the included Port. Think of it as a included Readme file for every Port.
CXEx Central is now the Central Hub for the CXEx Wrappers /porting with CXEx
Look in the App Database with which Wine version you'll have the most success with, and use the corresponding CXEx Wrapper from CXEx Central.
Alternatively, go from the newest to the oldest CXEx Wine Wrapper, you'll get different (better/not better) results that way.
Every CXEx Engine has a different compatibility, older Games work better with older CXEx Wine Wrappers for example.
Compatibility will always be the same (perhaps a little bit lower or a bit different) as CrossOver, so it's up to Codeweavers to make this better. If you want to use a Wine Wrapper that isn't dependent on third parties & modifications, check out Wineskin.
A bit of info on CXEx: (articles are not finished yet/work in progress, it takes a lot of time to write these...)
What is CXEx and how does it work?
For example somebody gives you a CXEx Ebony Port, and you do not have the Engine installed for this Wrapper.
Upon first launch, the CXEx Ebony Port looks if there is already the CXEx Ebony Engine installed on your System.
If it is from a previous CXEx Ebony Port, it uses that Engine and runs the Port.
If the Engine isn't there on your system, the CXEx Ebony Port will automatically extract the included Engine into your system to run the Port.
Couldn't be easier. No more downloading and installing various Engines, and also the Wrappers are relatively small compared to other Wrappers because of the Ultra 7-zip Compression of the Engines.
Upon the first start of a CXEx Port a Startup screen will be displayed as well, where the Porter has (hopefully) included some Information about the Port.
Why are there multiple CXEx Wrappers and Engines?
CXEx has it's roots in WINE.
WINE is a code translation Software that was developed on Linux for 'emulating' ( see Wine Is Not an Emulator) Windows Code on their Platform.
Each new Wine release adds compatibility for certain Games and Applications, but breaks some compatibility for others.
Like some Games only work with WINE version 1.1.18, and don't work with the newer 1.2.1anymore.
Traditionally Linux users have to make a choice for updating their installed WINE Engine for compatibility in some newer Games and Applications, or risk making already installed apps unusable or adding bugs to them due to some differences in the new Engine.
We have a tremendous advantage with the different WINE Engines, because we can let each Game or Application talk to a different Engine without deinstalling another Engine.
Since each of the CXEx Wrappers use other Engine files, this gives us tremendous potential on porting Games and Applications.
CXEx Frequently Asked Questions
CXEx Porting Tutorial - (outdated Tutorial, needs a rewrite)
CXEx Tips & Tricks Page
CXEx Central (main CXEx App)
CXEx Settings (CXEx Wrapper Settings)
CXEx Launcher (part of the CXEx Wrappers)
Creating CXEx Ports for yourself and others / Porting with CXEx
(5 MB Download)
I've decided a few months ago to get into Xcode a little bit, with no basic knowledge of anything cocoa or object-c.
I've pondered a while on what i could do with it and decided i would rewrite all my previous Terminal and Bash apps & tools with Xcode and see what would turn out from that in the end.
The app with the most benefit from that would be the old CXEx app.
Well, you know how the old CXEx & CiderX & CXZ Porters are, plain, script-list, not so mac like.
A few weeks later i've come up with a new design for the whole thing, and put in additional features and settings. Then some more. Then lots of other things as well.
Basically i didn't want to release the thing since i said i'd shut it down, but i figured you guys would have the most use out of this app.
To the handful that are still porting with CXEx, that is....
Well, long story short, here would be my idea on how a 'native' management app should be for creating Wrappers.
This app works similar to Wineskin Winery, with downloadable content, changeable settings and lots more.
CXEx Wrappers got a huge upgrade as well, with more efficient launcher code and now a verrrry customizable startup screen as well. (got rid of the helper apps inside the Wrappers as well)
Basically everything is new and improved, and very thoroughly tested.
Besides the actual CXx base code, which doesn't fall into my set of skills.
doh's the person to talk to for improving it, and if you want to get crankin' on the CXx base code yourself, feel free to grab it here.
But it worked as well as the original CrossOver does, so there's little room for improvement. (besides the shutdown bug)
CXEx Central may be a bit confusing at first, but every button/feature is documented.
Press the (?) Button in the Wrapper settings to show descriptions; go the the [ Online Manual ] Tab in Central for a detailed explanation on how things in Central work.
If it's still too confusing, stick with Wineskin Winery; Winery was designed more for new users to porting, while i took the more experienced approach.
The whole thing is pretty easy to use, and lots of cool new things to choose from, so knock yourself out with the new CXEx.
I'd figured i'd give you all the option to mess around with Central / the Wrappers / the custom Launcher first, before i spend another two weeks writing tutorials for it; since i've been mostly done with the app for some weeks now.
Of course, i've got a feature list to come via updates that's as long as my arm, so i'm gonna add new things via my own Auto-Update implementation soon. (eff you Sparkle)
The heart of CXEx, or more like CXSkin (by doh123) as it once was, is available as a source here.
CXEx Source Code
The whole CXEx Package (CXEx Central + CXEx Wrapper+Settings) is however, not open source, since it's my own implementation built on top of the CXSkin Source. CXSkin died years ago, and development of the core with it.
If you want to pick up the breadcrumbs that got left behind, feel free to do what you like.
Posted ValkTuna on 20 October 2011 - 02:21 PM
Fontconfig error: Cannot load default config file
Fontconfig error: Cannot load default config file
Fontconfig error: Cannot load default config file
X connection to :3595.0 broken (explicit kill or server shutdown).
Anyone has any help on CXEx opening a launcher.exe and launching the game from there? Thanks. :)
Posted HiPhish on 20 May 2011 - 09:15 PM
This must be the weirdest bug ever. I don't even mean the folder for the content of the wrapper (right click -> Show Package Contents), but litereally the folder (e. g. "Games" or whatever).
It is the finder window, nothing else, I checked so many times, quit every application, it is always the finder window. The Icewind Dale theme is going to haunt me tonight. Changing the folder and opening the new folder caused the exact same issue. Putting the wrapper onto the desktop worked fine, as long as there was no finder window of the desktop open. Launching the game from a stack works perfectly as well.
I even tried the same thing with Forklift, another file manager, but nope, everything works fine. It is ONLY the Finder.
But it doesn't just affect icewind Dale II. King's Bounty gets that weird bug where characters are not drawn except for a few polygons floating.
I don't know about IWD2, bu in King's Bounty there is usually an override for msvcrt.dll set in Winecfg. Maybe that helps.
I would upload my ports, but my internet connection wouldn't be able to handle it. If there are some logs I could post to help out, then please someone tell me what to post.
Posted plasticman55 on 19 May 2011 - 04:06 AM
11-05-19 12:03:19 AM CXX11Server Unable to load nib file: LauncherMenu, exiting 11-05-19 12:03:20 AM osascript Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find: /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper 11-05-19 12:03:20 AM [0x0-0x92092].com.portingteam.CXExSettings 2011-05-19 00:03:20.604 osascript Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find: 11-05-19 12:03:20 AM [0x0-0x92092].com.portingteam.CXExSettings /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapper 11-05-19 12:03:20 AM [0x0-0x92092].com.portingteam.CXExSettings osascript: OpenScripting.framework - scripting addition "/Library/ScriptingAdditions/Adobe Unit Types.osax" declares no loadable handlers. 11-05-19 12:03:23 AM CXX11Server Unable to load nib file: LauncherMenu, exiting
Could someone help please?
Posted devilhunter on 22 February 2011 - 09:26 PM
Just a few days ago i said i wouldn't do anything more with CXEx, yet i seem to be driven to experiment on it :D
With everyone drooling over one-app-interfaces for Wrappers instead of app based functions, i tried my hand at an Interface.
I liked the app-based structure of Wrappers, you could do specific things in less time than navigating a huge interface.
But, this all-in-one thing may have some benefits as well as i've found out, and the multiple-app interface did have some very annoying aspects.
So i've thrown out all CX apps in the Wrapper, and also i got rid of the single 'Port Information.app' and 'Engine Installer.app' in a CXEx Wrapper, latter one was a GUI dummy anyway.
Because of these steps i had to rewrite the Wrapper and most of all previous app-based programs almost from scratch, to get rid of all apps and to make one GUI for everything.
So this GUI doesn't work on normal CXEx Wrappers.
With this in mind, i didn't plan to release this, but i wanted some input about the CXEx Settings GUI from you guys anyway, perhaps i'll push out one last Update to CXEx with the reconfigured Wrapper and the universal Settings app.
New Inside of the Wrapper:
So here's the GUI:
Launching Wrapper with pressed option key gives you this:
Tab Screen 1:
Tab Screen 1 is pretty clear.
Tab Screen 2:
Tab Screen 2 has everything you'd need for installation or file management, even the Grim Reaper has found a home.
(isn't the little creep cute ^^ )
Tab Screen 3:
Tab Screen 3 has a mini-preview of the Startup Screen on the current Wrapper, and there are some buttons which let you open the banner & text file in your editors.
Also some icon import options, import .icns file or convert a picture into a .icns file and import it.
Under all that is a preview button for the call to the normal Startup Screen.
Tab Screen 4:
Engine Changer, custom app maker, edit reg files, view log files.
So nothing new here in terms of functions, just every app that was there previously in one GUI.
What could i do better? Which screen should be the first tab? Are the buttons grouped well together?
As said, this may not get released at all, i was just experimenting on a all-in-one GUI; and almost every fuction currently relies on a bash-call, since i'm just a XCode beginner.
Aside from that, it's not just a dumb .nib file in Xcode, but a fully working Interface for a frankenbuild of a CXEx Wrapper.
While Drakulix always tells me to 'buy the damn XCode book' to get more into XCode, i plan on doing things the way i've found out pretty much everything, by pressing all buttons and seeing what each one does
Seems to work out pretty well so far :P
Posted devilhunter on 26 January 2011 - 04:45 PM
There are some other cases other than the vcrun command that use this lowercase variable.
I'm not sure this helps generally because Winetricks is so buggy (sometimes a package works, sometimes it doesn't, and people get misled by the cache), but it's worth further testing.
Perhaps this works for some other winetricks annoyances as well.
Posted devilhunter on 09 January 2011 - 03:34 PM
Changes and new Features include:
- new Startup app: CXWrapper
no more pesky plist file editing, do it now from the nice GUI
(Port Name / X11 Quick Kill / Executable file)
HUGE thanks to Drakulix for the code.
Also the Wrapper itself and the subapp in /MacOS will get automatically renamed via changes in the Port Name field in the CXWrapper app.
The CXWrapper app looks like this:
- updated the CXEx Wrapper System to 5.1
- improvements in the auto-update code, now minor updates like 0.0.1 updates are possible, 7zip compression for smaller updates
- custom Graphics in the popup Dialogues
- minor fixes, The CXEx Porter will refresh it's Engine cache upon first launch after update
Grab this update via the Auto-Update
Posted LeVideoBro on 27 August 2012 - 10:11 PM
I know, I'm an idiot.
Posted Lux on 14 December 2011 - 01:36 PM
Posted LameSaint on 28 September 2011 - 10:36 PM
Posted ThiefFan on 01 August 2011 - 07:11 PM
I have a fresh install of CXEx Central running on Lion.
When I try to open the wrapper I get an error window saying:
"You can't open the application CXExWrapper.app because it may be damaged or incomplete."
I'm stumped, this is a fresh install I tried because the same thing happened on the previous installation.
Clues/beatings appreciated :)
Posted Gcenx on 02 April 2018 - 04:01 PM
Last Updated - December 29th/2019
Current version Wineskin-22.214.171.124
DISCLAIMER WINE ON MACOS DOES NOT SUPPORT DIRECTX10/DIRECTX11/DIRECTX12!
I CAN NOT SUPPORT WHAT WINE DOES NOT SUPPORT!!!!!!!
List of modifications in the Wineskin App (WineskinApp)
- The Auto-detect GPU feature should never cause malfunction in the port;
- The Auto-detect GPU feature should have a much bigger accuracy and detect the memory size of integrated video cards as well;
- The Retina Mode can be enabled from the Screen Options window;
- Kill Wineskin Processes should kill ALL Wineskin processes. (Wineskin-126.96.36.199 no longer tried to launch wineserverkill.exe)
- Images (not .icns files) should also be accepted has wrapper icons;
- LNK files should be able to be selected as a port's run path, so Wineskin can extract the path and flags from it;
- Winetricks installation can be silent (with no windows) so it's much faster;
- Disables X11 option if XQuartz is not installed.
- The first Advanced tab (Configuration) should be much more simple in the first section:
- The Windows EXE should use Wineskin syntax, including the drive and the flags, (eg. "C:/Program Files/temp.exe" --run) instead of using a macOS reference path (eg. /Program Files/temp.exe) and the flag apart (eg. --run).
- Advanced Tab "Disabled Gecko installation" checkbox (allows install to be enabled for "Wrapper Refresh" )
- Able to detect XQuartz installed via macports
- Integrated fntoggle directly into Wineskin.app, now you can have Standard F keys during wrapper usage.
- Wine versions not compatible with "mac driver" will have that option disabled.
- Fixed a long standing bug from official Wineskin "Command Line Wine Test" now works as intended.
- Ability to map Command as Ctrl (wine 3.17 and above)
- Ability to map Option as Alt (wine 1.7.4 and above)
- No longer alters "EXE Flags" meaning if you require a "/" it's no longer changed to a "\"
- Rebuild Wrapper now resets the MAIN EXE to nothing.exe
List of modifications for the Master Wrapper (WineskinLauncher)
- Many fixes when dealing with newest engines.
- Closes XQuartz on exit if used.
- Mono is never installed.
- Able to use XQuartz installed via macports
- fntoggle will be set on launch and unset on wrapper exit. (If enabled from wineskin.app)
- gnuTLS included so supported engines can use it, aka using WineCX18.5.0 Steam will download again.
Added ffmpeg- removed to avoid Legal Issues
- Now ntlm_auth is within wstools.bundle/bin
- Now checks $HOME/Wineskin/lib" for dylib's
- Added a fixed version of NCurses without this the fixed "Command Line Wine Test" will give terminal errors
- Gnutls support requires OSX10.9!
- Bundle ID is now generated from appName
- wine64 used over wine within 64Bit wrappers
- Font Smoothing enabled on wrapper creation
- Support wine32on64 in both normal and wow64 builds
List of modifications in the Winery App
- Improved - Engine Ordering.
- Connects to custom WineskinServer.
- Downloads engines hosted on WineskinServer.
- Directly download current "Unofficial Master Wrapper Version"
- "Update" feature will display when new "unofficial Wineskin Winery.app" version is available
- Wine versions that Require XQuartz to function are hidden by default.
- Able to read from a local EngineList.txt (in the same folder as Winery.app)
- Download and repack Engines from winehq
- Rebuild using Xcode10, now supports Dark Mode when using Mojave
- Correctly downloads engines again on OSX10.8
- Correctly handles wine version string for repacking.
- Correct GitHub linked used now allows files committed via “git lfs” to download correctly
With a minimum requirement of macOS/OSX 10.8.
With a recommended requirement of macOS/OSX 10.9.
Unofficial Wineskin Winery.app
Using the above just download then run, directly download the current master wrapper
Don't use keka to unpack as it currently breaks any downloaded applications after unpacking!
About Local EngineList.txt feature;
This feature was added so winery.app can read a local EngineList.txt file, create a text file with that name in the save directory as winery.app this will now override the copy hosted on GitHub , follow the correct Wineskin engine naming style to download Wine to be repacked into Engines.
WS9Wine3.15The above example would download portable-winehq-devel-3.15-osx.tar.gz and repack into WS9Wine3.15
WS9Wine64Bit3.15The above example would download portable-winehq-devel-3.15-osx64.tar.gz and repack into WS9Wine64Bit3.15
WS9WineStaging3.15The above example would download portable-winehq-staging-3.15-osx.tar.gz and repack into WS9WineStaging3.15
WS9WineStaging64Bit3.15The above example would download portable-winehq-staging-3.15-osx64.tar.gz and repack into WS9WineStaging64Bit3.15
This feature was added incase Winehq added a new wine version and I'm not able to update the list on GitHub , so if tomorrow Wine3.16 was released and compiled versions were available for download, it's possible to just make a list and add them yourself
Please make sure to clear out your users /tmp folder if you have any issues creating wrappers.
Anyone who uses PortingKit and is running OS X10.8 to 10.14 is now using Unofficial.
A Very Special Thanks to;
doh123 - For creating Wineskin
VitorMM - For the modernized code base along with all the included features!
NRG & dankoB - For Testing the initial releases