Pitch meter variables in datafile

[pfalvey]

I am editing the pitching meter for the MVP07 datafile to make it easier to pitch than the mod, but more difficult than the default MVP 05 datafile. I know how to edit the datafile, but I am unsure as to what some of the variables mean and do, even after using MD Datafile Line Spreadsheet. If anyone can shed further light on these variables, I'd appreciate it:

*34 accuracywidth (0.120)

*40 linespeed (0.750)

*50 badaccuracywidth (0.00)

51 ImperfectMovPrimary (1.00)

52 ImperfectMovSecondary (0.750)

53 MistakeMovPrimary (2.00)

54 MistakeMovSecondary (1.00)

*141 perfectaccuracygreen (255)

*143 Perfectaccuracyalpha (255)

*144 perfectaccuracysize (0.25)

*152 accuracygreen (255)

[spitoon]

I had the most luck with accuracywidth, changing it provides obvious results in the game (changing the size of the target green area on the meter).

The rest of the variables are really hard to pin down. Believe me, I've messed with them hundreds of different ways.

Those 3 with (255) as values, have to do with colors (I think) and don't effect anything in the game.

[jcd91]

pfalvey

can you briefly explain what you need to do to edit the variables? I'm a relative newbie to this and while i love the new 2007 mod (as do my 2 boys), i've got to make the pitching a little bit easier.

thanks

[pfalvey]

I had the most luck with accuracywidth, changing it provides obvious results in the game (changing the size of the target green area on the meter).

The rest of the variables are really hard to pin down. Believe me, I've messed with them hundreds of different ways.

Those 3 with (255) as values, have to do with colors (I think) and don't effect anything in the game.

Thanks for the reply and that helps regarding accuracywidth. Like I said I'm trying to get a pitch meter harder than the default, but easier than the MVP07 mod. What I've done so far is to take the difference in values of those variables and make the pitch meter 2/3 more difficult. For example:

accuraywidth for default is .120

accuracywidth for MVP07 is .60

2/3 x (.120-.60) = .40

I then subtracted .40 from the default .120 which gave me a variable of .80 for accuracywidth. I used the 2/3 with all the variables and it really hasn't netted the results I had thought it would. It seems to be much easier to pitch than the MVP07 mod, even though my changes are closer to the MVP07 values than the default. Maybe I'll just play with the accuracywidth and change the other variables back to their MVP07 values.

[pfalvey]

pfalvey

can you briefly explain what you need to do to edit the variables? I'm a relative newbie to this and while i love the new 2007 mod (as do my 2 boys), i've got to make the pitching a little bit easier.

thanks

I'll try. First you need to download the following utilities from this site:

1. BigGUI 1.0

2. Datafil comp utility 20. (dfcomputilv20)

3. MaddieDaddies datafile line spreadsheet

The first 2 should be in the tools & editors directory of MVP 2005 and the 3rd probably miscellaneuous (search the downloads). Read the readme's of these utilities and make sure you have all relevant subprograms installed (eazip, etc..)

Here's the process:

1. Run BiGUI and open the datafile.big file found in your MVP/data/datafile directory. I recommend making a backup first.

1A. Highlight the datafile.txt and export the file to a new folder(under the edit tab of BigGUI.).

2. Run dfcomputilv20 and choose the decompress datafile.txt into datafileEdit.txt.

3. Using dfcomputil, Open the datafileEdit.txt file and select the find function and enter: 0x739c0a96 Which is the datafile line where the variables can be found.

4. Find the accuracywidth variable. The first number after each semi-colon is the variable ID. You want ID #34. You'll want to keep the value between .60(Hard/MVP07) and .120(Easy/default). I am unsure what other variables do so I won't go any further. According to Spitoon, accuracywidth will affect the size of the green target on the meter, which represents optimum accuracy of the pitch.

5. Save the file in wordpad/notepad.

6. Using dfcomputil, compress datafileEdit.txt back into datafile.txt.

7. Copy that datafile.txt file and place it into your MVP/data folder. The datafile.BIG file can be kept in the data/datafile folder. The datafile.TXT will override the datafile.txt that is contained within the .BIG file.

This is the brief version, I'm glad you didn't ask for the long version. If you have any problems or questions, just PM me.

[jcd91]

Thanks for the great instructions. I'm giving it a try.

[jcd91]

It seemed to work for me. Thanks a ton!

[spitoon]

Also, 144 perfectaccuracysize seems to effect the size of the 'perfect zone' within the green zone. The range is 0 to 1, where 0 would be no perfect zone, and 1 would mean the entire green area is 'perfect'.

One of the most frustrating things about this game is still the lack of user pitcher walks. When I first discovered the 'accuracywidth' variable, I walked a bunch of guys right away, but now that I have adjusted to it, I rarely walk anybody anymore.

The problem is that you can walk someone if you miss the zone by a fairly big margin, but as you get closer to it (with practice), missing by a little just results in more 'fat' pitches and you end up getting hit harder rather than missing the zone all together.

[pfalvey]

Also, 144 perfectaccuracysize seems to effect the size of the 'perfect zone' within the green zone. The range is 0 to 1, where 0 would be no perfect zone, and 1 would mean the entire green area is 'perfect'.

One of the most frustrating things about this game is still the lack of user pitcher walks. When I first discovered the 'accuracywidth' variable, I walked a bunch of guys right away, but now that I have adjusted to it, I rarely walk anybody anymore.

The problem is that you can walk someone if you miss the zone by a fairly big margin, but as you get closer to it (with practice), missing by a little just results in more 'fat' pitches and you end up getting hit harder rather than missing the zone all together.

Thanks for the info on perfectaccuracysize, I always thought hitting any green on the meter was considered perfect and there were no degrees of perfections.

Your right about the lack of user walks. I've started to pitch so that I always nibble at the outskirts of the strike zone (unless the count is like, 3-0) and I think I've only walked about 3-4 CPU batters in 12 games. I've now gone back to the MVP07 pitch meter and the lack of walks are still there. What can you do, though, I won't intentionally keep pitching out of the strike zone just to get accurate user pitcher walks.

[spitoon]

Thanks for the info on perfectaccuracysize, I always thought hitting any green on the meter was considered perfect and there were no degrees of perfections.

I always thought that too, but try changing that number and you'll see way more "PERFECT" pitches, and less "EARLY" and "LATE" markers. I've changed so many numbers in there that it becomes difficult to keep track of them and what they do. Many of the numbers don't seem to have any effect in the game. I think the problem is that there are a number of factors involved, including some that are hard coded in the .exe and can't be changed.

Your right about the lack of user walks. I've started to pitch so that I always nibble at the outskirts of the strike zone (unless the count is like, 3-0) and I think I've only walked about 3-4 CPU batters in 12 games. I've now gone back to the MVP07 pitch meter and the lack of walks are still there. What can you do, though, I won't intentionally keep pitching out of the strike zone just to get accurate user pitcher walks.

If I had to pick one thing about this game that bothered me most it would be that. From what I can tell the game's designers take the attitude that people don't want to walk guys. It's true, I don't want to walk guys, but it's a part of the game and it has to happen at a realistic level for me to get full enjoyment out of the game. The only game that approached this for me was High Heat, and sadly it's gone.

It's a very complicated problem. The other side of it is that to have realistic strike out numbers (in this game) you need to have pinpoint control, but if you have pinpoint control, you won't get any walks.

The best I have been able to do was to turn off all of the pitching aides. No strike zone, no hot/cold zones, no vibration, no cursor. That way I'm pitching 'by feel' and it's way harder to hit the corners. I still walk the occasional guy, especially if I consider him a dangerous hitter, but the numbers are still significantly low.

[Kamasutra]

The best I have been able to do was to turn off all of the pitching aides. No strike zone, no hot/cold zones, no vibration, no cursor. That way I'm pitching 'by feel' and it's way harder to hit the corners.

Yep, this is still the best way to get close to realistic numbers, along with slight datafile tweaking.

Here are the values I tinkered with and narrowed it down. They do the trick for me (more walks, less strike outs etc) for human pitching:

def = default

mod = moded

34 accuracywidth def => 0.120 moded => 0.105

40 LineSpeed def => 0.750 moded =>1.305

43 ControlAffect def=> 0.600 moded => 0.340 (might want to leave this one on default if it's too difficult to pitch for you)

144 perfectaccuracysize def => 0.25 moded => 0.21

in conjuction, the bat time window (under the "233<batterpitcher>" section) can also be moded to counter balance the effects of your pitching tweaks... Higher = more time to react for you and the AI...lower = less time

197 BatTimeWindow def => 0.30 moded => 0.33

[69Yanks]

Hi Kamasutra:

I have your 2004 program to change the datafiles and really enjoyed them. I was wondering if you could send the 2005 to uploads for us to use or them via email. Thanks.

[Kamasutra]

Hi Kamasutra:

I have your 2004 program to change the datafiles and really enjoyed them. I was wondering if you could send the 2005 to uploads for us to use or them via email. Thanks.

Hi 69 yanks,

I did a similar program last year for 05 (one that changes cameras & custom tweaks). I managed to upload them here but they were never posted. I suspect it was when they changed file system as all the links on my old site were dead. I couldn't host it on my site since the program was a total of 22mb.

Anyway, I since bought a new pc and unfortunatly lost all the little tweaks & mods but I did save all my notes and a couple of the last datafiles I was using that were still a work in progress. If you don't mind receiving a simple datafile by email, I can email it to you. Bare in mind that this is one of the last datafiles I re-tweaked so I have no idea if it is up to your standards. I've sent it to quit a few people and had no complaints.

PM me where you would like to recieve it if interested.

Later

[pfalvey]

Hi 69 yanks,

I did a similar program last year for 05 (one that changes cameras & custom tweaks). I managed to upload them here but they were never posted. I suspect it was when they changed file system as all the links on my old site were dead. I couldn't host it on my site since the program was a total of 22mb.

Anyway, I since bought a new pc and unfortunatly lost all the little tweaks & mods but I did save all my notes and a couple of the last datafiles I was using that were still a work in progress. If you don't mind receiving a simple datafile by email, I can email it to you. Bare in mind that this is one of the last datafiles I re-tweaked so I have no idea if it is up to your standards. I've sent it to quit a few people and had no complaints.

PM me where you would like to recieve it if interested.

Later

Are you saying you had a program that changed values of the datafile? Like if I wanted to change accuracywidth, I would just load up your program and it would do it automatically, avoiding searching for number lines and such. I know how to do it manually, so to speak, but a program with all the relevant factors, so labeled and you could just change the values would be great. Maybe I'm misunderstanding, but it seems to me that would be a pretty valuable utility around here. Of course, you also mentioned the utility for 05 has been lost, so I guess it doesn't much matter.

[Kamasutra]

Hi Pfalvey, no it's a utility I had since 04 that simply loads different datafiles according to custom tweaks. ie: datafile with pitching mod + cameras 1, datafile with batting mod + cameras 2... .etc

It doesn't customize the tweaks themselves.

As always, I think you're better off editing the fields I mentioned yourself, nothing beats fine-tuning.

[fjccommish]

I tried changing datafile.txt to make the green bar larger. The new datafile.txt is in the datafile folder, but the bar is still tiny to not there at all.

I followed this:

I'll try. First you need to download the following utilities from this site:

1. BigGUI 1.0

2. Datafil comp utility 20. (dfcomputilv20)

3. MaddieDaddies datafile line spreadsheet

The first 2 should be in the tools & editors directory of MVP 2005 and the 3rd probably miscellaneuous (search the downloads). Read the readme's of these utilities and make sure you have all relevant subprograms installed (eazip, etc..)

Here's the process:

1. Run BiGUI and open the datafile.big file found in your MVP/data/datafile directory. I recommend making a backup first.

1A. Highlight the datafile.txt and export the file to a new folder(under the edit tab of BigGUI.).

2. Run dfcomputilv20 and choose the decompress datafile.txt into datafileEdit.txt.

3. Using dfcomputil, Open the datafileEdit.txt file and select the find function and enter: 0x739c0a96 Which is the datafile line where the variables can be found.

4. Find the accuracywidth variable. The first number after each semi-colon is the variable ID. You want ID #34. You'll want to keep the value between .60(Hard/MVP07) and .120(Easy/default). I am unsure what other variables do so I won't go any further. According to Spitoon, accuracywidth will affect the size of the green target on the meter, which represents optimum accuracy of the pitch.

5. Save the file in wordpad/notepad.

6. Using dfcomputil, compress datafileEdit.txt back into datafile.txt.

7. Copy that datafile.txt file and place it into your MVP/data folder. The datafile.BIG file can be kept in the data/datafile folder. The datafile.TXT will override the datafile.txt that is contained within the .BIG file.

This is the brief version, I'm glad you didn't ask for the long version. If you have any problems or questions, just PM me.

[59FIFTY]

if i change the datafile the cameras are default again is this normal cause i'm used to the 2007 cams;)

[Jim825]

The new datafile.txt is in the datafile folder, but the bar is still tiny to not there at all.

That's your problem. The datafile.txt file needs to be in the data folder, not the datadatafile folder. If you put it in the datadatafile folder, the game will use the datafile.txt file that is embedded in the datafile.big file (i.e. it will ignore your file). If, however, you put your datafile.txt file in the data folder, the game uses that one.

Try moving your datafile.txt file to the data folder and I'll bet that your meter changes will appear in the game.

[conception]

I am glad that somebody is working on this, because I still haven't gone through the trouble of retuning MVP 2007 in order to make it possible to pitch with the new datafile. If you do find a good level, please post this so that others who have encountered the same problem can correct it without going through the trial and error process you are going through.