Korea 2012 Megapack for BMS 4.34
-
Hi, I tried to use lod editor with the new 434 version and it did not work… as I was willing to do a revision on the F22. Now I do not know what to do… have you included the F22 I’ve created?
Regards Metalhead -
I beg your pardon… what?
Just for your information, Gentlemen, and for precision’s sake only: Chuckles clearly meant here to refer to ‘Korea 2012’ folder in his description… logical typos happen sometimes, told this by a well known specialist :lol:
With best compliments, Chuckles, being aboard and within the ‘crew’ was too much fine this time too!
Have great fun all with this beauty, mates, you will see immediately it.
With best regards to all.
759 is the serial of the '18C/D in the UI image posted in OP.
-
Hi, I tried to use lod editor with the new 434 version and it did not work…
You have to convert the DB with 3ddb_builder for LE to work. It’s in your install Tools folder. Read the documentation that is included along with it!!
C9
-
Thanks a ton Chuckles! Does this have Janhas’s models in it already?
-
Thanks a ton Chuckles! Does this have Janhas’s models in it already?
CCC created the DB for this theatre, so I will defer to CCC for the correct answer.
-
no, i didn’t touch F-16 stuff in tweaked DB.
BTW the tweaked DB is not used - it is directed to use default korea DB in tdf file.
-
Installing now thx !!!
-
I beg your pardon… what?
With best regards to all.
…I have an acquaintance with that particular CF Hornet. If I remember right.
-
I wonder why all F18E and F Super Hornets at these new theatres, have the same problem of a not working launch bar, so preventing catapult launching.- I have in every case to edit its *.dat file including the missing line, and then it works.- Can’t they share the same common Falcon 4.34/Data/Sim/Acdata folder ?
-
no, i didn’t touch F-16 stuff in tweaked DB.
BTW the tweaked DB is not used - it is directed to use default korea DB in tdf file.
Thanks for the information. So do we need to edit the .tdf in order to use the tweaked database?
-
I tried all the carrier campaigns on this theatre, and cannot set the carrier UHF frequencies, either by the presets or tunning the real frequencies
-
Thanks for the information. So do we need to edit the .tdf in order to use the tweaked database?
Apart from tdf, you need modded Art and campaign folder files to activiate that DB.
be patient, the key is campaigns are not modified to use tweaked DB.
-
I tried all the carrier campaigns on this theatre, and cannot set the carrier UHF frequencies, either by the presets or tuning the real frequencies
This will be added to the bug list.
-
Well…. missed this one because I’m just not a carrier ops addicted, to be honest. :lol:
So, my apologies to all concerned.Wih best regards.
-
I tried all the carrier campaigns on this theatre, and cannot set the carrier UHF frequencies, either by the presets or tunning the real frequencies
Firstly, to Chuckles and everyone else involved, thank you VERY much for bringing K’12 back!
I can also confirm and hopefully amplify on Soldano’s bug report. At first I did a k’12 Viper mission from Kunsan and everything was normal.
Then I went to Maxx and did a mission of Enterprise. On deck when I called for QNH, Taxi, etc., I got Kunsan. They gave me a QNH but everything else was “contact when in my airspace.” This was with presets and manually setting ground freq per briefing. I did save and load the DTE for the Maxx mission.
I hope that helps. -
I wonder why all F18E and F Super Hornets at these new theatres, have the same problem of a not working launch bar, so preventing catapult launching.- I have in every case to edit its *.dat file including the missing line, and then it works.- Can’t they share the same common Falcon 4.34/Data/Sim/Acdata folder ?
I quoted my previous post, just to remember users of this new theater who want to fly carrier missions, to edit previously the F18E.dat and F18F.dat files, adding the line related to the launchbar.- If not, you will find that catapult launchings with Super Hornets are not posible .- It seems to happen with every new theater released ultimately
-
Firstly, to Chuckles and everyone else involved, thank you VERY much for bringing K’12 back!
I can also confirm and hopefully amplify on Soldano’s bug report. At first I did a k’12 Viper mission from Kunsan and everything was normal.
Then I went to Maxx and did a mission of Enterprise. On deck when I called for QNH, Taxi, etc., I got Kunsan. They gave me a QNH but everything else was “contact when in my airspace.” This was with presets and manually setting ground freq per briefing. I did save and load the DTE for the Maxx mission.
I hope that helps.Good Day, All. Update on the above post: Last night after writing this I went into Mission Commander , and activated the carrier in K’12. I also changed it to Enterprise and moved it to the west coast (personal preference). Anyway, as I was Briefing the first mission I noticed the presets for UHF 2-4 were what I had been using in other theaters, and more importantly they worked in the cockpit. They are (for Enterprise ground/tower/approach) 265.3,.2,.1, respectively.
The TACAN did not work, so I went back into MC and changed it to the 16x from my notes.
I haven’t had a chance to test TACAN in K’12,yet, or test comms in Maxx, but I’ll let you know.
So, it may not be a bug, per se. It may just be the original install freq values are not what we’re used to seeing. -
I quoted my previous post, just to remember users of this new theater who want to fly carrier missions, to edit previously the F18E.dat and F18F.dat files, adding the line related to the launchbar.- If not, you will find that catapult launchings with Super Hornets are not posible .- It seems to happen with every new theater released ultimately
Thx, for that tip, Soldano. This-# Launchbar
#–---------------------------------------------------
hasLaunchBar 1
LaunchBarMinAngle 0.0
LaunchBarMaxAngle 80.0
is what I copied and pastes from f18c.dat to f18e.dat.
I’ll let you know if it works! -
It will work… with F18E/F/ G(EA-18G) … but, caveat… it wont work with all? (specific) plane(s). I think its about some new ‘switch’ in model itself. … I’m bugging MaV-jp to split teh beans… but he’s all but not ears.
I.e. with AV8B you’ll get CTD saying error in ‘input’ (LoL) … but yeah, it doesn’t work unfortunately… only! for the ‘player’ … AI planes use cat launch like for breakfast, even US cat , or Kuznetsov type launch.
But F18 family works out of the box, so, enjoy.
-
It will work… with F18E/F/ G(EA-18G) … but, caveat… it wont work with all? (specific) plane(s). I think its about some new ‘switch’ in model itself. … I’m bugging MaV-jp to split teh beans… but he’s all but not ears.
I.e. with AV8B you’ll get CTD saying error in ‘input’ (LoL) … but yeah, it doesn’t work unfortunately… only! for the ‘player’ … AI planes use cat launch like for breakfast, even US cat , or Kuznetsov type launch.
But F18 family works out of the box, so, enjoy.
Good Day, White_Fang and All, and compadre, you are right. When I put
Launchbar
#–---------------------------------------------------
hasLaunchBar 1
LaunchBarMinAngle 0.0
LaunchBarMaxAngle 80.0
into the Korea 2012 acdata ,and it worked. So, say you’re flying k’12, you have to put it in the appropriate ,K’12, acdata folder. The first time I tried I put it in the Korea folder-wrong.
On the second try, it worked, with a couple of visual observations. First, I assigned and used keyboard callbacks, so I don’t know if the switch moves in’pit.Secondly, the launch bar itself does not go up and down . When I extended the LB, the jet tilted slightly down by the nose. Very Tomcat-esque!
But the key thing is, The Rhino is now carrier-qualified.