4.33 Issues (Known or not)
-
Dunno if it has been posted - I do not see it for 4.33 U1: The waypoint 2 bug is still there in TEs:
When you plot a flight, there is always an unnecessary waypoint offset until the flight heads to its destined target/mission area:This also leads to AI flying offset before heading towards enemy positions e.g.
I recall this was not the case in 4.32 and older Falcon versions.
Correct me if I’m wrong.you ar wrong this is on purpose.
DeeJay will explain but this is like in real life
-
It should register hits after the target is destroyed as being ‘damaged’. Shouldnt be misses.
Didn’t know that, thanks!
-
I´m having problems using CBUs. I created a simple TE where i attack a AAA batallion in bad wheather, my loadout was 6x Mk-20 and some dumb bombs. The thing is that when i dropped my Mk-20 i saw they exploded right on top of the enemy vehicles but i didnt destroy anyone; i repeated my attacks with the same results, i saw the cbus exploding on top of the vehicles but i didnt destroy anything. After that i ended the mission and in the after action report it said that all my Mk-20 where misses and i had 0 AG kills.
I tried raising and lowering the burst altitude but the same keeps happening, i tried using other type of cbu as cbu 87 and 97 but i only get misses. I found it weird because i clearly see the cbu submunitions exploding where the enemy vehicle is but i dont get anything and only get misses, not even a damaged vehicle, and 0 AG kills. I tried using Mk82 free fall bombs but this time i did destroyed the enemy vehicles and damaged others. maybe it have something to do with the wind but as i said earlier i saw the cbu submunitions exploding where the enemy is but i cant even destroy a truck -
How low were you dropping them?
-
I tried dropping them from 500 ft to 2000 or 3000 ft and even higher at 5000 ft but i keep getting the same results. I tried rockets also with the same results; hits right on top where the enemy vehicle is but i only gets misses and no kill not even damaged vehicles
-
Once when I was asking the same the answer I got was: lofting is not vehicles, it’s for a general area or buildings and not for accurate bombing.
Left lofting ever since.
sent from my Xperia Z3 compact via TapaTalk
-
But i wasnt lofting my cbus, i was dropping them from level flight or i a dive in CCIP mode and i watched them explode where the enemy vehicles where. The same happened with rockets
-
Rockets are inaccurate and more against infantry or unarmored vehicle…
Can you try it with CBU’s 105 and CCRP and then tell if they do damage?
-
Rockets are inaccurate and more against infantry or unarmored vehicle…
Can you try it with CBU’s 105 and CCRP and then tell if they do damage?
I will try it and post the results
-
graphical issues …
1. sticking same part of gear
2. hole through viper -
-
I will try it and post the results
Ok, so i did some testing and i think the problem was a low burst altitude for the cbus. I tried dropping them with 500 ft of BA and they did no damage, then i changed it to 2000 ft and they destroyed a lot of vehicles in one pass. So thats it, a low burst altitude maybe caused problems with the submunitions properly deploying and thats why i couldnt kill anything. Also using Mk-20 against K-200 AD is not very effective.
-
@Src:
graphical issues …
1. sticking same part of gear
2. hole through viperKnown issue. Thank you.
-
The other night, I noticed a small LOD-issue with the MK82SE, namely that they appear to have their retarders already deployed while the bombs are still on the wing.
I have smart scaling enabled at 0.2NM, and after closing within that distance or zooming in with mouse wheel / look closer command, it looks okay.
-
The other night, I noticed a small LOD-issue with the MK82SE, namely that they appear to have their retarders already deployed while the bombs are still on the wing.
I have smart scaling enabled at 0.2NM, and after closing within that distance or zooming in with mouse wheel / look closer command, it looks okay.
I saw the same.
Sent from my XT1080 using Tapatalk
-
Small bug I found:
The OSB button that switches “WARM/COOL” on the AIM-9X SMS page
Once you are out of AIM-9X’s, pressing that OSB button will crash the game -
Small bug I found:
The OSB button that switches “WARM/COOL” on the AIM-9X SMS page
Once you are out of AIM-9X’s, pressing that OSB button will crash the gamea CTD is always classified showstopper and prio 1.
thanks for the report
-
Hi, not sure if this is known or not, but I have been trying to use labels on the units and aircrafts (names) and falcon freezes then crashes… CTD. Tried twice.
F4331 KTO 64 bits SP My rig is on the signature, with exception of the GPU which is not working and I am still using the old one Nvidia 9500 GT 1GB ddr3.
I will upload the crashelog.
Regards Metalhead================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in: 000000000485F91A Falcon BMS.exe, C_Fontmgr::_Draw32()+426 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\cfontres.cpp, line 564 Exception handler called in UnhandledExceptionHandler. Write to location 000000002f240000 caused an access violation. Bytes at CS:RIP: 89 28 48 83 C0 04 41 D0 EA 4D 8B 4B 30 FF C2 4D Registers: RAX=0x000000002f240000 RBX=0x000000002f240000 RCX=0x0000000000000004 RDX=0x0000000000000003 RSI=0x000000002f23fff4 RDI=0x000000002f24003c RBP=0x0000000000f0f0f0 RSP=0x00000000291af940 RIP=0x000000000485f91a FLG=0x0000000000010202 R8=0x000000002385a12d R9=0x0000000023816e18 R10=0x0000000000000001 R11=0x00000000232f1b70 R12=0x0000000000000006 R13=0x0000000023773e68 R14=0x0000000000000168 R15=0x000000002385a12c CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002B Call Stack: 0033:000000000485F91A Falcon BMS.exe, C_Fontmgr::_Draw32()+426 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\cfontres.cpp, line 564, Parameters(0x000000002F240000 0x0000000023773E68 0x0000000031983C1D 0x00000000291AFA09) 0033:000000000486D0B0 Falcon BMS.exe, O_Output::Draw()+3104 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\ooutput.cpp, line 720+170 byte(s), Parameters(0x0000000000000000 0x000000002DD97990 0x000000002DADCDCC 0x0000000023773E68) 0033:0000000004A6CC09 Falcon BMS.exe, C_MapIcon::Draw()+1065 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95_ext\cicons.cpp, line 649, Parameters(0x0000000000000000 0x0000000023773E68 0x000000002DADCC38 0x0000000000000000) 0033:0000000004854D9B Falcon BMS.exe, C_Window::DrawWindow()+107 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\cwindow.cpp, line 1135, Parameters(0x0000000023773E68 0x0000000000000000 0x0000000000000000 0x00000000253AA760) 0033:000000000484F06B Falcon BMS.exe, C_Handler::Update()+203 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\chandler.cpp, line 1042, Parameters(0x0000000023773E40 0x0000000023773E40 0x0000000000000000 0x0000000000227FE0) 0033:000000000485063F Falcon BMS.exe, C_Handler::DoOutputLoop()+687 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\chandler.cpp, line 1600, Parameters(0x0000000023773E40 0x0000000000000000 0x0000000025396690 0x0000000004850350) 0033:0000000004850359 Falcon BMS.exe, C_Handler::OutputLoopWrapper()+9 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\chandler.cpp, line 1499, Parameters(0x0000000023773E40 0x0000000023773E40 0x0000000025396690 0x0000000004850350) 0033:00000000044C809D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), d:\wip\bms\svn\source\rel-4.33\falclib\ehandler.cpp, line 1567+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004850373 Falcon BMS.exe, C_Handler::OutputLoop()+19 byte(s), d:\wip\bms\svn\source\rel-4.33\ui95\chandler.cpp, line 1506, Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0AD7 Falcon BMS.exe, _callthreadstartex()+23 byte(s), f:\dd\vctools\crt\crtw32\startup\threadex.c, line 376+13 byte(s), Parameters(0x0000000025396690 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000004AC0C7E 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:0000000076AA59BD kernel32.dll, BaseThreadInitThunk()+13 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) 0033:0000000076CDA2E1 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000) Top of Stack: 0x00000000291AF940: 000000002F22F000 000000002EF40000 FFFFFFFFCE67C3E9 0000000000000007 .."/..............g............. 0x00000000291AF960: 0000000000000007 0000000023773E68 00000000FFFFFFD8 0000000004470000 ........h>w#..............G..... 0x00000000291AF980: 0000000000000000 00000000000002EF 00000000317EFC40 000000000486D0B0 ................@.~1............ 0x00000000291AF9A0: 000000002F240000 0000000023773E68 0000000031983C1D 00000000291AFA09 ..$/....h>w#.....<.1.......).... 0x00000000291AF9C0: 0000000000F0F0F0 00000000FFFFFFFD 00000000000002FA 00000000291AFA18 ...........................).... 0x00000000291AF9E0: 00000000291AFA58 00000000291AF9F0 0000000000000000 000002FF00000001 X..).......).................... 0x00000000291AFA00: 0000000000000006 00000000232F1B70 0000000000000000 000002EF00000000 ........p./#.................... 0x00000000291AFA20: 000003000000000F 0000000004856BF4 0000000023773E40 0000000000000000 .........k......@>w#............ 0x00000000291AFA40: 0000000000000169 0000000023773E68 000000002DADCDCC 000000003168C040 i.......h>w#[email protected].... 0x00000000291AFA60: 0000000031465550 0000000004A6CC09 0000000000000000 000000002DD97990 PUF1.....................y.-.... 0x00000000291AFA80: 000000002DADCDCC 0000000023773E68 0000000023773E40 0000000000000000 ...-....h>w#....@>w#............ 0x00000000291AFAA0: 000000002380D990 0000000004A6FBD1 0000000000000000 000000002DADCDCC ...#.......................-.... 0x00000000291AFAC0: 0000000004B46F18 00000000FFFFFEA0 00000000313DB7B0 000000003182ADA0 .o................=1.......1.... 0x00000000291AFAE0: 000000002D660570 0000000025804A10 0000000000000000 0000000000000000 p.f-.....J.%.................... 0x00000000291AFB00: 0000000000000000 000000003182AE60 000000002DADC9D0 0000000004854D9B ........`..1.......-.....M...... 0x00000000291AFB20: 0000000000000000 0000000023773E68 000000002DADCC38 0000000000000000 ........h>w#....8..-............ 0x00000000291AFB40: 0000000000000000 000000002DBBB490 0000000000000000 000000000484F06B ...........-............k....... 0x00000000291AFB60: 0000000023773E68 0000000000000000 0000000000000000 00000000253AA760 h>w#....................`.:%.... 0x00000000291AFB80: 0000000000000000 000007FEE95E5D04 000000000F513F00 000000000F511AE0 .........]^......?Q.......Q..... 0x00000000291AFBA0: 0000000000000000 0000000000000000 000000000F5047D0 000000000F511B90 .................GP.......Q..... 0x00000000291AFBC0: 000000000F511AE0 0000000000000000 0000000000000000 0000000001000001 ..Q............................. 0x00000000291AFBE0: 000000000F513F00 000007FEE9610619 0000000000000000 0000000000000000 .?Q.......a..................... 0x00000000291AFC00: 0000000000000000 0000000000000000 00000000291AFCF0 0000FFFF00000000 ...................)............ 0x00000000291AFC20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFC40: 0000000000227FE8 0000000000227FE0 0000000000000000 0000000000000000 .."......."..................... 0x00000000291AFC60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFC80: 0000000000000000 00000300000003D4 0000000000000000 00000300000003D4 ................................ 0x00000000291AFCA0: 0000000100000016 0000000000000001 0000000000000000 0000030000000400 ................................ 0x00000000291AFCC0: 0000000100000016 0000000000000001 0000000000000000 0000000000000000 ................................ 0x00000000291AFCE0: 0000000000000000 0000000000000000 0000000000227FE0 000007FEE95F449C .................."......D_..... 0x00000000291AFD00: 0000000100000001 0000000000227FE8 000000000022BC98 0000000000000000 .........."......."............. 0x00000000291AFD20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFD40: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFD60: 0000000000000000 0000000000000000 0000000000000000 000007FEE95C2B61 ........................a+\..... 0x00000000291AFD80: 000000000F5AF2A0 000000000000003E 0000000000000000 000007FEE9622CB4 ..Z.....>................,b..... 0x00000000291AFDA0: 00000000253AA760 000007FEE9621D38 0000000000227FE8 0000000000227FE8 `.:%....8.b......."......."..... 0x00000000291AFDC0: 0000000000227FE0 000000000000003E 0000000000000000 0000000000000000 ..".....>....................... 0x00000000291AFDE0: 0000000000000000 00000000253AA760 0000000000000000 000000000485063F ........`.:%............?....... 0x00000000291AFE00: 0000000023773E40 0000000023773E40 0000000000000000 0000000000227FE0 @>w#....@>w#.............."..... 0x00000000291AFE20: FFFFFFFFFFFFFFFE 0000000000000000 0000030000000400 0000000004ABC35C ........................\....... 0x00000000291AFE40: 0000000000000000 0000000004850359 0000000023773E40 0000000000000000 ........Y.......@>w#............ 0x00000000291AFE60: 0000000025396690 0000000004850350 0000000004850350 00000000044C809D .f9%....P.......P.........L..... 0x00000000291AFE80: 0000000023773E40 0000000023773E40 0000000025396690 0000000004850350 @>w#....@>w#.....f9%....P....... 0x00000000291AFEA0: 0000000000000000 00000000291AEAF0 00000000291AEAF0 0000000000000000 ...........).......)............ 0x00000000291AFEC0: 0000000025396690 0000000004850373 0000000000000000 0000000000000000 .f9%....s....................... 0x00000000291AFEE0: 0000000000000000 0000000000000000 0000000000000000 0000000004AC0AD7 ................................ 0x00000000291AFF00: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFF20: 0000000000000000 0000000004AC0C7E 0000000025396690 0000000000000000 ........~........f9%............ 0x00000000291AFF40: 0000000000000000 0000000000000000 0000000000000000 0000000076AA59BD .........................Y.v.... 0x00000000291AFF60: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFF80: 0000000000000000 0000000076CDA2E1 0000000000000000 0000000000000000 ...........v.................... 0x00000000291AFFA0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFFC0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ 0x00000000291AFFE0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................ ================================================================================ Object at RCX(0000000000000004) 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: 'D:\Falcon\Falcon BMS 4.33 U1\Bin\x64\Falcon BMS.exe', run by Fabrizio. Error occurred at 00:15:56 on 2016-07-01. Version: Falcon BMS 4.33.1 (x64) 15227 Game is Campaign type Local Theater terrain path: 'D:\Falcon\Falcon BMS 4.33 U1\Data\Terrdata\korea' Operating System: Windows 7 (6.1.7601) Platform 2 Service Pack 1. Computer Name: FABRIZIO-PC Domain: WORKGROUP. 8 logical processor(s), type 8664. CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz. GenuineIntel. Stepping: 3 Model: C Family: 6. GPU 0: NVIDIA GeForce 9500 GT. Vendor: 4318\. Device: 1600\. SubSys: 1883642330\. Revision: 161. 37% memory in use: 8134 MB physical memory 5052 MB physical memory free 16265 MB paging file 12778 MB paging file free 8388608 MB user address space 8387677 MB user address space free Module List: D:\Falcon\Falcon BMS 4.33 U1\Bin\x64\Falcon BMS.exe, loaded at 0x0000000004470000 - 9402880 bytes - TimeDateStamp 0x 56fac303 - File date is 15:01:44 on 2016-03-29 C:\Program Files (x86)\FreeTrack\NPClient64.dll, loaded at 0x000000006a940000 - 19968 bytes - TimeDateStamp 0x 526cd113 - File date is 16:58:06 on 2015-11-24 D:\Falcon\Falcon BMS 4.33 U1\Bin\x64\dbghelp.dll, loaded at 0x000000006e280000 - 1558912 bytes - TimeDateStamp 0x 4b673670 - File date is 07:33:04 on 2010-03-03 C:\Windows\system32\kernel32.dll, loaded at 0x0000000076a90000 - 1163264 bytes - TimeDateStamp 0x 56e9ab29 - File date is 15:48:34 on 2016-03-16 C:\Windows\system32\USER32.dll, loaded at 0x0000000076bb0000 - 1008640 bytes - TimeDateStamp 0x 56423d2a - File date is 15:55:28 on 2015-11-10 C:\Windows\SYSTEM32\ntdll.dll, loaded at 0x0000000076cb0000 - 1732864 bytes - TimeDateStamp 0x 56e9ab48 - File date is 15:55:56 on 2016-03-16 C:\Windows\system32\PSAPI.DLL, loaded at 0x0000000076e80000 - 9216 bytes - TimeDateStamp 0x 4a5bc29d - File date is 22:41:54 on 2009-07-13 Environment Variables: 2: <adsk_3dsmax_x64_2014=c:\program files\autodesk\3ds="" max="" 2014\=""> 3: <allusersprofile=c:\programdata> 4: <appdata=c:\users\fabrizio\appdata\roaming> 5: <cm2014dir=c:\program files="" (x86)\common="" files\autodesk="" shared\materials\=""> 6: <commonprogramfiles=c:\program files\common="" files=""> 7: <commonprogramfiles(x86)=c:\program files="" (x86)\common=""> 8: <commonprogramw6432=c:\program files\common="" files=""> 9: <computername=fabrizio-pc> 10: <comspec=c:\windows\system32\cmd.exe> 11: <fp_no_host_check=no> 12: <homedrive=c:> 13: <homepath=\users\fabrizio> 14: <ilbdir=c:\program files="" (x86)\common="" files\autodesk="" shared\materials\=""> 15: <ilmdir=c:\program files="" (x86)\common="" files\autodesk="" shared\materials\=""> 16: <kicad_ptemplates=c:\program files\kicad\share\kicad\template=""> 17: <kisys3dmod=c:\program files\kicad\share\kicad\modules\packages3d=""> 18: <kisysmod=c:\program files\kicad\share\kicad\modules=""> 19: <localappdata=c:\users\fabrizio\appdata\local> 20: <logonserver=\\fabrizio-pc> 21: <number_of_processors=8> 22: <os=windows_nt> 23: <path=c:\program files="" (x86)\nvidia="" corporation\physx\common;c:\program="" (x86)\intel\icls="" client\;c:\program="" files\intel\icls="" client\;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="" files\intel\intel(r)="" management="" engine="" components\dal;c:\program="" (x86)\intel\intel(r)="" components\ipt;c:\program="" (x86)\amd\ati.ace\core-static;c:\program="" files\common="" files\autodesk="" shared\;c:\program="" (x86)\autodesk\backburner\=""> 24: <pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc> 25: <processor_architecture=amd64> 26: <processor_identifier=intel64 6="" 60="" family="" model="" stepping="" 3,="" genuineintel=""> 27: <processor_level=6> 28: <processor_revision=3c03> 29: <programdata=c:\programdata> 30: <programfiles=c:\program files=""> 31: <programfiles(x86)=c:\program files="" (x86)=""> 32: <programw6432=c:\program files=""> 33: <psmodulepath=c:\windows\system32\windowspowershell\v1.0\modules\> 34: <public=c:\users\public> 35: <sessionname=console> 36: <systemdrive=c:> 37: <systemroot=c:\windows> 38: <temp=c:\users\fabrizio\appdata\local\temp> 39: <tmp=c:\users\fabrizio\appdata\local\temp> 40: <userdomain=fabrizio-pc> 41: <username=fabrizio> 42: <userprofile=c:\users\fabrizio> 43: <windir=c:\windows> 44: <__COMPAT_LAYER=ElevateCreateProcess> ================================================================================</windir=c:\windows></userprofile=c:\users\fabrizio></username=fabrizio></userdomain=fabrizio-pc></tmp=c:\users\fabrizio\appdata\local\temp></temp=c:\users\fabrizio\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=3c03></processor_level=6></processor_identifier=intel64></processor_architecture=amd64></pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc></path=c:\program></os=windows_nt></number_of_processors=8></logonserver=\\fabrizio-pc></localappdata=c:\users\fabrizio\appdata\local></kisysmod=c:\program></kisys3dmod=c:\program></kicad_ptemplates=c:\program></ilmdir=c:\program></ilbdir=c:\program></homepath=\users\fabrizio></homedrive=c:></fp_no_host_check=no></comspec=c:\windows\system32\cmd.exe></computername=fabrizio-pc></commonprogramw6432=c:\program></commonprogramfiles(x86)=c:\program></commonprogramfiles=c:\program></cm2014dir=c:\program></appdata=c:\users\fabrizio\appdata\roaming></allusersprofile=c:\programdata></adsk_3dsmax_x64_2014=c:\program>
-
So far, this has been a fantastic new version of FBMS! However, there will always be some growing pains associated with new software improvements.
For one, I have found that the 2D cockpit FOV can not be changed. Since I do use 2D quite a bit during flights, I have found the FOV to be to close for what I want to see and be able to function in pit when accessing pit functions. 3D pit is fine for FOV settings but is difficult when dealing with specific aircraft functions that are much easier to access in 2D pit. Below is the 2D “in pit” list for FOV.
guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 59.999996 0 23 9000 29 18000 1 27000 26 ‘HUD - up once’
guidedview 1 0.000000 0.000000 0.000000 0.000000 -15.621903 0.000000 59.999996 0 0 9000 13 18000 2 27000 9 ‘straight forward’
guidedview 2 0.000000 0.000000 0.000000 0.000000 -36.536102 0.000000 41.999962 0 1 9000 17 27000 3 ‘MFDs - backup instruments’
guidedview 23 0.000000 0.000000 0.000000 -0.000000 28.439116 0.000002 59.999996 0 24 9000 36 18000 0 27000 32 ‘up twice’
guidedview 24 0.000000 0.000000 0.000000 -0.000000 58.439114 0.000001 59.999996 0 25 9000 43 18000 23 27000 40 ‘up three times’
guidedview 25 0.000000 0.000000 0.000000 0.000000 88.439110 -0.000000 59.999996 9000 49 18000 24 27000 46 ‘up four times’In 4.32, I could change the “in pit” FOV by changing the 7th initial value to increase FOV. Like this….
guidedview 0 0.000000 0.000000 0.000000 -0.000000 1.791412 0.000002 89.999996 0 23 9000 29 18000 1 27000 26 ‘HUD - up once’
guidedview 1 0.000000 0.000000 0.000000 0.000000 -15.621903 0.000000 89.999996 0 0 9000 13 18000 2 27000 9 ‘straight forward’
guidedview 2 0.000000 0.000000 0.000000 0.000000 -36.536102 0.000000 41.999962 0 1 9000 17 27000 3 ‘MFDs - backup instruments’
guidedview 23 0.000000 0.000000 0.000000 -0.000000 28.439116 0.000002 59.999996 0 24 9000 36 18000 0 27000 32 ‘up twice’
guidedview 24 0.000000 0.000000 0.000000 -0.000000 58.439114 0.000001 59.999996 0 25 9000 43 18000 23 27000 40 ‘up three times’
guidedview 25 0.000000 0.000000 0.000000 0.000000 88.439110 -0.000000 59.999996 9000 49 18000 24 27000 46 ‘up four times’The 89.999996 field highlited in red changes the FOV for 2D pits in 4.32
4.33 has not effect on changing FOV in 2D pit. This issue may have a solution, but I can not find it. 90* FOV in 2D pit works perfect for me when accessing certain functions. Is there any additional things I need to know or do to enable this?
Also, any other small issues people might be having could be included in this thread. Been reading all of the threads with possible issues so I know what to look for and how to deal with them.
Any fix on this issue? Thanks
Yes I found one: apply same changes “to the 3dckpit.dat in ckptart folder (not the one in the F-16CM-50 folder) then it works even for the F-16CM-50.” -
Hi Folks,
Read the thread, seems a lot has been handled already….awesome, though i found a texture glitch on the Mlu model:
Its on both sides… i hope there is a solution for this…
I know this are the txtrs from Jan Has in the Balkans Theater, but with the new BMS 4.33 txtrs in Korea its same issue and only with the Mlu mdl…Thx in advance…
Grtz,
H!TEC