Korea '80s Theater - discussion
-
Ok, I cant get mine to work…I have the new UI and it all seems fine until I try and fly a mission, the CTD’s. Have tried campaign and Dogfight. I renamed my original “sim” folder for backup and copied in the supplied one. Likewise the 2 cockpit art folder contents. Any ideas what may be my error? Thanks! I am using a modified object s molder from Rthorflech, but that should not be a problem should it, as the new theater has it sown new objects folder and DB…
Cheers, Mark
-
I have the new UI and it all seems fine until I try and fly a mission, the CTD’s.
Pls. post always that which AC cause the problem. Strange the so many CTD report. I flew so many AC to test their rack config and AI wepon usage. Except F-14 pit issue I did not get any CTD.
-
Both flights I chose F-16 BLK-40 to check out the new pit…
-
If also the Blk. 40 pit is turned to a buggy status somehow I will be very nervous. I did not touch anything concerning on pits because I have 0 skills in that area. I have posted screenshots and videos about 2 month ago, they worked fine.
How can it be that they were functional that time but they are not now…?
:evil:
As I can remember I have a backup DB from time when both of new cockpits have been integrated. If I cannot fix the problem means that I need some day to apply tweaks again that I have done once…
-
update 5?
perhaps pits worked with u 4…
wild wild thought -
Hm… Maybe, but it is not likely. Yesterday I checked an older DB, F-14 pit was functional in a DB which I use end of March. I haven’t checked F-16C Block 40/42. If you delete the cockpit files of Block 40/42 you can use them, but of course in this case they will have Block 50/52 cockpit.
-
Just for clarification. I won’t give up. If I have to redone tweaks on old DB, I will do it. I simply put so many effort into mod - as well other contributors - to not let lost new 3D pits.
-
Hi Molni, I will check later if the same issue occurs if I fly BLK-52 Viper. It may be I have done some other step wrong of course and the pit is not the problem. I will also check using F-14
-
number 2 and number 3 wont extract wtf!!! It says it cannot open the archive!!!
-
I made a test with and older DB. F-14 3D pit works but Block 40/42 cause CTD. It is very strange because the DB as I can remember backed up just after the integration of the pit.
-
i have some graphik issues with f4e, esk, d with their gear and flaps afterburner and flaps i think…is their someone else with the same problem?
-
Pls. post pictures about the bugs.
-
number 2 and number 3 wont extract wtf!!! It says it cannot open the archive!!!
If you extract number 1, it automatically extracts 2 and 3.
-
-
Ok, I tested the DB with U4 too. Issues are the same… I have no idea why. I have a DB which date is 17.03.2013. This day I posted a preview about F-16C Block 40/42 pit. That time DB worked now the same DB cause CTD everytime if I select F-16C Block 40/42 pit…
Honestly, I run out ideas how can be fixed and what can cause the issue. In an older DB F-14 pit works, but Block 40/42 cockpit is not, which is more important. I can release a functional MOD without the new F-16 cockpit sooner or later but without help I cannot fix the pit issue…
-
I have had CTD with the Block 40/42 mod in the past due to wrongly set 3dckpit.dat parent numbers so you might want to check there first.
i.e. Falcon BMS 4.32\Data\Art\ckptart\F-16C-40\3dckpit.dat
The original 3dckpit.dat explicitly refers to Parent 4
cockpithudmodel 4; LOD#7321 @ 60000
a new parent might be created (3152) to add a new HUD model and 3dckpit.dat updated to refer to the new parent.
cockpithudmodel 3152; LOD#7473 @ 600000
Unfortunately the files in “Falcon BMS 4.32\Data\Art\ckptart” are not theatre/DB specific.
So, if the new parent isn’t present in the Original BMS or another Add-on Theater DB, BMS will CTD (due to the missing parent) when the user tries to fly that particular plane/version.
Original Blk 40 HUD Mod with pilot v2.04 texture used in LODs 8018 82, 7319 8019 82, 7319 8020 7320, 7321, 7322 8021 7318 cockpitmodel 3120;LOD#7318 @ 600000 cockpitmodel2 3121;LOD#7319 @ 600000 cockpitmodel3 3122; LOD#7320 @ 600000 cockpithudmodel 3123; LOD#7321 @ 60000 cockpitcanopymodel 3124; LOD LOD#7322 @ 60000 used in 3dckpit.dat Original data cockpitmodel 1;LOD#7318 @ 600000 cockpitmodel2 2;LOD#7319 @ 600000 cockpitmodel3 3; LOD#7320 @ 600000 cockpithudmodel 4; LOD#7321 @ 60000 cockpitcanopymodel 5; LOD LOD#7322 @ 60000 F-16C-40 F-16C-42 F-16D-40 F-16D-42 Blk 40 HUD Textures 8020 and 8021 changed to 8520 and 8521 New Parents and LODs cockpitmodel 3149;LOD#7470 @ 600000 cockpitmodel2 3150;LOD#7471 @ 600000 cockpitmodel3 3151; LOD#7472 @ 600000 cockpithudmodel 3152; LOD#7473 @ 600000 cockpitcanopymodel 3153; LOD LOD#7474 @ 600000 cockpitmodel 3149;LOD#7470 8021 ref changed to 8521 cockpitmodel3 3151; LOD#7472 8020 ref changed to 8520 cockpithudmodel 3152; LOD#7473 8020 ref changed to 8520 cockpitcanopymodel 3153; LOD LOD#7474 8020 ref changed to 8520
-
Spit integrated the cockpit, I did not touch the pit in DB and of course I did not edited the cockpit dat files. He set the parents, LODs, everything according to demand of my MOD. It worked 2 months ago but currently it does not regardless I did not changed anything. I cannot solve this mystery…
I cannot interprate the code what you posted. I know what are in my files.
cockpitmodel 3138;
cockpitmodel2 3139;
cockpitmodel3 3140;
cockpithudmodel 3141;
cockpitcanopymodel 3142;
cockpitrttcanopymodel 6;
cockpitwingsmodel 3110;
cockpitwingsdfmodel 3110;
cockpitmodel_empty 3118;
cockpitcanopymodel_empty 3119;They are not the same, my guess spit used differnt LOD numbers, but it worked.
-
I cannot interprate the code what you posted. I know what are in my files.
cockpitmodel 3138;
……They are not the same, my guess spit used differnt LOD numbers, but it worked.
Yes, the parent numbers are particular, mine were just examples. I did a quick check on “Test release 4” with LE to make sure the cockpit.dat parents and LODs existed for the Block 40 and all looked ok but isn’t as it CTD so can’t help further.
I’ve had models missing/wrongly displayed that I was able to repair by reinstalling the LOD/textures with LE but worry about the DB integrity afterwards.
-
I got it working by using the stock pits, but it CTD’d on me halfway through my first campaign mission. Would you be interested in the crash log Molni?
-
I cannot interprete chrashlogs.
About cockpit issues. Tomrrow I will check how much work requires roughly to build up again the DB to make functional at least the F-14. How important for you the F-14 pit? I’m asking because of the time factor and also can be a factor that during the redone process I may can make mistakes again. Disable the pits as long as somebody won’t help me is very easy, we simply do not use the cockpit’s dat files. I know, it is very painful lose these pits after I have posted screenshots but I cannot fix the issues without help…