(Co-op 14 players AUSTRALIA) What the Data files actually include: VitaQuakeII offers 5 different pre-selected servers in the serverlist from different places (Australia, Russia, France, USA): 4 are deatmatch servers, one is a co-op server. I personally tested everything with a set of textures/high res models. Textures pack will obviously increase loading time and degrade a bit performances however game should stay playable with a fair decent amount of modified textures. If you want to play mission packs, place rogue and xatrix folders in ux0:/data/quake2. All my patroners for their awesome support: gnmmarechal and bhunterzor for testing the homebrew. MasterFeizz for Quake2Ctr source i used as base for the port. Ch3lin for the awesome livearea assets. Select = Show Mission (Singleplayer) / Scores (Multiplayer) Credits: Variable camera sensibility for right analog in option menu - Multiplayer with support for both locale and online games with featured online servers Controls: Unique features like dualshock rumbling, fps counter. Support for official mission packs - Support for high res textures pack - Native support to both PSVITA analogs Support for shareware and full versions of Quake Native 960x544 resolution! - Hardware acceleration thanks to vitaGL - MSAA 2x and MSAA 4x antialiasing support - Sound and Soundtrack support The port is fully hardware accelerated and supports high res textures pack and official mission packs. It supports also double analogs for comfortable gameplay, online and locale multiplayer with featured servers, soundtracks support, sounds support and a lot more stuffs. This should create an entry in a user space which you can then interrogate to get the full job name back.VitaQuakeII is a port of Quake II for PSVITA.Īt the moment vitaQuakeII has unique features like dualshock rumbling when player get hit. I would try using the QUSLJOB (List Jobs) API, specifying a job name of QPRTJOB/user_id/*ALL and a status of *ACTIVE. The QPRTJOB remains active and is re-used until either 9999 spool files are created for the job, or all spool files for the job have been deleted and there have been no more spool files written for 24 hours. Each QPRTJOB can hold up to 9999 spool files, after which a new QPRTJOB job is created for the user. When you then logon to the job as, for example, user JDOE the system recognises that the current user profile has changed and directs all spooled output to job QPRTJOB/JDOE/nnnnnn. For example, in your GUI application, the HTTP server job starts running under user QTMHHTTP. QPRTJOB is a job that is automatically created by the system when your job tries to create a spool file and the job's current user ID is different to the user ID that the job is running under.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |