Page 4 of 15
RE: RUSSIAN ACTIVE OPTION UPLOADED
Posted: Tue May 09, 2006 1:13 am
by el cid again
Ship ID: 2640 (Iyang Maru) - ship sunk (431013) before arrival date (440303)
Ship ID: 2648 (Kako Maru) - ship sunk (440612) before arrival date (441029)
Ship ID: 2650 (Kanagawa Maru) - ship sunk (441113) before arrival date (450415)
Ship ID: 2654 (Kasei Maru) - ship sunk (440615) before arrival date (441102)
Ship ID: 2656 (Kashimasan Maru) - ship sunk (430228) before arrival date (440311)
Ship ID: 2659 (Keian Maru) - ship sunk (430922) before arrival date (440108)
Ship ID: 2660 (Keito Maru) - ship sunk (440912) before arrival date (450107)
Ship ID: 2662 (Kensei Maru) - ship sunk (440624) before arrival date (440802)
Ship ID: 2664 (Kifune Maru) - ship sunk (441223) before arrival date (450316)
Ship ID: 2670 (Koetsu Maru) - ship sunk (440408) before arrival date (440411)
Ship ID: 2673 (Koko Maru) - ship sunk (440907) before arrival date (440927)
Ship ID: 2678 (Koun Maru) - ship sunk (440912) before arrival date (450602)
Ship ID: 2680 (Kuniyama Maru) - ship sunk (431111) before arrival date (431123)
Ship ID: 2681 (Kunuki Maru) - ship sunk (440909) before arrival date (450405)
Ship ID: 2683 (Kurokamisan Maru) - ship sunk (441102) before arrival date (450127)
Ship ID: 2691 (Meiho Maru) - ship sunk (440812) before arrival date (441122)
Ship ID: 2693 (Michi Maru) - ship sunk (450102) before arrival date (450123)
Ship ID: 2697 (Mikamisan Maru) - ship sunk (441024) before arrival date (450515)
Ship ID: 2723 (Otsuyama Maru) - ship sunk (440124) before arrival date (440828)
Ship ID: 2725 (Peihua) - ship sunk (430409) before arrival date (440903)
Ship ID: 2726 (Pluto Go) - ship sunk (450323) before arrival date (450529)
Ship ID: 2734 (Samukaze Maru) - ship sunk (440103) before arrival date (450501)
Ship ID: 2742 (Shingi Maru) - ship sunk (440905) before arrival date (441031)
Ship ID: 2746 (Shinragi Maru) - ship sunk (440704) before arrival date (450501)
Ship ID: 2748 (Shinten Maru) - ship sunk (440218) before arrival date (440313)
Ship ID: 2755 (Shoyu Maru) - ship sunk (420825) before arrival date (440301)
Ship ID: 2759 (Shuyo Maru) - ship sunk (420401) before arrival date (440320)
Ship ID: 2766 (Taietsu Maru) - ship sunk (431018) before arrival date (440627)
Ship ID: 2769 (Taijo Maru) - ship sunk (440220) before arrival date (440808)
Since all of these are from CHS and none were changed, I fear this is an inherited issue. But I will fix it in RHS and look to see if it is in CHS.
This is slightly frightening: the dates are NOT the same in CHS. I wonder how they got changed? No matter - we change them back.
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 1:16 am
by bbbf
ORIGINAL: el cid again
- Type 13 radar (139) has no penetration -> should have penetration 500 since it is air search radar
Here you have run into a code problem:
A radar cannot be what Type 13 is - surface search/air search
It is primarily asurface search radar - so that is how I code it - and so do CHS and stock. This is as correct as can be - but not quite right with respect to reality.
Is there enough room to have a Type 13 Air and a Type 13 Surface? Then mount both to achieve the same result?
A lot of doubling up, but you achieve the desired end.
RE: RUSSIAN ACTIVE OPTION UPLOADED
Posted: Tue May 09, 2006 1:17 am
by CobraAus
Now I need 2 helpers with Broadband 1 in EU and 1 in US to get around the timezone problem
and assist in getting out the updates I will send the lastest updates to them and they can send out to requesters when I am having zzzzzzzzzz
if you are willing to help just PM me
The relay positions have been filled and thanks to Hipper (EU relay) and Witpqs (US relay)
they will answer PM requests and e-mail for larger files and take a bit of the load off me
and allow me to zzzzzzzzz with no loss of time to you guys
Cobra Aus
RE: RUSSIAN ACTIVE OPTION UPLOADED
Posted: Tue May 09, 2006 2:57 am
by CobraAus
minor upgrade v2.15 (1 file for each scenario) has be sent out check PM's - no get just PM me
Cobra Aus
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 6:48 am
by Aterpa
ORIGINAL: el cid again
- Type 13 radar (139) has no penetration -> should have penetration 500 since it is air search radar
Here you have run into a code problem:
A radar cannot be what Type 13 is - surface search/air search
It is primarily asurface search radar - so that is how I code it - and so do CHS and stock. This is as correct as can be - but not quite right with respect to reality.
This is a known bug in the stock scenarios. There is even a downloadable tool for changing the penetration value from 0 to 500 in the original stock scenarios.
This is very important because the type 13 radar is used for the land based aircraft support units. As soon as they are upgrading their sound detectors to type 13 radar they are loosing all of their enemy aircraft detection capability. (I believe in RHS it is the same upgrade path, I dont have the file here at the moment.) Since the code can only have either air search radar or surface radar, type 13 radar has to be air search radar to work with the land based air support units. On ships there is usually one or more additionally surface radar, so it does not matter that the type 13 is only air search radar.
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 7:00 am
by Aterpa
ORIGINAL: el cid again
MAD (223) has penetration 500 -> should have 0 to work as surface radar
Here I think you are correct. Hard to tell - since we are really messing with the code.
Hmmm - in MY files it IS 500. So maybe you don't have the right file?
Yes it is currently 500, but it should be 0 to work as surface radar. Since it is intended to help finding submarines (ships) it should be surface radar (0) not air search radar (500). (I dont now if any kind of radar actually works on airplanes with the code.)
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 7:53 am
by Hipper
Hi folks Just PM me & I'll send along the 2.15 fix and the art fix to whoever wants them
cheers
Reply to PAD152
Posted: Tue May 09, 2006 12:15 pm
by el cid again
I have examined the data set in the context of your report.
About half of it is confusion on the part of the program - it cannot tell we want to upgrade to that ship - if the name is not identical it gets upset.
Or it is upset I changed the name of an engine slightly - I really didn't change the device at all. These things we can ignore.
The OTHER half is different. There are all sorts of things there. Some are trivial - a 1 in a field which will not be used. Some are significant. Some are inherited - and some are generated by changes we have done.
And some led me to several - even dozens - of other issues: IF you change certain things you must update all the records that use it in many cases. The issue about carrier ordnance may matter: my tests imply it does not matter in fact - but I converted over to the stock system for safety.
Because there are device changes - I have skipped to the next sequence in version numbering. I have just uploaded 2.20 to Cobra et al - and it is the same as I was going to call 2.16. But the implication is "don't use anything older than 2.2 something" - the changes are enough to warrant a new version - a prohibition against using older file sets - and a hope this is the end of the major issues. The good news is that there seem to have been an awful lot of lines that didn't generate errors.
Anyway - thanks.
Changes in planning (for all scenarios) are
adding Avro Anson - if Cobra is able to put his art in the art set -
apparently it was important down under but it was not allowed to be in the CHS data set
adding in a lot of corrections to Allied warships - done by AK Dreemer -
I wanted them now but need him to retransmit - and this was too important to wait.
I will slow down for 5 days - I must work a real work week for the first time in ages - but I will be around -
feed ANY issues back to me, cobra or the Forum.
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 12:18 pm
by el cid again
BBBF: There are NO slots for radar. I had to get rid of three kinds - due to computer report indications they would not work. I have no ability to add radar types until we get information what slots might be workable?
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 12:26 pm
by el cid again
A radar cannot be what Type 13 is - surface search/air search
It is primarily asurface search radar - so that is how I code it - and so do CHS and stock. This is as correct as can be - but not quite right with respect to reality.
This is a known bug in the stock scenarios. There is even a downloadable tool for changing the penetration value from 0 to 500 in the original stock scenarios.
This is very important because the type 13 radar is used for the land based aircraft support units. As soon as they are upgrading their sound detectors to type 13 radar they are loosing all of their enemy aircraft detection capability. (I believe in RHS it is the same upgrade path, I dont have the file here at the moment.) Since the code can only have either air search radar or surface radar, type 13 radar has to be air search radar to work with the land based air support units. On ships there is usually one or more additionally surface radar, so it does not matter that the type 13 is only air search radar.
IF you know of ANY issue of this sort - AND IF you tell me - it gets fixed. This will be in 2.21 - whenever that is released. RHS is a product of the FORUM - and feedback changes it. This is not the old days of "we know it is bad - but we won'd address it any time soon."
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 12:27 pm
by el cid again
Here I think you are correct. Hard to tell - since we are really messing with the code.
Hmmm - in MY files it IS 500. So maybe you don't have the right file?
Yes it is currently 500, but it should be 0 to work as surface radar. Since it is intended to help finding submarines (ships) it should be surface radar (0) not air search radar (500). (I dont now if any kind of radar actually works on airplanes with the code.)
Good catch. I got it backwards - twice. OK - it will be fixed in a few seconds. Look for it whenever 2.21 comes out.
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 2:05 pm
by Sardaukar
I'm not sure that air-to-surface radar works in game. But I'm very happy if it is found working. It's been very difficult to test if it works or not. Damn shame if it cannot be implemented since it is quite major part of "electronic warfare" in WW II.
In surface ships radar type switch (0 or 500) should and as far as I know they work fine. But there could be trouble using the switch on planes since aircraft radars may be coded differently. I did add myself (and it'll be in CHS, I think) air search radars to subs (SD and such) and they did seem to work remerkably well.
Now, Blimp should not be a problem if it's classified as "surface ship".
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 5:54 pm
by el cid again
In surface ships radar type switch (0 or 500) should and as far as I know they work fine. But there could be trouble using the switch on planes since aircraft radars may be coded differently. I did add myself (and it'll be in CHS, I think) air search radars to subs (SD and such) and they did seem to work remerkably well.
Now, Blimp should not be a problem if it's classified as "surface ship".
Most ships of any size get both surface and air radar - so there should be no need for a switch in that case. And yes, a Blimp is a misnamed PC - it should simulate "sonar" as well as any PC does - that is poorly - they had sonabouys to help confirm MAD contacts. The problem with a blimp - as in real life - is you don't want to get into a real battle with it! Is the AI smart enough to run?
RE: FILE SET RHS 2.14 Released for CVO and RAO
Posted: Tue May 09, 2006 10:27 pm
by CobraAus
I am up again and v2.20 is packaged and sent out to relays and those on my list
Cobra Aus
RE: FILE SET RHS 2.21 Released [Minor update]
Posted: Tue May 09, 2006 10:42 pm
by el cid again
Fixing MAD, upgrade for Japanese sound detector,
adding minor supply sinks, a few supply points to US
West Coast Cities.
United States cannot handle the 22,500 supplies per day of CHS
nor the 20,000 per day of stock - so reduced to 18,000. This seems to
be workable - but 18,000 fuel is going to overfill the buffer - so it is still too high.
The good news is no major problems have been detected. Corrections for Allied warships - and an airplane - are ready to add. If Cobra can put his art in the plane art set - I am told he did the Avro Anson but it didn't get added to CHS. Do we have an art slot?
RE: FILE SET RHS 2.21 Released [Minor update]
Posted: Tue May 09, 2006 10:52 pm
by CobraAus
I am told he did the Avro Anson but it didn't get added to CHS. Do we have an art slot?
I on it Sid will look at this morning if you set it up as slot 166 bitmap 97
you can get 2.21 out and I will follow shortly with Art upgrade
Cobra Aus
RE: FILE SET RHS 2.21 Released [Minor update]
Posted: Tue May 09, 2006 11:48 pm
by CobraAus
RHSRAO v2.21 packaged and sent to relays
Cobra Aus
RE: FILE SET RHS 2.21 Released [Minor update]
Posted: Wed May 10, 2006 3:19 am
by Buck Beach
Is this just a beta? I went to Spookies and there is nothing. I went to Rogue and the link is inoperable. I would like to try the RHS because there seems to be nothing coming from CHS. I am not interested in being a tester. The threads keep saying this is a release. Who is for, the public or an in house group still testing?
RE: FILE SET RHS 2.21 Released [Minor update]
Posted: Wed May 10, 2006 4:54 am
by m10bob
ORIGINAL: Buck Beach
Is this just a beta? I went to Spookies and there is nothing. I went to Rogue and the link is inoperable. I would like to try the RHS because there seems to be nothing coming from CHS.*** I am not interested in being a tester.***** The threads keep saying this is a release. Who is for, the public or an in house group still testing?
This is still in testing..
RE: FILE SET RHS 2.21 Released [Minor update]
Posted: Wed May 10, 2006 6:47 am
by Guest
Could you please send me the scenarios? Thanks.