Minimum System Requirements?

This topic contains 7 replies, has 4 voices, and was last updated by therevills 2 years, 4 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)

Author

Posts

November 20, 2016 at 2:40 am #5268

therevills

Participant

What are the minimum system requirements for the all targets for Monkey2?

Windows
OS:
GPU:
DirectX:
OpenGL:
Sound:

Mac OS
OS:
GPU:
OpenGL:
Sound:

Android
OS:
(any hardware restrictions?)

iOS
OS:
(any hardware restrictions?)

Cheers,
Steve

November 23, 2016 at 11:19 pm #5397

therevills

Participant

Bump!

November 24, 2016 at 9:33 am #5408

Mark Sibly

Keymaster

What are the minimum system requirements for the all targets for Monkey2?

The only real ‘hard’ requirement is it needs GLES20 or equivalent, eg: direct3d9 on windows, gl2 on macos/linux, android2.2, no idea about ios, etc.

It should run on any OS you can build SDL for.:

https://wiki.libsdl.org/Installation

I wont be able to test/build for *all* potential platforms, so community help with this will be important.

November 24, 2016 at 12:29 pm #5413

Jesse

Participant

I have a 2001 Macbook with El Capitan that has problem running some applications running OpenGL GLES20. The intel driver is not fully compatible. It does not run the Bananas Sdl2 Test but all the other bananas demos work.

November 24, 2016 at 9:15 pm #5420

therevills

Participant

I’ve tested MX2 / Ted2 on the following PCs:

OS: Windows 7
CPU: Intel Core i5 650 / 64bit
RAM: 8GB
GPU: Intel HD Graphics
DX: 11

OS: Windows 8.1
CPU: Intel Core i7 920 / 64bit
RAM: 6GB
GPU: Nvidia Geforce 670GTX
DX: 11

Need to test it on some old PCs, I’ve got an oldish Celeron running XP SP2 (DX9) which I can test on.

~~Is there a way to detect if an app is using DX or OpenGL?~~ Looks like you can using renderInfo:

SDL_Renderer *renderer = SDL_CreateRenderer(sdlWindow, -1, 0);
SDL_RendererInfo rendererInfo;
SDL_GetRendererInfo(renderer, &rendererInfo);

std::cout << "Renderer: " << rendererInfo.name << std::endl;

SDL_Renderer *renderer = SDL_CreateRenderer(sdlWindow, -1, 0);

SDL_RendererInfo rendererInfo;

SDL_GetRendererInfo(renderer, &rendererInfo);

std::cout << "Renderer: " << rendererInfo.name << std::endl;

http://gamedev.stackexchange.com/questions/81917/how-to-detect-graphics-api-at-runtime-with-sdl2

Could that be added to MX2 for easy access?

November 25, 2016 at 8:59 am #5427

therevills

Participant

Just tested on the old Celeron, Ted2 and MonkeyRoids fails to start with the same error:

The procedure entry point CancelIoEx could not be located in the dynamic link library KERNEL32.dll

OS: Windows XP SP2 32bit
CPU: Intel Celeron E1200
RAM: 2GB
GPU: Intel GMA3100
DX: 9c

So at the moment MX2 for Windows has a minimum OS of Vista.

GameHouse (a large casual game portal) has these requirements for games:

<b>Unsupported Engines</b>

The following technologies are currently incompatible with the advertising technology used by GameHouse:

OpenGL

Minimum / Recommended Systems Specs

Our system specs are based on visitor information at GameHouse.com. We encourage developers to keep these specs in mind while developing their games, as it ensures that the widest audience can play (and buy) your game. Significantly higher system requirements lead to a definite decrease in sales volume.

<b>Minimum Specifications</b>

Pentium III, 800 MHz processor
Windows 8 / 7 / Vista / XP
256 MB system RAM
32 MB video RAM
DirectX 7+
Internet Explorer 7.0+ and Mozilla Firefox
Supports windowed and full screen modes

<b>Recommended Specifications</b>

Pentium III, 1 GHz processor
Windows 8 / 7 / Vista / XP
512 MB system RAM
32 MB video RAM
DirectX 7+ or better
Internet Explorer 7.0+, Mozilla Firefox 3.0, and Google Chrome
SoundBlaster compatible sound card

Quality Assurance Overview

GameHouse handles quality assurance through its internal resources. Your GHP Producer / Portfolio Manager will collaborate with you on managing the pipeline and bug resolution process. For 3rd party games (i.e. – not published through GameHouse) our QA pass is limited to a final build verification / hardware compatibility pass. Published games get in-depth QA resources through their development cycle.

For more information, see the Tips section, below.

Tips: QA Best Practices
While your Producer / Portfolio Manager will work with you during the QA process, it’s imperative for your bottom line that you deliver as bug-free a product as possible. To assist you, here are the 10 most common bugs that cause QA failures for PC games, in no particular order.

Game does not recover properly from sleep/hibernate mode.
Game does not recover properly from Control/Alt/Delete (locking computer, checking task manager).
Game does not handle Alt Tab (switch to another application).
Game does not handle Alt F4 (manually force application to quit).
Game does not properly restore using windows key.
Game does not launch under Windows with UAC turned off (User Account Controls settings).
Game sounds continue to play when game is minimized to task bar.
Game does not launch to full screen on initial launch.
Game options do not save on subsequent launches.
When playing game in window mode, game will cause user native desktop resolution to change.

Final Build Verification & Compatibility Test Cases
All games undergo a test pass prior to release. Here are the cases that we test against; for smoother deployment, please ensure that your game complies with these prior to submission:

Verify the proper splash screen sequence: GameHouse logo, developer logo
Verify that when game is minimized or focus is lost all game audio ceases; game audio should resume when focus is returned
Verify with any User, UAC On: Alt-Tab does not cause the game to crash or hang.
Verify with any User, UAC On: Control Alt Delete does not cause the game to crash or hang.
Verify with any User, UAC On: Volume settings are not altered by launching the game or adjusting in-game sound levels.
Verify the game can be shut down through task manager. Use Control/Alt/Delete to bring up task manager and select the shut down option.
Verify that the game does not fight other applications for focus while playing in fullscreen and/or window mode
Verify that all clickable options in-game have mouseover highlights and sound effects
If level-saving feature is present, ensure that user’s progress is saved after exiting and relaunching
Verify that all controls work as expected, including keyboard, mouse, and all supported peripherals
Verify that the game pauses and music stops when interrupted by Ctrl/Alt/Del, Alt/Tab
Verify game has loading screen or progress bar
Verify the user can recover game from Windows L command
Verify the user can switch between game and application using Alt/Tab
Verify the user can recover game from Sleep & Hibernate
Verify that user can recover game from Control/Atl/Delete
Verify functionality of game options
Verify game does not have pre-existing player profiles
Verify the game runs on Windows 8
Verify the game run on Windows XP SP3
Verify there are NO external game links or e-commerce links
Verify on first launch the game launches into full screen mode