Israeli Theater for BMS 4.33 v1.0
-
My modded install (ITO and Balkans) just started crashing every time I click on Setup. My vanilla install (no mods) works though… strange. It started acting up after I chose pilot model and knee boards in ITO.
-
My modded install (ITO and Balkans) just started crashing every time I click on Setup. My vanilla install (no mods) works though… strange. It started acting up after I chose pilot model and knee boards in ITO.
Do you mean the setup inside BMS? And can you switch theaters and check if it happens in KTO (in the modified install)?
Did you notice if the path to the BMS EXE at top of the ITO config was pointing to the right install? -
Do you mean the setup inside BMS? And can you switch theaters and check if it happens in KTO (in the modified install)?
Did you notice if the path to the BMS EXE at top of the ITO config was pointing to the right install?Yes to all. Setup inside BMS. All theaters. The pilot model and kneedboard mods worked so I’m assuming it was pointing to the correct install. I have another unmodded install (only KTO) which still works fine.
-
Post crashlog if you have it please.
-
-
Thanks for your excelent Work!!
-
Guys excelent work , but why Egypt F-16 have only 2 AIM-7 ? I thought F-16 can take 4 of them on inner pilons.
-
Guys excelent work , but why Egypt F-16 have only 2 AIM-7 ? I thought F-16 can take 4 of them on inner pilons.
In fact on the F-16s that carry it the AIM-7 it can only mounted on stations 3 and 7.
http://www.f-16.net/f-16_armament_article10.html -
You are right , i was confused i read somewhere some times ago where they mention that can take 4 of them and on 4,32 they have 4.
I have other question how i install pilot body for egypt block 40 which lod number i have to replace ?
-
I have other question how i install pilot body for egypt block 40 which lod number i have to replace ?
There is no “simple” answer, because The pilot model in ITO is applied differently compared to what is described in the pilot model thread, in order to make it configurable via the config editor (+Texman plugin) in a clean fashion without hacking things manually in LE. If you’re familiar with LE, what you should do is extract only the pilot part of the model from the original download (IIRC it was distributed with cockpit around it to replace completely one of the cockpit parents) and add it - not replace - to the model in parent 3091, which is the HUD glass of the EAF block 40.
In the future we may extend the config option to include EAF block 40 as well.
BTW it works already on the other EAF blocks. -
Thanks for this release. My fav is the Block 30 IAF with the new model edits. Took me a dogfight to discover one of it.
Cheers
-
Thanks for this release. My fav is the Block 30 IAF with the new model edits. Took me a dogfight to discover one of it.
That’s our squadron’s go-to jet as well
-
Post crashlog if you have it please.
================================== CRASHLOG =====================================
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
0000000016EEA840 <unknown>Exception handler called in UnhandledExceptionHandler.
Write to location 0000000016eea840 caused an access violation.
Bytes at CS:RIP: ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??Registers:
RAX=0x0000000016eea840 RBX=0x0000000022537780 RCX=0x000000006bb62020 RDX=0x0000000000000000
RSI=0x00000000244eb0a0 RDI=0x00000000001efba0 RBP=0x0000000000000000 RSP=0x000000003bcefd98
RIP=0x0000000016eea840 FLG=0x0000000000010246
R8=0x0000000000000000 R9=0x0000000000000000 R10=0x0000000000000000 R11=0x0000000000000202
R12=0x0000000000000000 R13=0x0000000000000000 R14=0x0000000000000000 R15=0x0000000000000000
CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002BCall Stack:
Top of Stack:
0x000000003BCEFD98: 0000000004832A3C 0000000022537780 000007FEEFBE1D38 000000006BB62028 <*……wS"…8…( .k…
0x000000003BCEFDB8: 000000006BB62028 0000000000000000 0000000000000000 0000000000000001 ( .k…
0x000000003BCEFDD8: 0000000000000000 FFFFFFFFFFFFFFFE 0000000079437450 0000000079437450 …PtCy…PtCy…
0x000000003BCEFDF8: 0000000004833AF0 0000000022537780 0000000000000000 000000006BB62020 .:…wS"… .k…
0x000000003BCEFE18: 000000006BB62020 FFFFFFFFFFFFFFFE 0000000000000000 0000030000000400 .k…
0x000000003BCEFE38: 0000000004A9C874 0000000000000000 00000000048337F9 0000000022537780 t…7…wS"…
0x000000003BCEFE58: 0000000000000000 0000000024C6CDA0 00000000048337F0 00000000048337F0 …$…7…7…
0x000000003BCEFE78: 00000000044B526D 0000000022537780 0000000022537780 0000000024C6CDA0 mRK…wS"…wS"…$…
0x000000003BCEFE98: 00000000048337F0 0000000000000000 000000003BCEEF30 000000003BCEEF30 .7…0…;…0…;…
0x000000003BCEFEB8: 0000000000000000 0000000024C6CDA0 0000000004833813 0000000000000000 …$…8…
0x000000003BCEFED8: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 …
0x000000003BCEFEF8: 0000000004AA0F37 0000000000000000 0000000000000000 0000000000000000 7…
0x000000003BCEFF18: 0000000000000000 0000000000000000 0000000004AA10DE 0000000024C6CDA0 …$…
0x000000003BCEFF38: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 …
0x000000003BCEFF58: 00000000772E5A4D 0000000000000000 0000000000000000 0000000000000000 MZ.w…
0x000000003BCEFF78: 0000000000000000 0000000000000000 000000007741B831 0000000000000000 …1.Aw…
0x000000003BCEFF98: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 …
0x000000003BCEFFB8: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 …
0x000000003BCEFFD8: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 …
0x000000003BCEFFF8: 0000000000000000 …================================================================================
Object at RCX(000000006BB62020)================================================================================
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\Bin\x64\Falcon BMS.exe’, run by TOTO.
Error occurred at 21:04:00 on 2015-11-04.
Version: Falcon BMS 4.33.0 (x64) 14753
Not in game
Theater terrain path: ‘C:\Falcon BMS 4.33\Data\Terrdata\korea’
Operating System: Windows 7 (6.1.7601) Platform 2 Service Pack 1.
Computer Name: TOTO-PC Domain: WORKGROUP.
4 logical processor(s), type 8664.
CPU: Intel Core i5-3570K CPU @ 3.40GHz. GenuineIntel. Stepping: 9 Model: A Family: 6.
GPU 0: NVIDIA GeForce GTX 560 Ti . Vendor: 4318. Device: 4608. SubSys: 595924066. Revision: 161.
55% memory in use:
8156 MB physical memory
3618 MB physical memory free
16311 MB paging file
9469 MB paging file free
8388608 MB user address space
8385572 MB user address space freeModule List:
C:\Program Files (x86)\NaturalPoint\TrackIR5\NPClient64.dll, loaded at 0x00000000021d0000 - 13824 bytes - TimeDateStamp 0x 511085e3 - File date is 14:09:08 on 2013-02-04
C:\Falcon BMS 4.33\Bin\x64\Falcon BMS.exe, loaded at 0x0000000004470000 - 9171968 bytes - TimeDateStamp 0x 562b288d - File date is 20:43:28 on 2015-10-23
C:\Falcon BMS 4.33\Bin\x64\dbghelp.dll, loaded at 0x0000000056320000 - 1558912 bytes - TimeDateStamp 0x 4b673670 - File date is 00:33:04 on 2010-03-03
C:\Windows\system32\USER32.dll, loaded at 0x00000000771d0000 - 1008128 bytes - TimeDateStamp 0x 4ce7c9f1 - File date is 17:24:10 on 2010-11-20
C:\Windows\system32\kernel32.dll, loaded at 0x00000000772d0000 - 1164800 bytes - TimeDateStamp 0x 560a0093 - File date is 17:10:54 on 2015-09-28
C:\Windows\SYSTEM32\ntdll.dll, loaded at 0x00000000773f0000 - 1730496 bytes - TimeDateStamp 0x 560a0083 - File date is 17:13:52 on 2015-09-28
C:\Windows\system32\PSAPI.DLL, loaded at 0x00000000775b0000 - 9216 bytes - TimeDateStamp 0x 4a5bc29d - File date is 15:41:54 on 2009-07-13Environment Variables:
2: <allusersprofile=c:\programdata>3: <appdata=c:\users\toto\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=toto-pc>8: <comspec=c:\windows\system32\cmd.exe>9: <eicddrive=f:>10: <fp_no_host_check=no>11: <homedrive=c:>12: <homepath=\users\toto>13: <localappdata=c:\users\toto\appdata\local>14: <logonserver=\toto-pc>15: <number_of_processors=4>16: <os=windows_nt>17: <path=c:\programdata\oracle\java\javapath;c:\program files=“” (x86)\nvidia=“” corporation\physx\common;c:\program=“” files\common=“” files\microsoft=“” shared\windows=“” live;c:\program=“” (x86)\common=“” live;c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\windowspowershell\v1.0;c:\program=“” (x86)\windows=“” live\shared;c:\program=“” (x86)\quicktime\qtsystem=“”>18: <pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc>19: <processor_architecture=amd64>20: <processor_identifier=intel64 6=“” 58=“” family=“” model=“” stepping=“” 9,=“” genuineintel=“”>21: <processor_level=6>22: <processor_revision=3a09>23: <programdata=c:\programdata>24: <programfiles=c:\program files=“”>25: <programfiles(x86)=c:\program files=“” (x86)=“”>26: <programw6432=c:\program files=“”>27: <psmodulepath=c:\windows\system32\windowspowershell\v1.0\modules>28: <public=c:\users\public>29: <sessionname=console>30: <systemdrive=c:>31: <systemroot=c:\windows>32: <tacview_export_path=c:\users\toto\docume~1\tacview>33: <temp=c:\users\toto\appdata\local\temp>34: <tmp=c:\users\toto\appdata\local\temp>35: <userdomain=toto-pc>36: <username=toto>37: <userprofile=c:\users\toto>38: <windir=c:\windows>39: <windows_tracing_flags=3>40: <windows_tracing_logfile=c:\bvtbin\tests\installpackage\csilogfile.log>41: <__COMPAT_LAYER=ElevateCreateProcess>================================================================================</windows_tracing_logfile=c:\bvtbin\tests\installpackage\csilogfile.log></windows_tracing_flags=3></windir=c:\windows></userprofile=c:\users\toto></username=toto></userdomain=toto-pc></tmp=c:\users\toto\appdata\local\temp></temp=c:\users\toto\appdata\local\temp></tacview_export_path=c:\users\toto\docume~1\tacview></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=3a09></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=4></logonserver=\toto-pc></localappdata=c:\users\toto\appdata\local></homepath=\users\toto></homedrive=c:></fp_no_host_check=no></eicddrive=f:></comspec=c:\windows\system32\cmd.exe></computername=toto-pc></commonprogramw6432=c:\program></commonprogramfiles(x86)=c:\program></commonprogramfiles=c:\program></appdata=c:\users\toto\appdata\roaming></allusersprofile=c:\programdata></unknown>
-
Version: Falcon BMS 4.33.0 (x64) 14753 Not in game Theater terrain path: 'C:\Falcon BMS 4.33\Data\Terrdata\korea'
Are you sure this is ITO related?
-
my IP wont let me download torrents anyone got it up on megaco or somewhere else?
-
Are you sure this is ITO related?
No, I’m not sure. But I didn’t have any trouble until I turned on pilot model in ITO. After that all my theaters were FUBAR’d on setup.
-
Maybe I’m the only one, maybe it is my system, but in comparison to the standard installation, I had many issues (installation took a lot of time only to get to the main screens, automatic desinstallation is not working, I have to do it manually, activating the pilot model is creating a crash, during a campaign 1st or 3rd I had a lot of errors/crashes with the message that F4 BMS stopped to worked etc). Sorry but I uninstalled and I wait for the next version.
Edit Reported with latest Nvidia drivers
Sagal
[email protected]; Asus: P8Z77VPRO, SLI 2xGTX-670, 3xVG278H, Xonar Phoebus; G.Skill 16GB; Seasonic X-760W; Noctua NH-U12P SE2; Crucial m4 SSD 256GB; WD Caviar Black 2TB; CM Storm Trooper; TrackIR 5; Logitech: z906, Momo FF; CH: Fighterstick, proPedal, proThrottle; Obutto R3volution; Windows10 Pro 64b -
ITO has only two campaigns… so no 3rd…
Regardless,
assuming you don’t turn on the pilot model in the config (a feature which we will check again).
do instability issues still occur? -
Maybe I’m the only one, maybe it is my system, but in comparison to the standard installation, I had many issues (installation took a lot of time only to get to the main screens, automatic desinstallation is not working, I have to do it manually, activating the pilot model is creating a crash, during a campaign 1st or 3rd I had a lot of errors/crashes with the message that F4 BMS stopped to worked etc). Sorry but I uninstalled and I wait for the next version.
Let’s break it down…
1. It’s normal for the installer to take some time until the main screen shows up since it loads the entire 1.2 GB file first to verify its integrity (depends mostly on HD speed)
2. Automatic uninstaller not working generally means the theater didn’t install completely. What sort of message did you get when you tried to uninstall? dId you try to delete files using another way before you started the uninstaller?
3. The crashing setup screen is being investigated. This pilot model patch only modifies one model in ITO’s 3DDB (koreaobj.lod), so crashing the setup screen seems unrelated, and we didn’t encounter it in beta testing - however we’re re checking it anyway. Post crashlogs please
4. Again post crashlogs from the flights. This could be related to 1 (incomplete install)What are your system specs?
-
No, I’m not sure. But I didn’t have any trouble until I turned on pilot model in ITO. After that all my theaters were FUBAR’d on setup.
OK as we are unable to reproduce it on several different systems (also with the Balkans installed), and the crashlog doesn’t tell much, may I suggest this:
1. Make a clean BMS 4.33 install and check the Setup screen
2. Install ITO and recheck.
3. Activate ITO’s pilot model and recheck.
4. Make any other configuration changes (e.g in Setup, BMS config) and recheck.Again, It would be unlikely that the pilot model option has something to do with crashing the setup screen, and my feeling is that it could be related somehow to local hardware which is read when the setup screen is loaded. But we’ll be smarter after the above.