Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Linux news
#1
Hello guys, here are some news on the Linux front. Yes I know, I ought to do that more regularly Tongue

In short progress is slow but steady Smile

* A port to wxWidget 3.0 was done recently, mostly because Debian will drop wxWidget 2.8 . It is enabled by default but wx2.8 is still there, you can restore is with the -DWX28_API=TRUE build option.
  • Most of regressions were fixed so it will work as bad as before Wink No I'm kidding, it actually works better on my PC. Feel free to test it.

  • Unfortunately Windows is still blocked to wx2.8, contributions are welcome (first step is to add a wx3.0 library build)

  • Some wxWidget libraries depend on GTK3. PCSX2 code was updated to support GTK3 but wxWidget is not as stable as expected. Nevertheless, you can enable GTK3 with the -DGTK3_API=TRUE build option (debug build only).

* Better support of cross-building (thanks to Micove). Cmake used to select wrong libraries between lib32/lib64/lib/...
  • You need to use this new option on 64 bits machines -DCMAKE_TOOLCHAIN_FILE=cmake/linux-compiler-i386-multilib.cmake

  • Note: build.sh will do it by default, so just build.sh

* Support of AVX
  • code is now compiled with -march=native to support all optimizations of your CPU. It can be disabled with the -DISABLE_ADVANCE_SIMD=TRUE build option (for example distribution or inside VM)
  • Note: GSdx (Linux) needs a couple of updates to support SSE4x. Again contributions are welcome, check this issue https://github.com/PCSX2/pcsx2/issues/438

* New (nearly) playable game: Bouken Jidai Katsugeki Goemon
  • Full support of MMU with the interpreter, and a dedicated game-fix for the recompiler
  • No more TLB misses! (full story will be posted in http://pcsx2.net/developer-blog.html in coming weeks).
  • Crashes are reported on GSdx windows not sure on Linux.

* Finally, Ubuntu PPA is up to date with the latest feature. However, Ubuntu 12.04 support is discontinued!



Ongoing work (aka the plan for the next months):

* port lilypad to Linux
  • It will bring Force Feedback, MultiTap and it might work better in several games.
  • I'm close to have keyboard support but help would be appreciated to build a full GUI. Please contact us if you are interested.
* port GSdx to openGL 4.5
  • A long time ago, I planned to update the code to support GL_ARB_direct_state_access. It was postponed because no official driver supported it.



Last but not least, thanks to all contributors. Even the smallest patches are a big help.
Reply

Sponsored links

#2
I'm not desperate for contributions Tongue2 but I know the difficulty to find a task to do.

By the way, if you doesn't like those contribution idea, feel free to pick another in https://github.com/PCSX2/pcsx2/wiki/Cont...DO-List%29

And good news, keyboard is working with lilypad Smile
Reply
#3
Glad to see the progress on the Linux Version, looking at the latest news Gaming may not be a Windows hog in the next few years Tongue
Reply
#4
The progress especially over the last 3 years for Linux version brings a manly tear to my eye. Because of the progress, I haven't had Windows on my computer for over a year now. And to me...that's awesome.
OS: Linux Mint 17.2 64 bit (occasional Antergos/Arch user)
(I am no longer a Windows user)
CPU: Intel Pentium G3258
GPU: Nvidia GTX 650 Ti



Reply
#5
wow, it's really a great progress. considering, only gregory worked on the linux version.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction

[Image: 84t1dRu.png]
Reply
#6
Thanks for sharing. Rep+1.
Reply
#7
Lilypad update. Joystick supports is mostly done. The biggest issue so far is a nice gui...

Quote:Found input device => bustype:3, vendor:46d, product:c29b, version:111
Name:G27 Racing Wheel
FULL Axis info 0=>16383, current 8192, flat 0, resolution 0
Scale not supported
FULL Axis info 0=>255, current 255, flat 0, resolution 0
FULL Axis info 0=>255, current 255, flat 0, resolution 0
FULL Axis info 0=>255, current 255, flat 0, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -1=>1, current 0, flat 0, resolution 0
Scale not supported
New device created. Found axe:6, buttons:23, m_rel:0

Found input device => bustype:3, vendor:6a3, product:109, version:100
NameWackoAITEK P880
HALF Axis info 0=>255, current 128, flat 15, resolution 0
HALF Axis info 0=>255, current 128, flat 15, resolution 0
HALF Axis info 0=>255, current 128, flat 15, resolution 0
HALF Axis info 0=>255, current 128, flat 15, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -1=>1, current 0, flat 0, resolution 0
Scale not supported
New device created. Found axe:10, buttons:12, m_rel:0

Found input device => bustype:3, vendor:6a3, product:f620, version:111
NameTongueS2700 Rumble Pad
HALF Axis info 0=>255, current 128, flat 15, resolution 0
HALF Axis info 0=>255, current 127, flat 15, resolution 0
HALF Axis info 0=>255, current 128, flat 15, resolution 0
HALF Axis info 0=>255, current 127, flat 15, resolution 0
HALF Axis info 0=>255, current 127, flat 15, resolution 0
FULL Axis info -1=>1, current 0, flat 0, resolution 0
Scale not supported
FULL Axis info -1=>1, current 0, flat 0, resolution 0
Scale not supported
New device created. Found axe:12, buttons:13, m_rel:0

Found input device => bustype:3, vendor:54c, product:268, version:111
NameWackoony PLAYSTATION®3 Controller
DS3 device detected !!!
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>255, current 0, flat 15, resolution 0
FULL Axis info 0=>1023, current 0, flat 63, resolution 0
Scale not supported
FULL Axis info 0=>1023, current 0, flat 63, resolution 0
Scale not supported
FULL Axis info 0=>1023, current 0, flat 63, resolution 0
Scale not supported
FULL Axis info 0=>1023, current 0, flat 63, resolution 0
Scale not supported
New device created. Found axe:27, buttons:19, m_rel:0
Reply
#8
(02-04-2015, 11:53 PM)gregory Wrote:
  • A long time ago, I planned to update the code to support GL_ARB_direct_state_access. It was postponed because no official driver supported it.

It's been some time now but if you have some seconds:
Why have you actually planned to do this? What is the advantage? How do you know that this option exists?
Reply
#9
Is that only supported in Open GL 4.5?

Direct State Access allows developers to both set and query properties on objects (textures, shader programs, frame buffers, and so on) without having to make units active or bind objects to them; programs can operate directly on the objects themselves.
Reply
#10
It is a 4.5 gl extension but it just a matter of drivers actually. It can be done on any gl3 gpu class.

Before to do an operation:
If (texture) activate texture unit
Bind object <= do a lookup and save it
Do operation

With direct access:
Do operation <= it will do the lookup but won't save it before the operation.

It will clean a bit the code especially for texture management. It is closer of dx so it is better suited to gsdx architecture. For speed reason it won't be used everywhere (bind once stuff). Last but not least, most of the dev prefers this kind of api so let's dream about more contributions.
Actually there is the osx issue now which is limited to a 4 years old api...
Reply




Users browsing this thread: 2 Guest(s)