Main > Main Forum
720 Real/Joystick/Spinner Test
<< < (20/30) > >>
Derrick Renaud:
Futile.

 :banghead:

(edit) For the 100th time. SUBMIT THE CODE!

(edit 2) The above was not meant against cotmm68030's post.

I Just don't understand what is so hard to understand that if arabara has some magical shifter code, sprite fix code, etc, then submit it, submit it, submit it.  Maybe saying it 3 times in a row will make it happen.  Strange as it seems, that is how stuff gets added to MAME.  Not by stating the world is against me and stopping me from submitting it.
Derrick Renaud:

--- Quote from: Xiaou2 on January 27, 2011, 10:09:25 pm ---Heh, I find it interesting that Haze is against multiple control input methods due to code maintainability.. yet Derrick is all about putting in tons of hacks to be 'maintained'.
--- End quote ---

Yes, that is why I posted the 3 control hack patches on the software forum and did not submit them.  You realize that we do allow digital control of analog devices for ease of use.  That is a hack.  Map lightguns to joystick guns.  Mice to analog sticks and guns.  More hacks.  Or maybe we care about ease of use.  Which is why I asked if other games used a Return of the Jedi type centering thrust type analog axis.  Currently MAME maps the mouse as a non centering analog joystick.  I was wondering if there were enough cases to warrant the ability to map the mouse as a return to center device so it behaved closer to the real control, as in the patch I mentioned on the software forum.

(edit) Instead of discussing what the Sinister Derrick is all about, can we stick to the topic of what games used that type of control? (edit)

So the options are remove the ability to use the mouse as a joystick, or improve the remapping so it has the ability to behave more like the real control.

While I can't speak for him, I don't believe Haze is completely against more type of controls,  as long as they are well thought out core implementations and serve a purpose.  He just states as I have,  "No one is interested in coding it"


--- Quote from: Xiaou2 on January 27, 2011, 10:09:25 pm --- Personally, I dont care if there are hacks, as long as they are not the default.. or are confusing others as to what the game really used.  There are always times when a person might not have a proper controller... and its nice to have the ability to substitute.more efforts to the mame preservation goals.
--- End quote ---

The world is ending, I did something that X2 agrees with me about.   ;D  Notice you can select "Real" in 720 which means the others are fake and are there for ease of use.  Well spinner is also there to accurately simulate synced rotate/center data.
Derrick Renaud:

--- Quote from: Derrick Renaud on January 28, 2011, 12:51:50 am ---"No one is interested in coding it"
--- End quote ---

Let me clarify this.  I did not want to edit the post, because that makes people think something sinister is going on.

720 - Very minor thing added.  Difference in code was quite small.  Never ending flack because of it.

That really makes people interested in doing more.  Not to mention we have to wait a few years to make sure some other shifter submission is not lost in the mail.  Would not want to be the cause of more hate.
Haze:

--- Quote from: Xiaou2 on January 27, 2011, 10:09:25 pm --- Its funny, all the Hypocrisy that is behind the mame team.  Admittedly Driver-Man was way too brass knuckles. But he might still be able to be helpful regardless.  If Devs are against new people, then it goes against the call for Developers help...

--- End quote ---

I don't think anybody wants another 'Guru' to be added to the list.  As has been stated, all Driver-Man was doing was pulling up a tiny amount of code from old versions while demonstrating an attitude that belonged at a playgroup even without anybody provoking him and without actually having achieved anything to even attempt to warrant his treatment of people actually involved.

I've stated elsewhere that I'm not against such things being done in a way which doesn't break existing functionality / testability on normal hardware. (I'm not Aaron, I'd even consider extra commandline switches / configuration files myself)

I wouldn't agree to adding fake buttons to defender, fake joystick hacks to assault, or even the 'run like hell' garbage that used to be in track n field etc. because they're 100% usable on a keyboard / pad as it is, but some games are simply untestable without some degree of hacks.  Prebillian, for example, would be completely unusable without the 'power' display added to the OSD (I think)

Reasonable decisions must be made on a case by case basis.
marcusP:

--- Quote from: Derrick Renaud ---For the 100th time. SUBMIT THE CODE!

The latest idea to use the -joy & -mouse options to select between options in the driver code would be refused.

--- End quote ---

Whom did you consult, or is that just YOUR own OPINION?

Submitting code just to be refused is waste of time, no?


You are doing the same thing again. I'm not submitting anything untested. How abut we let people decide, or at least let's hear their opinion first. Vox populi, vox dei, do you agree?




--- Quote ---The submissions are sent to everyone on the team for discussion.

--- End quote ---

Where was your submission discussed, by whom? It was only me trying to discuss it here and on MAMEworld forum, and I got more support there among MAME devs than you, even though everyone hated me. -- Why would we not discus it BEFORE submission is made, would that not make more sense?




--- Quote ---Options should not be used in this way.  They are used to tell the MAME core how to operate, not game code.  Not one file in the src\mame directory accesses options using options_get_string()  The -joy & -mouse options tell MAME that these devices are hooked up to the computer.  Not how a game is to behave.

--- End quote ---

Ugghhh. MAPPING, it's all about mapping. I do not read command line parameters, but use the same information "inptport.c" uses to separate between digital, absolute and relative devices. I could just as well use the information from UI mapping menu, just like you get your string variable from your new menu. It's all the same to me. As I said, you only had to PICK one of my solutions, and now you finally did.


If this was some good movie you would have realized by now that crazy old drunk is not a fool, but great and wise Code-Fu master, in disguise. This so far was with my both hands in my pockets, let me now show you some real moves...

ShaaaZZzzzzaam!
http://www.mediafire.com/?skcth05nid0txbb  ...the school is Wudang,
technique... female form of 'eight trigram palm', KaabOOoooshhh! -:


* Fixed sprite flickering/disappearance (broken since .115)

* Jittery analog motion diagnosed/attended, can be fixed in several ways.

* SIMULTANEOUS support of all the devices! Play with analog hack and authentic spinner or mouse, and keyboard, in the same time.

* Easy for testing without any menu selection or need to change anything anywhere, other than to map your input devices in whichever way you want, as usual.

* Maximum flexibly, you can map any devices to both authentic or hack input.

* Does not use command line parameters or whatever external data to the driver - the only files need changing is "atarisy2.c" for control fixes, and the file requiring correction for flickering is "atarigen.c".


Code-Fu in slow-motion....


--- Code: ---static READ8_HANDLER( leta_r )
{
     static int    last_in, input, rotations, last_angle, angle;
     int aX=    input_port_read(space->machine,  "LETA0") - 127;
     int aY=  - (input_port_read(space->machine,"LETA1") - 127);
     int relative_in = input_port_read(space->machine, "LETA2");
        if(aX!=0 || aY!=0){
             if((angle= atan2(aX, aY) *22.9183)< 0) angle+= 144;
             if(last_angle > 120 && angle < 24) rotations+= 144;
             if(last_angle < 24 && angle > 120) rotations-= 144;
             input =           (last_angle = angle) + rotations;
        }else if(last_in!=relative_in)last_in=input=relative_in;
        return((offset&3)<1)?
                input_port_read(space->machine,"LETA3") : input;
}// +=1;

--- End code ---

Beautiful, isn't it? This little piece of code does all that I said above, and so can substitute hundreds of your lines with unnecessary bloat and fiddling with MAME core engine.


Derrick & Haze: - Master, please forgive, we have failed!

You fought well, but you fought me, so master understands.


1.) Do you want to know how to fix flickering animation?

2.) Do you want to know how to solve jittery analog motion?

3.) Do you want to use my new algorithm to handle analog hack?

Navigation
Message Index
Next page
Previous page

Go to full version