Wiipressuresense said:
CarbonX13 said:
I'm pretty sure the MotionPlus is partially, if not fully, based in the game's engine itself to incorporate support for it. Meaning that the game's engine was made so that it can be run on MotionPlus, and which is why games that do not support MotionPlus cannot have the support added. It'll likely take a modification of the actual game engine, instead of simply implementing a conversion of some sorts or adding a new control mapping thing.
Yeah but the Devs would have been messing with motion plus for a very long time now, so at least some basic code should be in most games around 2008 I would of thought?
But yeah I wanna access the game engine and change it, anybody hacked released any tools or do I need a Dev kit
Most devs wouldnt really bother messing with it (especially with the point of putting it in the game) if they see no advantage or feasibility of having support in the game engine for it.
I am a computer science major, so I know programming. From a programming perspective, it would be bad to have excess code for something that is not implemented at all. For example, if SMG2 had base code for WM+ support but didnt use it, that could be 30 megabyes of data that could have been trimmed from the game since it isnt used, not to mention hundreds of dollars wasted to implement something that isnt useable at ALL.
As for rewriting the game engine to support it... unless you have the knowledge of a whole dev team about the inner workings of the wii, hardware mapping, control schemes and programming with a non-official devkit, plus the ability to either reverse engineer the existing engine or write your own, which based off of your first 4 posts I can assume you do not, this is not something that can be done (at least not by any usual means). If anything, you would be better off writing your own knockoff game from scratch.
EDIT - to elaborate on the topic of having useless, excess code:
Scenario - Windows X, the next generation Windows OS, is released in 2012. Upon release, people examine all of the installed files. a file ps3dsk.sys is found, totaling to 42 Mb. This file has the base support for reading PS3 disks. However, since Microsoft does NOT have the licenses to market Windows X as a PS3 emulator, nor is it a game system at all (as it simply provides a backbone for games to be played on), the file ps3dsk.sys is a useless file with no function whatsoever. 3 months were spent on the development of this single file by a team of 5 people. So say MS wasted 12 grand on development of a 42 Mb file that does NOTHING except waste space and ultimately make the system slower. THAT is poor programming.
(Of course, that is a hypothetical situation)