IKAROS Theater v4.1.0
-
Real aircraft does have DED… For now in the sim you can only see the ded in the HUD display as there isnt any AUP cockpit unfortunatelly you can find the Laser settings in the “list” pages of the DED.
First of all, i 'd like to say thank you Manos for your immediate response to my question. I followed your advice and used the keyboard Shift+H keystroke to make the DED appear on the HUD and then the numpad keys to implement its various functions. This way I was able to use the GBUs properly. I wish one day someone would come up with a functional AUP cockpit for the F-4, but either way your solution also works just fine. Ευχαριστώ φιλε. να 'σαι καλά.
-
So, I have a question regarding the skins of the M2000 EGM/BGM and M2000-5 of the HAF in the Ikarus theater. I used these aircraft on several TEs that i have created (nothing much, just simple engagements) and I cannot get them to appear in HAF skins; they always appear in French Airforce skins, even though I use the Change skin button on the loadout page when loading the aircraft with weapons. I have read in the camo.cfg file that all I have to do is change the number 0 ( i.e 1 331 0) for the actual number of the HAF skinsets , which I can get from LOD editor, in order to get these skinsets to be applied to the corresponding aircraft in the theater. I also downloaded LOD editor and tried to use it but I came up with nothing, since I don’t want to do anything to screw up my database. So I just “opened” the aircraft skins using the skinset viewer and that’s about it. My question is how do I find which number corresponds to the HAF skinset for the two versions of M2000 in the HAF, using LOD editor? I understand that it is probably an extremely dumb question for someone who has used LOD editor before, but for someone who runs LOD editor for the first time it is a daunting task, since any mistake could screw up the entire database. I also watched a couple of videos on youtube about LOD editor, but they were mostly about installing new skins and couldn’t find anything helpful (or maybe it was there and I missed it). So if someone could help by either explaining how I could find out the correct skinset numbers with LOD editor or by simply telling me what these numbers are, I would really appreciate it. Thanks, in advance to anyone who may try to help me. Also, if my understanding of the procedure for setting the proper skinsets in camo.cfg is in any way mistaken please do correct me.
-
Hi m8, help incoming!
What you need to do IS:
- Create and save the mission, then exit BMS.
- Open Mission Commander, find and open the mission file.
- Go to 3rd tab “Units” and press the 3rd button “Squadrons”.
- In the (aircraft type) “Name” find the squadron you desire and double click on it, another window will open.
- In the “Squadron Name” manually write the number of the real squadron you desire. E.g. for HAF Mirages are the 331 (using the -5 model EGM/BGM) and 332 (for the older variant). Note the “Default Skin” etc below values changing just on the right to reflect the camo.cfg settings. You can cross-check skin & aft model through the two buttons bellow.
- If you desire, you can also change the “Squadron Patch” on the left, use the arrows to find the appropriate real patches (for M2K’s are the #1 & #2).
- Hit “Apply” on the bottom right, that window will close and return to previous.
- Hit “Save” on top right to save the mission with the new assigned skinsets setting.
- Exit MC and go fly.
Extra info about LE, on how to view skinsets a model is wearing: (this is informational, is not required for Icarus Theater since all the planes in interest are already predefined in the camo.cfg file, on the bottom of it you can read some more info about the assigned squadrons/countries/versions etc).
- Open LE, find a plane model and hit 3-D Viewer.
- When viewing the plane on the new window, click keyboard Space, a smaller window will appear.
- Click to expand “Display”
- On the “Texture Sets” write the number of skinsets the model uses. (You can check how many sets the model has in “Normal” > “Texture Sets”).
- On the “Use Set” bellow write or play with the arrows to view each skinset on the model.
- Esc to return back anytime.
Remember that numbering starts from 0, so 1st set is 0, 2nd is 1, etc etc.
-
Ok, first of all Raptor thanks for the help; it was really something that I could never have come up with by myself. So, this is what happened when I followed your instructions and used Mission Commander. I did exactly like you said and the skins didn’t change at first. BUT when I used the “Change Skin " button on the loadout page the skin changed to the correct one in both the loadout page and in the 3D word while flying. So I am assuming that your solution requires that I edit each TE with Mission Commander first and then change the skin in the loadout page, which is quite easy and simple actually.
However I am confused about something that I read in the camo.cfg file in the Ikaros Theater, where it says the following:
_” Camouflage override feature. Now is possible to override default texture set computation and specify exact texture set for sqadron via txt cfg file called camo.cfg in campaingn/save folder (each theter can have its own)Format of camo.cfg:
First line is number of specified sqadrons (max 256). Add 1 on the total for each line you write below it.
Then each sqaudron is defined on 1 line by 3 numbers.
First number is Team ID. For Ikaros Theater 1 is Greece, 2 is Turkey, etc. Check Mission Commander for the rest numbers / countries ID’s.
Second number is Squadron Name. This must be a number, most likely the real Squadron number.
Third number is the desired texture Skin Set for the Squadron. Check the corresponding 3D model on LodEditor to determine and arrange the Skin Sets as appropriate.
Note: Skin Sets is counted from 0."_The way I understood all that was that if I changed the skinset number for these aircraft in the camo.cfg file from 0 (default value) to 5 (which seems to be the correct skinset from MC) I would get the correct skins in the game for all TEs and campaigns regardless of any additional processing with MC or any other software. This apparently has not been the case, so was I wrong in my original understanding of the quote in camo.cfg, and if yes, what does that quote really mean ? Anyway, you already provided me with a more that adequate solution to my problem which seems to be working perfectly, so my interest in this is now simply out of curiosity. Anyway, once again thank you for your answer and keep up the great work with this amazing theater that has so much more to offer ( I would really love to see some HAF A-7s someday in the future and I can only hope for a cockpit for the A-7 too :D, but I guess the devs know best and I have absolute confidence in them).
-
This’s my crash log. the TE editor has the same problem with the campaign when recon souda AIRBASE. My PC config: CPU: Intel i5-4590 3.30GHZ RAM:4G Graphic card:NVDIA GTX750ti OS:WIN7 64BIT…. Does it matter with my PC performance? Thanks!
I encountered exactly the same crash log !
28 Nt from Nea Anchialos in approach, after 1 hour of flight in Campain mode day 1. (Take off 10h03, 335 Sqn)
I plan to reinstall Ikaros just to see.
What I can say : my first flight in Ikaros was TE Battle for Karpathos from Hoover and I forgot to switch in Operational DB,so it ran very well during one hour and finally crash.But it’s understable in that case! -
No need to reinstall.
sent from my mi5 using Tapatalk
-
I just tried now 2 TE in BFK. Before the first (Tasmo 5h28 ) I deleted dx9display.dsp and unchecked the External Display (both),I was shooted down near the target East of Creta.Exit the mission,debrief ok!
For the second TE Tasmo 5h18,I checked again External Display (both), perform the mission,come back by the south of Creta near Chania,20Nt far of Souda and new BMS crash
I provide the crash Log================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 00000000044F5200 Falcon BMS.exe, InitPolygon()+208 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\polylibdraw.cpp, line 88+16 byte(s) Exception handler called in UnhandledExceptionHandler. Read from location 00000000751ab9e0 caused an access violation. Bytes at CS:RIP: F3 0F 58 14 8A F3 0F 58 74 8A 04 F3 0F 58 7C 8A Registers: RAX=0x00000000095815e8 RBX=0x0000000000000004 RCX=0x000000001c0841b8 RDX=0x0000000004f9b300 RSI=0x000000002713f660 RDI=0x000000002654e350 RBP=0x000000002713cf90 RSP=0x000000002713cbc0 RIP=0x00000000044f5200 FLG=0x0000000000010206 R8=0x000000009f835688 R9=0x0000000000000004 R10=0x0000000000000001 R11=0x000000002713cc20 R12=0x000000005cc2c880 R13=0x000000005cc2c900 R14=0x000000005cc2c8d8 R15=0x000000002713d0b0 CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002B Call Stack: 0033:00000000044F5200 Falcon BMS.exe, InitPolygon()+208 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\polylibdraw.cpp, line 88+16 byte(s), Parameters(0x000000002654E350 0x0000000047E51224 0x00000000024576C0 0x00000000044FEC44) 0033:00000000044F78F0 Falcon BMS.exe, DrawPolyATL()+128 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\polylibdraw.cpp, line 798, Parameters(0x000000009F834FF0 0x000000002713F660 0x000000002654D5E0 0x0000000000000001) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x000000002654D540 0x000000002713F660 0x000000002654EEE0 0x0000000000000001) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x000000002654EDF0 0x000000002713F660 0x0000000084FD7670 0x0000000000000001) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x0000000084FD75D0 0x000000002713F660 0x0000000084FD70D0 0x0000000000000001) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x0000000084FD7030 0x000000002713F660 0x0000000084FD8840 0x0000000000000000) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x0000000084FD88E0 0x000000003F7CC06A 0x000000002713F660 0x0000000004F981C0) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x000000004327CB10 0x000000002713CF90 0x0000000042888B28 0x0000000042888B28) 0033:00000000044FA04C Falcon BMS.exe, BSubTree::Draw()+460 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 784, Parameters(0x000000003F530410 0x000000003F7CC0E0 0x0000000000000000 0x00000000C000003C) 0033:00000000044FA22C Falcon BMS.exe, BSubTree::DrawFromDerived()+444 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 811, Parameters(0x000000003F738280 0x0000000080000000 0x000000003F7CC06A 0x000000003F7CC06A) 0033:00000000044FA2BE Falcon BMS.exe, BRoot::Draw()+126 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\bspnodes.cpp, line 835, Parameters(0x00000000FFFFFFFF 0x0000000000000000 0x000000002713CF90 0x0000000004F981C0) 0033:00000000044FD3C4 Falcon BMS.exe, StateStackClass::pvtDrawObject()+1812 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\bsplib\statestack.cpp, line 289+73 byte(s), Parameters(0x0000000024986BF8 0x0000000000000000 0x0000000000006720 0x000000005CC2C888) 0033:0000000004516246 Falcon BMS.exe, DrawableBSP::Draw()+3142 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\objects\drawbsp.cpp, line 751, Parameters(0x0000000047ADC189 0x00000000401D5E90 0x0000000049A581FA 0x000000002713F660) 0033:0000000004518193 Falcon BMS.exe, DrawableBuilding::Draw()+147 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\objects\drawbldg.cpp, line 115, Parameters(0x000000005CA94AB8 0x000000002713F709 0x0000000000000005 0x00000000401D5E90) 0033:0000000004A46FEA Falcon BMS.exe, ObjectDisplayList::DrawBeyond()+298 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\objects\objlist.cpp, line 647, Parameters(0x000000005CA94AB8 0x000000002448B560 0x000000005CA94AE0 0x000000005CA94A90) 0033:0000000004A4A0C9 Falcon BMS.exe, DrawablePlatform::Draw()+425 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\objects\drawplat.cpp, line 153, Parameters(0x000000002448B560 0x000000002713F879 0x0000000000000018 0x00000000401D5E90) 0033:0000000004A46FEA Falcon BMS.exe, ObjectDisplayList::DrawBeyond()+298 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\objects\objlist.cpp, line 647, Parameters(0x000000002448B560 0x000000002493F7E0 0x00000000401D5F18 0x00000000401D5E90) 0033:00000000045565C8 Falcon BMS.exe, RenderOTW::DrawGroundObjects()+472 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\renderer\otw.cpp, line 1243, Parameters(0x00000000401D5E90 0x00000000401D5E90 0x0000000000000000 0x000000007FFFFF01) 0033:0000000004556156 Falcon BMS.exe, RenderOTW::DrawSceneFromCustomPosition()+1974 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\renderer\otw.cpp, line 742, Parameters(0x00000000401D5E90 0x00000000E3755F00 0x000000002713FBB0 0x000000000C788EF0) 0033:00000000045558D6 Falcon BMS.exe, RenderOTW::DrawSceneFromViewpoint()+486 byte(s), e:\wip\bms\svn\source\rel-4.33\graphics\renderer\otw.cpp, line 582+61 byte(s), Parameters(0x000000000C77EA20 0x00000000401D5E90 0x000000003F7CC06A 0x0000000000000000) 0033:000000000477BE59 Falcon BMS.exe, OTWDriverClass::RenderScene()+2025 byte(s), e:\wip\bms\svn\source\rel-4.33\sim\otwdrive\otwloop.cpp, line 2801, Parameters(0x000000000C77EA20 0x0000000000000000 0x0000000041D84CDB 0x0000000012501A90) 0033:000000000477B65E Falcon BMS.exe, OTWDriverClass::RenderFrame()+158 byte(s), e:\wip\bms\svn\source\rel-4.33\sim\otwdrive\otwloop.cpp, line 2565, Parameters(0x0000000047AD5C01 0x0000000000000000 0x0000000004C84AC8 0x0000000004BB3608) 0033:0000000004777D56 Falcon BMS.exe, OTWDriverClass::Cycle()+1846 byte(s), e:\wip\bms\svn\source\rel-4.33\sim\otwdrive\otwloop.cpp, line 560, Parameters(0x00000000B28FCA5F 0x00000000014913C7 0x000000000000001B 0x00000000014913C7) 0033:0000000004848224 Falcon BMS.exe, SimulationLoopControl::Loop()+1844 byte(s), e:\wip\bms\svn\source\rel-4.33\sim\simloop\simloop.cpp, line 572, Parameters(0x0000000000000000 0x0000000000000000 0x0000000024148EF0 0x0000000004847AF0) 0033:00000000044CAF6D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), e:\wip\bms\svn\source\rel-4.33\falclib\ehandler.cpp, line 1572+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AE4CE7 Falcon BMS.exe, _callthreadstartex()+23 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 376+13 byte(s), Parameters(0x0000000024148EF0 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AE4E8E Falcon BMS.exe, _threadstartex()+258 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 354+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000076D959CD kernel32.dll, BaseThreadInitThunk()+13 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000076FCA561 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) Top of Stack: 0x000000002713CBC0: 8000000080000000 8000000080000000 000000003E89143C 0000000000000000 ................<..>............ 0x000000002713CBE0: 000000002713F660 00000000044F78F0 000000002654E350 0000000047E51224 `..'.....xO.....P.T&....$..G.... 0x000000002713CC00: 00000000024576C0 00000000044FEC44 000000003F91361D 00000000268C2A20 .vE.....D.O......6.?.... *.&.... 0x000000002713CC20: 0000000000000000 000000000001CA24 0000000000000000 0000000000000000 ........$....................... 0x000000002713CC40: 000000000000002C 00000000024576C0 0000000002450340 0000000002457680 ,[email protected]..... 0x000000002713CC60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x000000002713CC80: 0000000000000000 00000000401D601C 0000000000000000 0000000000000000 .........`.@.................... 0x000000002713CCA0: 0000000000000000 00000000044FFDEC 3F7CC06A3F7CC06A 3F7CC06A3F7CC06A ..........O.....j.|?j.|?j.|?j.|? 0x000000002713CCC0: 000000002713F660 0000000004F981C0 000000009F835650 00000000044FA04C `..'............PV......L.O..... 0x000000002713CCE0: 000000009F834FF0 000000002713F660 000000002654D5E0 0000000000000001 .O......`..'......T&............ 0x000000002713CD00: 000000002713F660 00000000044FA04C 000000002654D540 000000002713F660 `..'[email protected]&....`..'.... 0x000000002713CD20: 000000002654EEE0 0000000000000001 000000002713F660 00000000044FA04C ..T&............`..'....L.O..... 0x000000002713CD40: 000000002654EDF0 000000002713F660 0000000084FD7670 0000000000000001 ..T&....`..'....pv.............. 0x000000002713CD60: 000000002713F660 00000000044FA04C 0000000084FD75D0 000000002713F660 `..'....L.O......u......`..'.... 0x000000002713CD80: 0000000084FD70D0 49A581FA00000001 000000002713F660 00000000044FA04C .p.............I`..'....L.O..... 0x000000002713CDA0: 0000000084FD7030 000000002713F660 0000000084FD8840 0000000000000000 0p......`..'....@............... 0x000000002713CDC0: 000000002713F660 00000000044FA04C 0000000084FD88E0 3F7CC06A3F7CC06A `..'....L.O.............j.|?j.|? 0x000000002713CDE0: 000000002713F660 0000000004F981C0 000000002713F660 00000000044FA04C `..'............`..'....L.O..... 0x000000002713CE00: 000000004327CB10 000000002713CF90 3E89A4FF42888B28 3E11B8E442888B28 ..'C.......'....(..B...>(..B...> 0x000000002713CE20: 000000002713F660 00000000044FA22C 000000003F530410 3F7CC06A3F7CC0E0 `..'....,.O.......S?......|?j.|? 0x000000002713CE40: 0000000000000000 00000000C000003C 000000002713F660 00000000044FA2BE ........<.......`..'......O..... 0x000000002713CE60: 000000003F738280 8000000080000000 3F7CC06A3F7CC06A 3F7CC06A3F7CC06A ..s?............j.|?j.|?j.|?j.|? 0x000000002713CE80: 0000000000000000 00000000044FD3C4 00000000FFFFFFFF 0000000000000000 ..........O..................... 0x000000002713CEA0: 000000002713CF90 0000000004F981C0 00000000C6C84800 0000000000000000 ...'.............H.............. 0x000000002713CEC0: 3E89A4FF3FC5EE46 3E11B8E43E11B928 40317956BE0BD62A BD90523DBD905281 F..?...>(..>...>*[email protected]..=R.. 0x000000002713CEE0: 3E22FF12BE6E364D 3F7CC06A3F7CC0E0 0000000000000000 00000000C000003C M6n...">..|?j.|?........<....... 0x000000002713CF00: C7896D46C7D395DA 3E22FF12C58BD122 3F7CC06A3F800000 0000000000000000 ....Fm..".....">...?j.|?........ 0x000000002713CF20: 00000000470CA000 000000002713F550 00000000C0B38200 0000000000000000 ...G....P..'.................... 0x000000002713CF40: 4796D53947D3D738 00000000458BA003 C58BD12247896D46 0000000047D395DA 8..G9..G...E....Fm.G"......G.... 0x000000002713CF60: FFFFFFFFFFFFFFFE 3E89A4FF3FC5EE46 3E11B8E43E11B928 40317956BE0BD62A ........F..?...>(..>...>*...Vy1@ 0x000000002713CF80: BD90523DBD905281 3E22FF12BE6E364D 3F7CC06A3F7CC0E0 0000000000000000 .R..=R..M6n...">..|?j.|?........ 0x000000002713CFA0: 00000000C000003C 00000000401D5E90 0000000000000000 0000000000000000 <........^.@.................... 0x000000002713CFC0: C0B38224379414CD 0000000000000000 C0B38224379414CD 0000000000000000 ...7$..............7$........... 0x000000002713CFE0: 4134B03F345C8836 4134B03F345C8836 412824B6F88D05E7 4134B03F345C8836 6.\4?.4A6.\4?.4A.....$(A6.\4?.4A 0x000000002713D000: 000000003F800000 0000000000000000 00000000C6B991E2 0000000000000000 ...?............................ 0x000000002713D020: 0000000000000005 00000000401D5E90 000000002713D140 0000000004516246 .........^.@....@..'....FbQ..... 0x000000002713D040: 0000000024986BF8 0000000000000000 0000000000006720 000000005CC2C888 .k.$............ g.........\.... 0x000000002713D060: 000000002713D0B0 412824B63F800000 4134B03F3F800000 C0B38224379414CD ...'.......?.$(A...??.4A...7$... 0x000000002713D080: 00000000476A6000 000000002713F660 C0B3822437941400 0000000000000000 .`jG....`..'.......7$........... 0x000000002713D0A0: 47896D4647D395DA 00000000458BD122 47896D4647D395DA 4134B03F458BD122 ...GFm.G"..E.......GFm.G"..E?.4A 0x000000002713D0C0: 412824B6F88D05E7 4134B03F458BD122 C0B38224379414CD 0000000000000014 .....$(A"..E?.4A...7$........... 0x000000002713D0E0: 00000000C6C5B956 412824B6F88D05E7 4134B03F345C8836 C0B38224379414CD V............$(A6.\4?.4A...7$... 0x000000002713D100: 000000002713D210 0000000004516246 0000000024986BF8 0000000000000000 ...'....FbQ......k.$............ 0x000000002713D120: 0000000000006720 00000000B7FC5DE8 000000002713D180 000000003F800000 g.......].........'.......?.... 0x000000002713D140: C0B382243F800000 0000000000000014 B9562CBC476A6000 000000002713F730 ...?$............`jG.,V.0..'.... 0x000000002713D160: 4134B03F345C8800 C0B38224379414CD 47940E0647D4B982 00000000458BD122 ..\4?.4A...7$......G...G"..E.... 0x000000002713D180: 47940E0647D4B982 00000000458BD122 000000003FC4632F 00000000458BD122 ...G...G"..E..../c.?...."..E.... 0x000000002713D1A0: C0B38224379414CD 0000000000000014 0000000000000000 412824B6F88D05E7 ...7$........................$(A 0x000000002713D1C0: 4134B03F345C8836 C0B38224379414CD 0000000000000000 0000000000000000 6.\4?.4A...7$................... 0x000000002713D1E0: 000000003F800000 0000000000000000 000000003B7CCAC5 0000000000000000 ...?..............|;............ 0x000000002713D200: 0000000000000005 00000000401D5E90 000000002713D320 0000000004516246 .........^.@.... ..'....FbQ..... 0x000000002713D220: 0000000024986B90 0000000000000000 0000000000000840 0000000024A9B198 .k.$............@..........$.... 0x000000002713D240: 000000002713D290 000000003F800000 000000003F800000 412824B4ED0A55C2 ...'.......?.......?.....U...$(A 0x000000002713D260: 4134B04F49127C00 000000002713F8C0 49622ABA4848D400 0000000045A1D6F6 .|.IO.4A...'......HH.*bI...E.... 0x000000002713D280: 3F563938BDAD3DB5 000000003D9F88F8 3F563938BDAD3DB5 000000003D9F88F8 .=..89V?...=.....=..89V?...=.... 0x000000002713D2A0: C0B43DDEC4DBF44B 000000003D9F88F8 0000000000000000 0000000000000000 K....=.....=.................... 0x000000002713D2C0: 4134D717A10EBD60 0000000000000000 0000000000000000 0000000000000000 `.....4A........................ 0x000000002713D2E0: 493017BF4841A72B 000F00004547E9B2 3FC4632F00E40000 3FB22D8C4547E9B2 +.AH..0I..GE......../c.?..GE.-.? 0x000000002713D300: C0C5DF5EFFF50FC5 0000000000000018 0000000000000000 41289FC8C6940ED6 ....^.........................(A 0x000000002713D320: 4137F84753D9D290 C0C5DF5EFFF50FC5 0000000000000000 0000000000000000 ...SG.7A....^................... 0x000000002713D340: 0000000000000000 0000000000000000 000000009F254450 0000000000000000 ................PD%............. 0x000000002713D360: 0000000000000000 0000000000000000 0000000000000000 0000000000207E80 .........................~ ..... 0x000000002713D380: 0000000000000000 00000000002080E0 00000000002097A0 0000000000000000 .......... ....... ............. 0x000000002713D3A0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ While Drawing LOD 10124 (this may only be a coincidence if the call stack is not the LOD drawing code) ================================================================================ Object at RCX(000000001C0841B8) Data inaccessible ================================================================================ Compiler Options: _MSC_VER=1800 WINVER=0x502 _WIN32_WINNT=0x502 _WIN32_WINDOWS=0x502 NTDDI_VERSION=0x5020000 _WIN32_IE=0x602 ANSI _M_AMD64 _AMD64_ _WIN64 Release* System Information: 'C:\Falcon BMS 4.33 U1\Bin\x64\Falcon BMS.exe', run by Utilisateur. Error occurred at 14:57:22 on 2017-07-08. Version: Falcon BMS 4.33.3 (x64) 16068 Game is Tactical Engagement type Local Theater terrain path: 'C:\Falcon BMS 4.33 U1\Data\Add-On Ikaros\Terrdata' Operating System: Windows 7 (6.1.7601) Platform 2 Service Pack 1. Computer Name: UTILISATEUR-PC Domain: WORKGROUP. 8 logical processor(s), type 8664. CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz. GenuineIntel. Stepping: 7 Model: A Family: 6. GPU 0: AMD Radeon HD 6900 Series. Vendor: 4098\. Device: 26393\. SubSys: 62787651\. Revision: 0. 31% memory in use: 16366 MB physical memory 11262 MB physical memory free 32729 MB paging file 25566 MB paging file free 8388608 MB user address space 8385452 MB user address space free Module List: C:\Program Files (x86)\NaturalPoint\TrackIR5\NPClient64.dll, loaded at 0x0000000002340000 - 13824 bytes - TimeDateStamp 0x 4d82b6e6 - File date is 18:35:36 on 2011-03-17 C:\Windows\system32\PSAPI.DLL, loaded at 0x00000000040a0000 - 9216 bytes - TimeDateStamp 0x 4a5bc29d - File date is 03:41:54 on 2009-07-14 C:\Falcon BMS 4.33 U1\Bin\x64\Falcon BMS.exe, loaded at 0x0000000004470000 - 9599488 bytes - TimeDateStamp 0x 584da3f6 - File date is 21:07:38 on 2016-12-11 C:\Windows\system32\atiumd6a.dll, loaded at 0x000000006afa0000 - 8893160 bytes - TimeDateStamp 0x 55c02171 - File date is 08:27:56 on 2015-08-04 C:\Falcon BMS 4.33 U1\Bin\x64\dbghelp.dll, loaded at 0x000000006ef40000 - 1558912 bytes - TimeDateStamp 0x 4b673670 - File date is 12:33:04 on 2010-03-03 C:\Windows\system32\kernel32.dll, loaded at 0x0000000076d80000 - 1163264 bytes - TimeDateStamp 0x 5915fe13 - File date is 20:22:34 on 2017-05-12 C:\Windows\system32\USER32.dll, loaded at 0x0000000076ea0000 - 1009152 bytes - TimeDateStamp 0x 5824a140 - File date is 18:32:42 on 2016-11-10 C:\Windows\SYSTEM32\ntdll.dll, loaded at 0x0000000076fa0000 - 1732864 bytes - TimeDateStamp 0x 5915fdce - File date is 20:24:14 on 2017-05-12 Environment Variables: 2: <allusersprofile=c:\programdata> 3: <appdata=c:\users\utilisateur\appdata\roaming> 4: <commonprogramfiles=c:\program files\common="" files=""> 5: <commonprogramfiles(x86)=c:\program files="" (x86)\common=""> 6: <commonprogramw6432=c:\program files\common="" files=""> 7: <computername=utilisateur-pc> 8: <comspec=c:\windows\system32\cmd.exe> 9: <fp_no_host_check=no> 10: <homedrive=c:> 11: <homepath=\users\utilisateur> 12: <localappdata=c:\users\utilisateur\appdata\local> 13: <logonserver=\\utilisateur-pc> 14: <number_of_processors=8> 15: <os=windows_nt> 16: <path=c:\programdata\oracle\java\javapath;c:\program files="" (x86)\pc="" connectivity="" solution\;c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\windowspowershell\v1.0\;c:\program="" (x86)\ati="" technologies\ati.ace\core-static;c:\program="" (x86)\amd\ati.ace\core-static=""> 17: <pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc> 18: <processor_architecture=amd64> 19: <processor_identifier=intel64 6="" 42="" family="" model="" stepping="" 7,="" genuineintel=""> 20: <processor_level=6> 21: <processor_revision=2a07> 22: <programdata=c:\programdata> 23: <programfiles=c:\program files=""> 24: <programfiles(x86)=c:\program files="" (x86)=""> 25: <programw6432=c:\program files=""> 26: <psmodulepath=c:\windows\system32\windowspowershell\v1.0\modules\> 27: <public=c:\users\public> 28: <sessionname=console> 29: <systemdrive=c:> 30: <systemroot=c:\windows> 31: <temp=c:\users\utilis~1\appdata\local\temp> 32: <tmp=c:\users\utilis~1\appdata\local\temp> 33: <userdomain=utilisateur-pc> 34: <username=utilisateur> 35: <userprofile=c:\users\utilisateur> 36: <windir=c:\windows> 37: <windows_tracing_flags=3> 38: <windows_tracing_logfile=c:\bvtbin\tests\installpackage\csilogfile.log> 39: <__COMPAT_LAYER=ElevateCreateProcess> ================================================================================</windows_tracing_logfile=c:\bvtbin\tests\installpackage\csilogfile.log></windows_tracing_flags=3></windir=c:\windows></userprofile=c:\users\utilisateur></username=utilisateur></userdomain=utilisateur-pc></tmp=c:\users\utilis~1\appdata\local\temp></temp=c:\users\utilis~1\appdata\local\temp></systemroot=c:\windows></systemdrive=c:></sessionname=console></public=c:\users\public></psmodulepath=c:\windows\system32\windowspowershell\v1.0\modules\></programw6432=c:\program></programfiles(x86)=c:\program></programfiles=c:\program></programdata=c:\programdata></processor_revision=2a07></processor_level=6></processor_identifier=intel64></processor_architecture=amd64></pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc></path=c:\programdata\oracle\java\javapath;c:\program></os=windows_nt></number_of_processors=8></logonserver=\\utilisateur-pc></localappdata=c:\users\utilisateur\appdata\local></homepath=\users\utilisateur></homedrive=c:></fp_no_host_check=no></comspec=c:\windows\system32\cmd.exe></computername=utilisateur-pc></commonprogramw6432=c:\program></commonprogramfiles(x86)=c:\program></commonprogramfiles=c:\program></appdata=c:\users\utilisateur\appdata\roaming></allusersprofile=c:\programdata>
-
We have pinpointed a problem that causes random ctd. It has been fixed
-
We have pinpointed a problem that causes random ctd. It has been fixed
The professionals at work
WONDERFULL !!! -
We have pinpointed a problem that causes random ctd. It has been fixed
can we expect this update relatively soon? because i’m working on missions for a LAN-meeting for my squadron and it makes it really annoying to save after every single step just to pre-empt this random CTD, it’s practicly unworkable for me in terms of frustration levels. i want to use this theater as it offers exactly what i need and it’s something else than Balkans, ITO or KTO. but i may have to switch theaters just for my own sanity.
hoping for some good news.
-
I don’t know yet. Currently we are adding new airbases and we are fixing bugs.
-
I have just to report a curious bug that happened while installing this amazing theatre (thanks for this unique installation routine! - I need to drink an Ouzo right now. At the first time I didn’t recognized that I installed the Add-On to the default directory (yeah, right - it was my own fault (have another drink :drink: )).
But at the second time the program installed all the directories and files to the …\Data\Add-On Ikaros*Ikaros Settings*-Folder (Win7 64, Admin). So BMS crashed while changing the theatre; equally with the modified path in the theater.lst-file.
Looking to the directories of the first run, everything was set correct. Checking the routine a third time, the Installer now chose the correct BMS folder but just added two Ikaros Settings-folders (…\Data\Add-On Ikaros*Ikaros Settings\Ikaros Settings*).
Moving the files to the heading directory manually and everything works fine. Just a very mystique independent existence of the Installer… -
@ Chasseur
Yes, I saw this happening in another installation. I’ll consider this for the next update’s installer script.
Until then, please bear in mind that the correct Root-path for all IKAROS files & folders is ALWAYS …:\Falcon BMS 4.33 U1\Data\Add-On Ikaros\
Thank you!
-
I encountered exactly the same crash log !
28 Nt from Nea Anchialos in approach, after 1 hour of flight in Campain mode day 1. (Take off 10h03, 335 Sqn)
I plan to reinstall Ikaros just to see.
What I can say : my first flight in Ikaros was TE Battle for Karpathos from Hoover and I forgot to switch in Operational DB,so it ran very well during one hour and finally crash.But it’s understable in that case!The same as you : after 1 hour of flight in campaign day 1, 28 Nt from Nea Anchialos in approach. But after that , i never encounter the crash when approach Nea Anchialos in the following campaign
-
I found a small spelling mistake when exiting a mission: “leaving aircraft –- STANBY” instead of “STANDBY”.
All the best, Uwe
-
-
I can not add the package of F-16C-50-347 or F-16C-52-337 in the Campaign Exercise Poseidon.
Available Aircrafts I can only add in the Blue Force are F-16AM , Tornado IDS , F-16C BLK 52 HAF and EMB-145H AWAC :
why is this?
-
Guys, is it just me, or is F-16C 340sq and 340sq +CFT missing from IKAROS teplanes.lst? I can see the jets in TacRef and can add squadrons via Mission Commander, however, I cannot add flights/packages with that jet in BMS Mission Builder. Do you have the data so I can add it to TE planes, or tell me where to look to find it please?
EDIT: 337sq C and C +CFT is also missing.
EDIT2: It looks like the majority of the C models are missing. I can only select the D models, with or without CFTs. Is there a DB error or is it WIP? I want to fly 340sq F-16C +CFT out of Souda but I can’t Looks like JOKER above has the same issue, but he’s using the campaign DB, whereas I’m using the TE DB via the Ikaros configThanks!
-
They are under F-16C BLK52+
-
They are under F-16C BLK52+
Is it possible to have the names updated for the next release? Or are they named as such intentionally?