Realism- and gameplay-related hardcode fixes for SH3.EXE - Page 225

h.sie · 05-07-12, 02:29 PM

@Leitender: I changed my plans, so I won't use MinRange because of several reasons. The plan currently is shown in the marinesims.de forum: The radar wavelength will be written/coded into the insignificant digits of the maxRange.

e.g. MaxRange:
12000m = unchanged = sends/detects all frequencies as before
12000.01m = sends/detects only cm wavelength
12000.02m = sends/detects only m wavelength

But: It's in very, very early stage - no guarantee that it will work.

By the way: No reason to explain yourself. I asked for input. You were one of the few who gave input.

h.sie · 05-09-12, 11:39 AM

Regarding the introduction of two different wavelengths for radar & radar warn receivers (RWR), I can now give an overview what is possible and what not:

1) it is possible to introduce two different wavelengths using the insignificant digits of the MaxRange parameter in AI_Sensors.dat resp. Sensors.dat:

Example:

MaxRange=12000 : Sends/detects both cm- and m- radar wavelengths as before.
MaxRange=12000.01 : Sends/detects only cm-wavelengths.
MaxRange=12000.02 : Sends/detects only m-radar wavelengths.

2) BUT: The best (and nearby) solution is NOT possible: It is not possible for the RWR code, that continuously scans for enemy radar systems in render range, to find out the MaxRange (and thus wavelength) of every single radar system and react accordingly to the wavelength (i.e. detect it or not). I gave up here.

3) BUT: I am slightly optimistic to offer a workaround solution, that will work well in most situations: It is possible to determine 2 very important values by coding:

a) the current distance between the Uboat and the closest cm-radar system and
b) the current distance between the Uboat and the closest m-radar system.

these two variables give answers to two important questions:

a) is at least one cm-radar system in the maxRange of the RWR?
b) is at least one m-radar system in the maxRange of the RWR?

With these two answers, the workaround would work as follows:

Lets assume the RWR detects only cm-waves and there is no cm-wave radar system in the MaxRange of the RWR. Then, the detection probability will be forced to 0, the RWR will be made blind, even if there is a m-radar in very close range. It won't be detected.

If there is a cm-radar system in range, the RWR will be act unchanged and detect it soon.

The only problem arises in situations where BOTH, cm- and m- radar systems, are in MaxRange of the RWR, because then the RWR is active and will "see" both systems (since in reality it cannot distinct between the wavelengths).

IMO this is absolutely not critical, because it will cause a detection and a line on the NavMap, pointing into the direction of the detected radar (which could be the wrong direction to the m-radar, of course).

One of the main problems (that the Metox detects cm-radar) could be solved to 99%. Thus, surprising aircraft attacks are possible without being warned by RWR.

Feedback welcome.

Rubini · 05-09-12, 01:24 PM

Hi h.sie,

How are you mate?
Sorry to be totally OT from your current work (radar lenght). I have not any knowledge to help you on this matter.

But I should like to suggest a new item on your to do list about hydrophones.
I guess that you know that some months ago I tried/made a small mod that adds three layers for hydrophone to add more playability and realism for the hydrophones . Also i guess that you have noted that only the more deep layer allows the player to listen by himself on the hidro station. A limitation from Sh3 that makes that mod just useful for half of the users.

Perhaps with hardfix could be not difficult to cut the max hydrophone range (on sensors.dat) accordingly the depth of the uboat. Let's say: PD to -18m: 12000m, -17 to -28m: 18000m and <-28m: the maxrange as it is on sensors.dat.

Thanks again by your great work. The radar fix will be another great addition!

Leitender · 05-10-12, 01:42 AM

h.sie,

nice to see that you´re continuing your studies. If i compare your basic approach with your randomized_events solution, i see a benefit in differentiation of the wavelength which radar transmitters are to be discovered by RWR.

In this case you have to determine if the sensor sends / reacts on cm, m or both m and cm waves. In reality, both bandwiths were only possible with combined systems for U-Boats as well as for AI ships. For U-Boats, a combination is possible and a second radar system is included in the big mods to have combined radio-systems.

Until now, no combination of m and cm RWR is simulated, these banddiths are put together in one RWR sensor. You have to rework the special U-Boat files and eventually the basic.cfg

To equip the AI ships you have to alternate the .sns-files and thus you have to decide, which system the special vessel will have. (i made the same thoughts, when fiddling around with combined asdic sensors. The SH3 devs simplified these real life combined systems in combining their characteristics in a unique sensor).

In fact, there were three important bandwiths working during WW2: VHF-Band (1m-10m), S-Band (10cm-15cm) and X-Band (2cm-4cm). Maybe there should be introduced a third digit? And maybe more combined sensor systems?

So my question is: Aren´t you satisfied with your own SH3 Commander solution? Or doesn´t it work (personally, i hadn´t yet the time to test)? I ask, because i found this solution very simple not only to simulate the Metox blackout, but also simple to attach it to the player´s system.

Greetings

h.sie · 05-10-12, 03:38 PM

@Rubini: Hi mate, maybe later. one project at a time.

@Leitender: I don't understand.

1) Why do i have to rework the special U-Boat files and eventually the basic.cfg if I change the behavior of an RWR??? To change the RWR detection wavelength, only one change in Sensors.dat (MaxRange) for every RWR type is necessary with the hardcode fix. The Uboat will use the same RWR types as before.

2) Why do I have to alternate the .sns-files and decide, which system the special vessel will have? The vessels are already equipped with (the correct) radar. To change the radar wavelength, only one change in AI_Sensors.dat (MaxRange) for every radar type is necessary with the hardcode fix. The vessels and aircraft will use the same radar types as before.

3) Regarding 3 different wavelengths: The effort to model different wavelengths exponentially rises with the number of different wavelengths and thus only makes sense, if it had historical relevance (as it happened with Metox that couldn't detect cm-radar). Do you have any reliable historical information, that a similar problem existed for S-Band and X-Band? (i.e. RWR detected S- but not X-Band and vise-versa)? Did that cause similar problems as with Metox?

To answer your question: I havn't played so far, so I cannot say whether I'm satisfied with the Sh3-Cmdr solution. IMO it's too crude to simply apply a failure probability of a certain percentage for the year 1943, independent of what radar a unit really is equipped with.

But I must admit that I think about to go back to the simple Sh3-Cmdr solution. Hmmmm?

Wolfstriked · 05-10-12, 04:22 PM

Quote:

Originally Posted by h.sie

But I must admit that I think about to go back to the simple Sh3-Cmdr solution. Hmmmm?

Not everyone uses SH3commander though and I think the one patch for many changes concept is great for ease of adding mods.

Do you have any plans to try for a more realistic compressed air?One area that I think is rather easy to change is the time it takes for the low pressure blower to complete the blowing of main ballast tanks.In game its about 30seconds when in real life it takes 10 to 15 minutes.Will cause sub to not be able to reach top speed for the time its blowing out the ballasts.

The only problem is then the player can just "blow ballast" and voila problem fixed.But this can be player choice then....

No problem if you think its more a cosmetic change and not worth the time to implement.

rowi58 · 05-12-12, 07:10 AM

Hi h.sie,

I***8217;m using the following solution within SH3_Cmdr's ***8220;Randomised events.cfg***8221;. Not as ***8220;Malfunction***8221;. Not as ***8220;Sabotage***8221;. Just a ***8220;normal***8221; event with 100% probability. It changes the ***8220;MaxHigh***8221; of the three RWR-sensors ***8220;Metox***8221;, ***8220;Borkum***8221; and ***8220;Naxos***8221; and reduces the precise and max. range of those.

;---------------------------------------------------------------------------------RadarWar--by-rowi58
[0:data\Library\Sensors.dat]
;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte
ApplyToPeriod=19420801|19430201
ChooseFrom=1
RndMidPat=1

0_x2729E=15000;.......... ***8220;Naxos***8221; - MaxHigh
0_x4BA99=7000;........... ***8220;Borkum***8221; - precise Range
0_x4BAAA=7000;........... ***8220;Borlum***8221; - max. range
0_x4BACE=15000;.......... ***8220;Borkum***8221; - MaxHigh
0_x4EE30=7000;............ ***8220;Metox***8221; - precise range
0_x4EE41=7000;............ ***8220;Metox***8221; - max. range
0_x4EE65=15000;.......... ***8220;Metox***8221; - MaxHidh

;-----------------------1943
[1:data\Library\Sensors.dat]
;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte
ApplyToPeriod=19430202|19430601
ChooseFrom=1
RndMidPat=1

0_x2729E=15000
0_x4BA99=7000
0_x4BAAA=7000
0_x4BACE=15000
0_x4EE30=5000
0_x4EE41=5000
0_x4EE65=200

;-----------------------1943
[2:data\Library\Sensors.dat]
;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte
ApplyToPeriod=19430602|19431231
ChooseFrom=1
RndMidPat=1

0_x2729E=15000
0_x4BA99=7000
0_x4BAAA=7000
0_x4BACE=15000
0_x4EE30=5000
0_x4EE41=5000
0_x4EE65=60

;-----------------------1944
[3:data\Library\Sensors.dat]
;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte
ApplyToPeriod=19440101|19440531
ChooseFrom=1
RndMidPat=1

0_x2729E=15000
0_x4BA99=5000
0_x4BAAA=5000
0_x4BACE=60
0_x4EE30=5000
0_x4EE41=5000
0_x4EE65=60

;-----------------------1944_45
[4:data\Library\Sensors.dat]
;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte
ApplyToPeriod=19440601|19451231
ChooseFrom=1
RndMidPat=1

0_x2729E=60
0_x4BA99=5000
0_x4BAAA=5000
0_x4BACE=60
0_x4EE30=5000
0_x4EE41=5000
0_x4EE65=60

Reducing the property ***8220;MaxHigh***8221; to 60 m (from 15.000 m) means that the RWR could not detect an aircraft with Radar ***8211; but it could detect ships with Radar. I think, no scripted aircraft or those who are generated by SH3 (AirStrike.cfg) will fly at an altitude of less then 60 m.

The start date and end date of each period refers to the appearance of RWR- and Radar-types, orienting at the ***8220;Basic.cfg***8221; and the SNS files of the most important sub chasing aircrafts such as Liberator, Wellington, Sunderland and Catalina. These dates can be different in every ***8220;super Mod***8221;.

ATM, it works fine. The only problem is, that I can not say whether the reduction of ***8220;MaxHigh***8221; to 200 m will work because i don't know at which altitude non-scripted aircraft will approach.

Note: the absolute hex-dresses will not work with Stock-SH3 or any other Mod including CCoM 8.1. The example above can not be used as a ***8220;fix***8221; or ***8220;add-on***8221; for the ***8220;Randomised events.cfg***8221;.

Greetings
rowi58

dariocapcro · 05-13-12, 04:56 PM

Hello everyone, especially h.sie, I have a problem, I take off your v16b1 patch kit and read the instructions several times but it always throws me a message, sorry, no compatible version of sh3.exe found, can anyone help me or say in what order could be a problem, greetings from Croatian

h.sie · 05-14-12, 10:10 AM

@rowi: thanks very much. the sh3-commander solution saves me a lot of time, trouble and controverse discussions.

@dariocaprio: it seems you don't have the original & unpatched sh3.exe

dariocapcro · 05-14-12, 10:32 AM

Regards, and I do not, means that it is impossible to use your version, I'm sorry but thanks, greetings to everyone

h.sie · 05-14-12, 11:57 AM

sh3 is available for some bucks - it's worth the money (in combination with a supermod)

rowi58 · 05-14-12, 12:13 PM

Quote:

Originally Posted by h.sie

@rowi: thanks very much. the sh3-commander solution saves me a lot of time, trouble and controverse discussions.
...

Hope it helps.

In some cases, SH3_Cmdr is a very good alternative. For this problem, i think, it is a simple and reliable solution.

Greetings
rowi58

rowi58 · 05-14-12, 12:24 PM

Quote:

Originally Posted by dariocapcro

Hello everyone, especially h.sie, I have a problem, I take off your v16b1 patch kit and read the instructions several times but it always throws me a message, sorry, no compatible version of sh3.exe found, can anyone help me or say in what order could be a problem, greetings from Croatian

Hi dariocapcro,

as h.sie wrote, you must have an unpatched SH3.EXE (and Co.). If you patched the sh3.exe with the "4-GB-Patch" before, h.sie's patch will not work. So re-install the backup of the sh3.exe and try it again.

Otherwise, buy a new SH3-Pogramm for 4,99 ***8364; from "Green Pepper" (available at mostly all Super Stores or at "amazon").

Greetings
rowi58

dariocapcro · 05-14-12, 01:15 PM

Thanks everyone, h.sie, you're right

kaizerkat · 05-15-12, 10:53 AM

just getting back to sh3 and read this thread about this add-on to fix alot of things in sh3. Is there a thread on how to create a working directory so that i can try out these new fixes?

05-07-12, 02:29 PM	#3361
h.sie Admiral Join Date: Jul 2008 Posts: 2,192 Downloads: 131 Uploads: 0	@Leitender: I changed my plans, so I won't use MinRange because of several reasons. The plan currently is shown in the marinesims.de forum: The radar wavelength will be written/coded into the insignificant digits of the maxRange. e.g. MaxRange: 12000m = unchanged = sends/detects all frequencies as before 12000.01m = sends/detects only cm wavelength 12000.02m = sends/detects only m wavelength But: It's in very, very early stage - no guarantee that it will work. By the way: No reason to explain yourself. I asked for input. You were one of the few who gave input. __________________ My Mediafire page: http://www.mediafire.com/hsie Last edited by h.sie; 05-07-12 at 02:57 PM.

05-09-12, 11:39 AM	#3362
h.sie Admiral Join Date: Jul 2008 Posts: 2,192 Downloads: 131 Uploads: 0	Regarding the introduction of two different wavelengths for radar & radar warn receivers (RWR), I can now give an overview what is possible and what not: 1) it is possible to introduce two different wavelengths using the insignificant digits of the MaxRange parameter in AI_Sensors.dat resp. Sensors.dat: Example: MaxRange=12000 : Sends/detects both cm- and m- radar wavelengths as before. MaxRange=12000.01 : Sends/detects only cm-wavelengths. MaxRange=12000.02 : Sends/detects only m-radar wavelengths. 2) BUT: The best (and nearby) solution is NOT possible: It is not possible for the RWR code, that continuously scans for enemy radar systems in render range, to find out the MaxRange (and thus wavelength) of every single radar system and react accordingly to the wavelength (i.e. detect it or not). I gave up here. 3) BUT: I am slightly optimistic to offer a workaround solution, that will work well in most situations: It is possible to determine 2 very important values by coding: a) the current distance between the Uboat and the closest cm-radar system and b) the current distance between the Uboat and the closest m-radar system. these two variables give answers to two important questions: a) is at least one cm-radar system in the maxRange of the RWR? b) is at least one m-radar system in the maxRange of the RWR? With these two answers, the workaround would work as follows: Lets assume the RWR detects only cm-waves and there is no cm-wave radar system in the MaxRange of the RWR. Then, the detection probability will be forced to 0, the RWR will be made blind, even if there is a m-radar in very close range. It won't be detected. If there is a cm-radar system in range, the RWR will be act unchanged and detect it soon. The only problem arises in situations where BOTH, cm- and m- radar systems, are in MaxRange of the RWR, because then the RWR is active and will "see" both systems (since in reality it cannot distinct between the wavelengths). IMO this is absolutely not critical, because it will cause a detection and a line on the NavMap, pointing into the direction of the detected radar (which could be the wrong direction to the m-radar, of course). One of the main problems (that the Metox detects cm-radar) could be solved to 99%. Thus, surprising aircraft attacks are possible without being warned by RWR. Feedback welcome. __________________ My Mediafire page: http://www.mediafire.com/hsie Last edited by h.sie; 05-09-12 at 04:18 PM.

05-09-12, 01:24 PM	#3363
Rubini Ocean Warrior Join Date: May 2005 Location: São Paulo Brazil Posts: 2,728 Downloads: 132 Uploads: 0	Hi h.sie, How are you mate? Sorry to be totally OT from your current work (radar lenght). I have not any knowledge to help you on this matter. But I should like to suggest a new item on your to do list about hydrophones. I guess that you know that some months ago I tried/made a small mod that adds three layers for hydrophone to add more playability and realism for the hydrophones . Also i guess that you have noted that only the more deep layer allows the player to listen by himself on the hidro station. A limitation from Sh3 that makes that mod just useful for half of the users. Perhaps with hardfix could be not difficult to cut the max hydrophone range (on sensors.dat) accordingly the depth of the uboat. Let's say: PD to -18m: 12000m, -17 to -28m: 18000m and <-28m: the maxrange as it is on sensors.dat. Thanks again by your great work. The radar fix will be another great addition! __________________ One gamer's must-have mod is another gamer's waste of time. -Sailor Steve

05-10-12, 03:38 PM	#3365
h.sie Admiral Join Date: Jul 2008 Posts: 2,192 Downloads: 131 Uploads: 0	@Rubini: Hi mate, maybe later. one project at a time. @Leitender: I don't understand. 1) Why do i have to rework the special U-Boat files and eventually the basic.cfg if I change the behavior of an RWR??? To change the RWR detection wavelength, only one change in Sensors.dat (MaxRange) for every RWR type is necessary with the hardcode fix. The Uboat will use the same RWR types as before. 2) Why do I have to alternate the .sns-files and decide, which system the special vessel will have? The vessels are already equipped with (the correct) radar. To change the radar wavelength, only one change in AI_Sensors.dat (MaxRange) for every radar type is necessary with the hardcode fix. The vessels and aircraft will use the same radar types as before. 3) Regarding 3 different wavelengths: The effort to model different wavelengths exponentially rises with the number of different wavelengths and thus only makes sense, if it had historical relevance (as it happened with Metox that couldn't detect cm-radar). Do you have any reliable historical information, that a similar problem existed for S-Band and X-Band? (i.e. RWR detected S- but not X-Band and vise-versa)? Did that cause similar problems as with Metox? To answer your question: I havn't played so far, so I cannot say whether I'm satisfied with the Sh3-Cmdr solution. IMO it's too crude to simply apply a failure probability of a certain percentage for the year 1943, independent of what radar a unit really is equipped with. But I must admit that I think about to go back to the simple Sh3-Cmdr solution. Hmmmm? __________________ My Mediafire page: http://www.mediafire.com/hsie

05-12-12, 07:10 AM	#3367
rowi58 Eternal Patrol Join Date: Jun 2006 Location: Karlsruhe Posts: 679 Downloads: 56 Uploads: 0	Hi h.sie, I*8217;m using the following solution within SH3_Cmdr's 8220;Randomised events.cfg8221;. Not as 8220;Malfunction8221;. Not as 8220;Sabotage8221;. Just a 8220;normal8221; event with 100% probability. It changes the 8220;MaxHigh8221; of the three RWR-sensors 8220;Metox8221;, 8220;Borkum8221; and 8220;Naxos8221; and reduces the precise and max. range of those. ;---------------------------------------------------------------------------------RadarWar--by-rowi58 [0:data\Library\Sensors.dat] ;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte ApplyToPeriod=19420801\|19430201 ChooseFrom=1 RndMidPat=1 0_x2729E=15000;.......... 8220;Naxos8221; - MaxHigh 0_x4BA99=7000;........... 8220;Borkum8221; - precise Range 0_x4BAAA=7000;........... 8220;Borlum8221; - max. range 0_x4BACE=15000;.......... 8220;Borkum8221; - MaxHigh 0_x4EE30=7000;............ 8220;Metox8221; - precise range 0_x4EE41=7000;............ 8220;Metox8221; - max. range 0_x4EE65=15000;.......... 8220;Metox8221; - MaxHidh ;-----------------------1943 [1:data\Library\Sensors.dat] ;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte ApplyToPeriod=19430202\|19430601 ChooseFrom=1 RndMidPat=1 0_x2729E=15000 0_x4BA99=7000 0_x4BAAA=7000 0_x4BACE=15000 0_x4EE30=5000 0_x4EE41=5000 0_x4EE65=200 ;-----------------------1943 [2:data\Library\Sensors.dat] ;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte ApplyToPeriod=19430602\|19431231 ChooseFrom=1 RndMidPat=1 0_x2729E=15000 0_x4BA99=7000 0_x4BAAA=7000 0_x4BACE=15000 0_x4EE30=5000 0_x4EE41=5000 0_x4EE65=60 ;-----------------------1944 [3:data\Library\Sensors.dat] ;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte ApplyToPeriod=19440101\|19440531 ChooseFrom=1 RndMidPat=1 0_x2729E=15000 0_x4BA99=5000 0_x4BAAA=5000 0_x4BACE=60 0_x4EE30=5000 0_x4EE41=5000 0_x4EE65=60 ;-----------------------1944_45 [4:data\Library\Sensors.dat] ;Simulation der elektronischen Kriegsführung - Radar gegen Radarwarngeräte ApplyToPeriod=19440601\|19451231 ChooseFrom=1 RndMidPat=1 0_x2729E=60 0_x4BA99=5000 0_x4BAAA=5000 0_x4BACE=60 0_x4EE30=5000 0_x4EE41=5000 0_x4EE65=60 Reducing the property 8220;MaxHigh8221; to 60 m (from 15.000 m) means that the RWR could not detect an aircraft with Radar 8211; but it could detect ships with Radar. I think, no scripted aircraft or those who are generated by SH3 (AirStrike.cfg) will fly at an altitude of less then 60 m. The start date and end date of each period refers to the appearance of RWR- and Radar-types, orienting at the 8220;Basic.cfg8221; and the SNS files of the most important sub chasing aircrafts such as Liberator, Wellington, Sunderland and Catalina. These dates can be different in every 8220;super Mod8221;. ATM, it works fine. The only problem is, that I can not say whether the reduction of 8220;MaxHigh8221; to 200 m will work because i don't know at which altitude non-scripted aircraft will approach. Note: the absolute hex-dresses will not work with Stock-SH3 or any other Mod including CCoM 8.1. The example above can not be used as a 8220;fix8221; or 8220;add-on8221; for the 8220;Randomised events.cfg8221;. Greetings rowi58 __________________ Last edited by rowi58; 05-14-12 at 12:07 PM.*

05-10-12, 01:42 AM	#3364
Leitender Planesman Join Date: Nov 2011 Posts: 191 Downloads: 50 Uploads: 0	h.sie, nice to see that you´re continuing your studies. If i compare your basic approach with your randomized_events solution, i see a benefit in differentiation of the wavelength which radar transmitters are to be discovered by RWR. In this case you have to determine if the sensor sends / reacts on cm, m or both m and cm waves. In reality, both bandwiths were only possible with combined systems for U-Boats as well as for AI ships. For U-Boats, a combination is possible and a second radar system is included in the big mods to have combined radio-systems. Until now, no combination of m and cm RWR is simulated, these banddiths are put together in one RWR sensor. You have to rework the special U-Boat files and eventually the basic.cfg To equip the AI ships you have to alternate the .sns-files and thus you have to decide, which system the special vessel will have. (i made the same thoughts, when fiddling around with combined asdic sensors. The SH3 devs simplified these real life combined systems in combining their characteristics in a unique sensor). In fact, there were three important bandwiths working during WW2: VHF-Band (1m-10m), S-Band (10cm-15cm) and X-Band (2cm-4cm). Maybe there should be introduced a third digit? And maybe more combined sensor systems? So my question is: Aren´t you satisfied with your own SH3 Commander solution? Or doesn´t it work (personally, i hadn´t yet the time to test)? I ask, because i found this solution very simple not only to simulate the Metox blackout, but also simple to attach it to the player´s system. Greetings

05-13-12, 04:56 PM	#3368
dariocapcro Watch Join Date: Mar 2011 Location: Croatia Posts: 19 Downloads: 91 Uploads: 0	croat Hello everyone, especially h.sie, I have a problem, I take off your v16b1 patch kit and read the instructions several times but it always throws me a message, sorry, no compatible version of sh3.exe found, can anyone help me or say in what order could be a problem, greetings from Croatian

05-14-12, 10:10 AM	#3369
h.sie Admiral Join Date: Jul 2008 Posts: 2,192 Downloads: 131 Uploads: 0	@rowi: thanks very much. the sh3-commander solution saves me a lot of time, trouble and controverse discussions. @dariocaprio: it seems you don't have the original & unpatched sh3.exe __________________ My Mediafire page: http://www.mediafire.com/hsie

05-14-12, 10:32 AM	#3370
dariocapcro Watch Join Date: Mar 2011 Location: Croatia Posts: 19 Downloads: 91 Uploads: 0	croat Regards, and I do not, means that it is impossible to use your version, I'm sorry but thanks, greetings to everyone

05-14-12, 11:57 AM	#3371
h.sie Admiral Join Date: Jul 2008 Posts: 2,192 Downloads: 131 Uploads: 0	sh3 is available for some bucks - it's worth the money (in combination with a supermod) __________________ My Mediafire page: http://www.mediafire.com/hsie

05-14-12, 01:15 PM	#3374
dariocapcro Watch Join Date: Mar 2011 Location: Croatia Posts: 19 Downloads: 91 Uploads: 0	croat Thanks everyone, h.sie, you're right

05-15-12, 10:53 AM	#3375
kaizerkat Helmsman Join Date: May 2006 Posts: 110 Downloads: 498 Uploads: 0	just getting back to sh3 and read this thread about this add-on to fix alot of things in sh3. Is there a thread on how to create a working directory so that i can try out these new fixes?