Vantskruv

What is the difference between the rb75, rb75b and the rb75t?

Very much thanks, another suggestion would be to see which weapons you can combine/take-with-you with the aircraft.

Where is the RB-05A control joystick/hat placed in the real cockpit, or is it the radar control joystick that steers the weapon? Searched through the manual, but have not found any visual reference of the control.

Thank you, setting QFE to get ground level every time releasing a bomb would be quite awkard.

FORGET THIS POST BELOW (solution above) I was testing the LASTE system, trying to input wind data while climbing from airport. I'm not sure if this is per function, or it is a bug. When setting wind data while climbing, the wind measurement halts at the inputted data. Only temp is continuing measuring, slowly decreasing while gaining altitude as expected. If clearing the LASTE-data, current wind data is correctly displayed and updated. I was hoping to be able to put in winddata while climbing instead of writing it down at paper. Is this per function, or should I report it as a bug? NOTE: I'm running DCS 1.5.

Is HOF affected by current set airpressure in altimeter? Or is HOF always using the STD pressure of 29.92?

I don't think that is possible as shortcut keys seems to be hardcoded in the game (not possible to mod via scripts....correct me if I'm wrong). Though it is possible to modify the lists of the menus, but only to the maximum of the 10 items (F1 to F10). Yet I've not found a way to automatically reset the menu to return to mainmenu, also I've not been able to disable the auto popup of the menu, i.e. when you request startup, the menu of requesting taxi automatically shows up.

Is it not possible to change reosultion on these small panels? Do they behave different than TV- and computer- displays?

http://www.starvr.com/ I just wanted to create this thread as I'm interested in this VR peripheral. Why I'm interested is that it will come with a FOV of horizontal 210 degrees and vertical 130 degrees. I've heard that HTC Vive and Oculus Rift will have about 110 degrees FOV. Anyone heard of any plans DCS supporting this device?

Thank you very much Yurgon, have not thought about the HUD representing which sensor is set as SPI. I need to check this out when I come home. Also I'm discussing with myself, maybe a bit value returned by one of my synapses may get flipped, so sometimes I may press CHINA HAT long backwards instead of long forwards withou noticing it...:unsure:

I think he means he have problems to slaving all sensors to SPI. I've noticed this aswell, but I'm not sure if I'm doing it wrong. Example of my problem while setting SPI with TGP and slave all sensor to it: To begin with, I have HUD as SOI and a markpoint A selected, I slave all my sensors with CHINA HAT long forward. As this is done, TGP moves and points to the markpoint as expected. Edit: Actually I do not remember if I do the CHINA HAT long forward with TGP as SOI, sorry, need to check that when I come home... With the TGP as SOI, I slew it to a target of my choice, then make that point as SPI by pressing TMS long up. Then I slave all my sensors to that SPI by CHINA HAT long forward. This is when the problem comes, as some times the previous SPI (markpoint A in this case) still is SPI (as if the SPI set at the slewed target did not get set), and TGP will slew back to my markpoint, instead of still pointing to the target that I slewed to. So then, I again need to do the process by finding the target and setting it as SPI and slaving all sensor to it, hoping it will not slew back to my markpoint. Sometimes it works, sometimes it does not, which is very irritating when you have found your target.

Press 'TAB'.

Another crash. Playing with the HUEY and then the A10C on multiplayer server. Log file is 131MB big, but I noticed that this log-code repeats itself over and over again filling up the file 05273.946 UNKNOWN ?: [string "./MissionEditor/GameGUI.lua"] in line 172 in func: 05273.946 UNKNOWN ?: [string "./Scripts/UI/gameMessages.lua"] in line 157 in func: updateAnimations 05273.946 UNKNOWN ?: [string "./Scripts/UI/lentaMessages.lua"] in line 177 in func: updateAnimations 05273.946 UNKNOWN ?: [C] in line -1 in func: ipairs 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 55 in func: setVisible 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetSetVisible 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 110 in func: getSize 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetGetSize 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 106 in func: setSize 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetSetSize 05273.946 UNKNOWN ?: [string "./Scripts/UI/lentaMessages.lua"] in line 177 in func: updateAnimations 05273.946 UNKNOWN ?: [C] in line -1 in func: ipairs 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 55 in func: setVisible 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetSetVisible 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 110 in func: getSize 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetGetSize 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 106 in func: setSize 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetSetSize 05273.946 UNKNOWN ?: [string "./dxgui/bind/Widget.lua"] in line 59 in func: getVisible 05273.946 UNKNOWN ?: [C] in line -1 in func: WidgetGetVisible And then ending with: 05291.035 WARNING DX11BACKEND: setTechnique() must be non zero 05291.035 INFO DCS: try to write dump information 05291.039 INFO EDCORE: # -------------- 20151002-101233 -------------- 05291.041 INFO EDCORE: 05291.042 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 65D19680 00:00000000 05291.046 INFO EDCORE: 00000000 00000000 0000:00000000 05291.081 INFO EDCORE: 65D19680 00C2EDE0 0000:00000000 ?setShader@DX11Renderer@RenderAPI@@UEAAHPEAUIShader@2@_K@Z()+60 05291.083 INFO EDCORE: 69241E6C 00C2EEA0 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+254C 05291.090 INFO EDCORE: 69241A4D 00C2EED0 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+212D 05291.126 INFO EDCORE: 6BBD40FF 00C2EF00 0000:00000000 ?DrawObjects@DXRenderer@Graphics@@UEAAXPEAPEAVRenderObject@2@I@Z()+6F 05291.127 INFO EDCORE: 7574DEEA 00C2EF40 0000:00000000 ?DrawZWrited@RenderParserImpl@@QEAAXXZ()+11A 05291.128 INFO EDCORE: 75750825 00C2EFD0 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+2265 05291.128 INFO EDCORE: 7575053B 00C2F000 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+1F7B 05291.129 INFO EDCORE: 757698BB 00C2F2E0 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+80B 05291.130 INFO EDCORE: D7BE7D04 00C2F370 0000:00000000 05291.131 INFO EDCORE: D7BEB44E 00C2F3D0 0000:00000000 05291.131 INFO EDCORE: D7C01BE4 00C2F400 0000:00000000 05291.132 INFO EDCORE: D7C01B34 00C2F430 0000:00000000 05291.132 INFO EDCORE: D7CAB4BC 00C2FAE0 0000:00000000 05291.135 INFO EDCORE: D7CAD365 00C2FB20 0000:00000000 05291.139 INFO EDCORE: 84FD2D92 00C2FB50 0000:00000000 BaseThreadInitThunk()+22 05291.139 INFO EDCORE: 86039F64 00C2FBA0 0000:00000000 RtlUserThreadStart()+34 05291.237 INFO EDCORE: Minidump created. 05291.239 INFO DCS: try to write track file Edit: Adding a crashdump for this crash. CrashDump.zip

Crash log thread with description Crashing while sitting in the cockpit starting up the engine of the KA-50 in a "CREATE FAST MISSION scenario" Adding log and crash dump data. This is the end of the log for reference 00214.016 DEBUG SOUNDER: dofile("CommonAlg.lua") 00214.016 DEBUG SOUNDER: dofile("Tools.lua") 00214.016 DEBUG SOUNDER: created host MAIN_16827392/main, id=219 00214.016 DEBUG SOUNDER: created sounder MAIN_16827392 as 163 00216.129 WARNING DX11BACKEND: setTechnique() must be non zero 00216.151 INFO DCS: try to write dump information 00216.155 INFO EDCORE: # -------------- 20151002-072036 -------------- 00216.163 INFO EDCORE: 00216.165 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 65E99680 00:00000000 00216.169 INFO EDCORE: 00000000 00000000 0000:00000000 00216.233 INFO EDCORE: 65E99680 0111F1F0 0000:00000000 ?setShader@DX11Renderer@RenderAPI@@UEAAHPEAUIShader@2@_K@Z()+60 00216.236 INFO EDCORE: 693E1E6C 0111F2B0 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+254C 00216.285 INFO EDCORE: 693E1A4D 0111F2E0 0000:00000000 ?GetLoadPriority@NGModel@model@@UEAAMXZ()+212D 00216.334 INFO EDCORE: 6C6540FF 0111F310 0000:00000000 ?DrawObjects@DXRenderer@Graphics@@UEAAXPEAPEAVRenderObject@2@I@Z()+6F 00216.336 INFO EDCORE: 6E48DEEA 0111F350 0000:00000000 ?DrawZWrited@RenderParserImpl@@QEAAXXZ()+11A 00216.337 INFO EDCORE: 6E490825 0111F3E0 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+2265 00216.339 INFO EDCORE: 6E49053B 0111F410 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+1F7B 00216.342 INFO EDCORE: 6E4A98BB 0111F6F0 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+80B 00216.343 INFO EDCORE: D7BE7D04 0111F780 0000:00000000 00216.343 INFO EDCORE: D7BEB44E 0111F7E0 0000:00000000 00216.343 INFO EDCORE: D7C01BE4 0111F810 0000:00000000 00216.344 INFO EDCORE: D7C01B34 0111F840 0000:00000000 00216.344 INFO EDCORE: D7CAB4BC 0111FEF0 0000:00000000 00216.345 INFO EDCORE: D7CAD365 0111FF30 0000:00000000 00216.347 INFO EDCORE: 84FD2D92 0111FF60 0000:00000000 BaseThreadInitThunk()+22 00216.347 INFO EDCORE: 86039F64 0111FFB0 0000:00000000 RtlUserThreadStart()+34 00218.301 INFO EDCORE: Minidump created. 00218.303 INFO DCS: try to write track file Logs.zip DxDiag.txt

Crashed here while flying the A10C. Happened a couple of seconds after turning TGP on. dcs_log.txt

First, it is only showing half the cockpit (from backside to middle of pilot seat). Second, it turns off when turning the rotary floodlight switch less than a quarter of a circle.

Yep, push to talk! Though it is working flawlessy with stable version.

I noticed that no one could hear me at TS3 while flying. Any other that had this problem or know a solution? Note: Installed plugins was unchecked.

It is also a good name to remember when playing scrabble, many points you see.:D "mnogofaktornozavisyaschego"

Ok thanks my friend, I will download it now.

Should I download the current version of openbeta, or wait until 1.5 is released (maybe relieving the load on the servers)?

No love either to the KA50? :cry:

After I read your post Skatezilla, I was wondering what the other pair of number ( i.e. 0.8 ) mean. I've googled a little and also searched in the manual. So, I found a very good explanation of the alignment process: http://www.checksix-fr.com/bibliotheque/index.php?Fichier=6119 There is also an explanation in the manual, though I couldn't find any detailed data about requirements for EAC to fully work. So to conclude how it works from my research: T = x.x y.y where x.x is minutes processed while aligning and y.y is the status of the alignment which in chronological steps shows: - INIT - ATTD (system knows attitude data) - ATTD + HDG (system knows attitude and heading data) - 8.0 - 7.2 (at this time INS NAV READY is showing, you are ready to activate NAV in scramble mode) and down to 0.8 The decimal number shows the accuracy of the system (the lesser the better), and EAC needs an accuracy lesser than 1.0 to be enabled. Edit: I.e. if accuracy is 7.2, errors are 7.2 times greater than normal.

Just remember to activate nose-steering below 70 knots, and everything will be okay.

I had this problem too, but I've learned that: * Do not move your aircraft before NAV is aligned to version 4.0.0.8, otherwise alignment will stop and EAC will not function properly. * Do not switch EAC on before you selected NAV after it have been aligned (Î'm not sure if this is required or not). My steps when starting up the aircraft (concentrated on the EAC and NAV): 1) Turn on EGI and CDU switches (below the CDU screen) 2) Do not move the aircraft while NAV is aligning, the alignment takes about 4 minutes. 3) When alignment is done, it is represented by a blinking 'INS NAV READY' in the top of the CDU screen and the version T = 4.0.0.8 is represented. 4) Navigate to the NAV->ALIGN page in CDU 5) Check that T= 4.0.0.8, this tells us that NAV is fully aligned (as when INS NAV READY is flashing) 6) Select NAV by pressing R7 button on the CDU, or OSB9 on MFD (if I calculating it correctly) when in ALIGN page. 7) Press EGI button on NMSP (Navigation Mode Select Panel) 8) Turn on the RDR ALTM and EAC which is placed below the throttle.