Page 33 of 371
RE: Thread for DB3000 database problems, updates or issues
Posted: Thu Apr 03, 2014 10:40 pm
by mikmykWS
DB queries and requests logged from my last post. Thanks guys!
Mike
RE: Thread for DB3000 database problems, updates or issues
Posted: Sat Apr 05, 2014 6:44 am
by ipe
ORIGINAL: El Savior
Finland Hamina-class is without SONAR and ASW-weapons:
The sonar suite includes a Simrad Subsea Toadfish active high-frequency search and attack sonar, and a Sonac/PTA towed array sonar. Not sure which model it is, but it can be added same Toadfish sonar in Rauma-class SS2400 Toadfish.
1 ×  rail for depth charges or mines (depth charges are normal load)
1 x Sonac/PTA towed array sonar
Also speed for Hamina is 30+ knots. I know that they can go much faster with their state of the art water propulsion jet. Adding few knots wont do bad. True high speed is classified, but 35 knots can be easily achieved. Older Rauma class can go at least 35 knots too, which Hamina replaced.
http://www.naval-technology.com/projects/haminaclass/
http://en.wikipedia.org/wiki/Hamina-class_missile_boat
Hämeenmaa minelayer is without mines. From 2009+ new mine can be added: Sea Mine 2000 - bottom, Acoustic & target Discrimination. Older version use bottom mines.
4 × rails for 100-150 mines
http://en.wikipedia.org/wiki/H%C3%A4mee ... _minelayer
Thanks!
No, no and no. Hamina doesnt have any ASW sensors. That faulty information been circling all over internet since 90s. Hamina only has ability to take depth charges and their use is controlled by other ships (like Rauma).
Katanpää-class MHC could be added thats newest class of ships in finnish navy.
http://en.wikipedia.org/wiki/Katanp%C3% ... ure_vessel this wikipedia page is accurate.
RE: Thread for DB3000 database problems, updates or issues
Posted: Sat Apr 05, 2014 11:42 am
by VFA41_Lion
RE: Thread for DB3000 database problems, updates or issues
Posted: Sat Apr 05, 2014 5:04 pm
by Coiler12
One interesting what-if is the 747 CMCA variant, a bomber/missile carrier proposal for the 747.
RE: Thread for DB3000 database problems, updates or issues
Posted: Sun Apr 06, 2014 6:14 am
by Sardaukar
RE: Thread for DB3000 database problems, updates or issues
Posted: Mon Apr 07, 2014 12:59 am
by slicendice
EO DAS sensor apppears to be nonfunctional as of build 411. I could see that some fixes were applied to build 410 version to allow it to better represent it's real world functionalities(although I'd say that its detection range and update rate is still inadequate). So what was the change between the two builds?
I think I have mentioned this before, but Sea Giraffe 150 HC still lacks a surface search ability. Now LCS 2 is left without a surface search radar which is totally laughable.
RE: Thread for DB3000 database problems, updates or issues
Posted: Mon Apr 07, 2014 5:42 pm
by Broncepulido
I see the RBS70 missile variants are listed as RB 70, it was almost impossible to find it (also it's not present the RBS90 twin pedestal mount, because the performances very probably employing the RBS70 Mk2 missile, employed by Sweden 1993-2004).
http://sv.wikipedia.org/wiki/RBS_90
EDIT: Don't mean on it, sorry, I see RBS is the System and is listed as "Facility", RB (Robot) is only the missile. Thanks and go forward!
RE: Thread for DB3000 database problems, updates or issues
Posted: Wed Apr 09, 2014 11:28 pm
by mikmykWS
ORIGINAL: Coiler12
One interesting what-if is the 747 CMCA variant, a bomber/missile carrier proposal for the 747.
Have added the request but if you could post some links it would really help us out.
Thanks!
Mike
RE: Thread for DB3000 database problems, updates or issues
Posted: Thu Apr 10, 2014 3:17 am
by Mgellis
ORIGINAL: mikmyk
ORIGINAL: Coiler12
One interesting what-if is the 747 CMCA variant, a bomber/missile carrier proposal for the 747.
Have added the request but if you could post some links it would really help us out.
Thanks!
Mike
This is what I could dig up...
http://www.g2mil.com/bm747.htm
http://wethearmed.com/military-and-law- ... -a-bomber/
http://www.rand.org/content/dam/rand/pu ... MR1028.pdf
http://www.fas.org/man/eprint/benson.htm
http://www.flightglobal.com/pdfarchive/ ... 00348.html
I hope this helps.
Mark
RE: Thread for DB3000 database problems, updates or issues
Posted: Thu Apr 10, 2014 5:00 pm
by Coiler12
Don't worry, for my next batch of never-were requests I do have links. Sorry about not getting any for the 747 bomber/missile carrier, I couldn't find many exact proposals.
A-6F Intruder:
Upgraded A-6. Cancelled in favor of the A-12 and then not revived due to post-USSR budgets. (Ironically, the most exact specifications I found were in Russian)
A-6F Intruder (in Russian)
F-117B (Land based) and A/F-117X (Carrier based):
Upgraded F-117.
F-117 Variants
And from Russia, the Il-102, a ground attack plane with an anachronistic tail-gun system passed up in favor of the Su-25.
Il-102
RE: Thread for DB3000 database problems, updates or issues
Posted: Thu Apr 10, 2014 8:08 pm
by mikmykWS
Requests logged. Thanks!
Mike
RE: Thread for DB3000 database problems, updates or issues
Posted: Fri Apr 11, 2014 9:06 am
by ComDev
F-23
Understood, but so could the F-22 until they introduced the clipped-fin AIM-120. So makes sense to keep the load at 6x? [8D]
RE: Thread for DB3000 database problems, updates or issues
Posted: Mon Apr 14, 2014 8:36 am
by slicendice
http://news.usni.org/2014/04/09/navy-ax ... llfire-lcs
LCS Will have Longbow Hellfire instead of Griffin IIB as interim ASuW weapon, for now at least. However I'm really worried about it's ingame lethality against surface target due to the HEAT warhead type.
And I'm not sure about the status of the X-47B entry ingame. If it is meant to be a placeholder for UCLASS, I'd suggest removal for the time being. There's no firm info on it, we won't even know the preferred airframe for at least another year. That means some possible substantial change later on. X-47B itself was never meant to be operational.
RE: Thread for DB3000 database problems, updates or issues
Posted: Mon Apr 14, 2014 2:42 pm
by Mgellis
ORIGINAL: slicendice
And I'm not sure about the status of the X-47B entry ingame. If it is meant to be a placeholder for UCLASS, I'd suggest removal for the time being. There's no firm info on it, we won't even know the preferred airframe for at least another year. That means some possible substantial change later on. X-47B itself was never meant to be operational.
No! Don't take our killer robots away!
Seriously, I'd argue it's better to have a guesstimate version of a future platform than nothing at all; one can always update the information as new data comes in. This way, it and other things like the Global Combat Ship can at least be used in scenario designs.
One issue in scenario design is that some political events are more plausible if you set them ten or fifteen years in the future (i.e., give the world enough time for things to
really go to hell in a hand basket) but, of course, we have limited information on what might be in service five or six years down the line and which could be included in the scenario. Like the deployed X-47B (I think I suggested the database editors could use "MQ-47C Medusa" instead to distinguish it from the experimental version.) So, guesstimates on bleeding edge platforms are fine with me. It's better than not having them.
RE: Thread for DB3000 database problems, updates or issues
Posted: Mon Apr 14, 2014 3:04 pm
by Mgellis
ORIGINAL: slicendice
http://news.usni.org/2014/04/09/navy-ax ... llfire-lcs
LCS Will have Longbow Hellfire instead of Griffin IIB as interim ASuW weapon, for now at least. However I'm really worried about it's ingame lethality against surface target due to the HEAT warhead type.
Just curious...anyone know how many missile will be in the VLS Longbow modules? As I recall, the Griffin module had 15 missiles; will it be about the same number?
RE: Thread for DB3000 database problems, updates or issues
Posted: Wed Apr 16, 2014 10:34 am
by Rudd
This may be of interest
P-8 with the AN/APS-149 or new Advanced Airborne Sensor?
from
http://foxtrotalpha.jalopnik.com/exclus ... 1562912667
RE: Thread for DB3000 database problems, updates or issues
Posted: Thu Apr 17, 2014 9:57 pm
by NickD
I'd like to register a couple of low-priority requests for New Zealand:
SH-2G(I) Seasprite
NZ has recently purchased ten of the SH-2G(A)s which were originally purchased by Australia but handed back to Kaman when the project was cancelled in 2008. Kaman has actually managed to make them work (with a less ambitious avionics fit, but still capable of operating Penguin missiles) and NZ will operate eight of them from its warships and use the other two as sources of spare parts. They're scheduled to enter service with the RNZAF between 2014 and 2016 and will replace the service's five SH-2Gs:
*
http://www.navy.mil.nz/mtf/na/rec-act/a ... bility.htm
*
http://www.navy.mil.nz/mtf/na/rec-act/q ... prites.htm
*
http://www.defenseindustrydaily.com/aus ... ect-03338/
Protector class OPV
The first tier of the RNZN's patrol force, these two ships can each carry a helicopter and were designed to operate between the South Pacific and the Antarctic:
*
https://en.wikipedia.org/wiki/Protector ... rol_vessel
*
http://www.naval-technology.com/project ... assoffsho/
RE: Thread for DB3000 database problems, updates or issues
Posted: Fri Apr 18, 2014 12:39 am
by orca
Can you add sensors to mq-8c similar to mq-8b?
I assume they will have equivalent or better.
RE: Thread for DB3000 database problems, updates or issues
Posted: Fri Apr 18, 2014 8:01 pm
by Beagle
I would like to add a low priority request for runways to allow two fighters to take off at once. This is quite common place and makes a big difference on intercept missions in getting the extra fighters off the ground quicker.
RE: Thread for DB3000 database problems, updates or issues
Posted: Fri Apr 18, 2014 11:50 pm
by mikmykWS
ORIGINAL: Beagle
I would like to add a low priority request for runways to allow two fighters to take off at once. This is quite common place and makes a big difference on intercept missions in getting the extra fighters off the ground quicker.
Pretty sure this will be available next public beta release.
M