#Galcon commands not working update
#Galcon commands not working archive
#Galcon commands not working software
#Galcon commands not working windows

So calling a wrapped product a wrapped product is like a big warning sign that says be happy if it runs but don't expect it to run.

#Galcon commands not working software

You need to keep many versions of the same software in to make different wrapped products run and and and and.

#Galcon commands not working update

Features doesn't work / when you move it from one pc to another it behaives completly different / most of the time additional libraries and the wrapping software never gets a update for new libraries when they come out. That for many reason's Out of 10 wrapped products (i don't call them all games) 8 fail to deliver a seemless, short- and longtermstable experience. Wrapper has become a negative word on linux. So what is the real matter with the word wrapper. It can even be faster if you have a better implementation than the original as wine has already prooven (not always a good thing as you can see on dosbox adjusting cycles).

#Galcon commands not working archive

But a good 'wrapper' can archive a close to the original feel. A 'wrapper' can never reach the quality (or 100% same deal) of a native application and if only for the above mentioned reason (compare the reimplementation with the original). This issues range from performance / functionality to stability and longterm runability. The big issue VP or the author of the thread might have with being called a wrapper is, that 80% of the wrapped products people experienced on linux have issues.

So while valve / aspyr / feral can compare their source with the original source, VP or wine and even dosbox will never be able to compare their source with the original source of the original os.

#Galcon commands not working windows

You can much easier compare if 2 functions do the same and their execution time in every step than you can say eOn behaives exactly the same as windows and has the same execution time. They only use it small circumstance when the effort to port this part would crush any business and when there is for sure that there is nearly no performance impact when they do it that way. The difference between Valves / Feral's and Aspyr's ports are they try not to wrap a complete vcrun + directx + directsound + whatever is needed for the game on top to make a game run. Basically many programmers use this technic and it has even it's own pattern -> Valves togl, Ferals indirectx or whatever aspyr use might do some wrapping (translation from one type of function call to another type of function call) too. So wrapper itself is nothing bad if done right. It totally matches.ītw that also totally matches for any wine / dosbox based games delivered throu steam. > see the description on wikipedia for a wrapper. So basically the game itself is packaged in eOn but is itself a PE executable. That is supported by VP's own description of the software (It is a fully native implementation of essential Windows technologies (such as Direct3D)). The witcher 2 port starts a ELF File to setup an enviroment where the PE executable can run. ELF executables need a linux enviroment to run. PE / Windows executables need a windows enviroment to run. 'In computing, an executable file or executable program, or sometimes simply an executable, causes a computer 'to perform indicated tasks according to encoded instructions,' as opposed to a data file that must be parsed by a program to be meaningful.' 'Wrapper generally refers to a type of packaging, such as a flat sheet made out of paper, cellophane or plastic to enclose an object.'Īs far as analysis show the executable seems not to be change and included in a containerfile with the extension vps (egrep 'This program cannot be run in DOS mode' witcher2.vpfs). Or you know, don't, and rather act nice and encourage more ports by rewarding quality work and encouraging improvement where the quality isn't great - that way, we get more games and the community won't be perceived as so hostile. Now - if you really think that isn't native, go after Aspyr, Feral and Valve too. But do not complain about it not being native when it clearly is. So, complain about the quality of the port, it's far from ideal. They did what everyone does, as it's cheaper to do this than write a new renderer, and guess what, it works.

But the constant spewing of 'it's a wrapper, it's a wrapper' from people here is just ridiculous. The fact the port has some terrible performance issues is a completely different problem. That's about as native as those ports get, and it's FINE. I just wanted to take a moment to say this one simple thing, because some people in this subreddit keep repeating this misinformation as if they knew what they were talking about.ĮON is not a wrapper.