bwRavencl

Afaik it can be used by the pilot to place an event mark in the avionics log, to help the maintenance crew find the cause of a potential anomaly.

Thanks! :thumbup:

If they had the manual in a release-worthy state, we would certainly already have our hands on it. It's pretty obvious (also to ED) that everybody would like to have the manual as early as possible - thus it makes practically zero sense to ask for it. :doh: However, requesting a list of the key commands (which was the actual intention behind me starting this thread) is an entirely different story and not so obvious. For complex aircraft like the Hornet the creation of a profile can take multiple hours and the "looking up" of the key commands is something that we could already do now while we are waiting for the Hornet to go EA. Of course what I am assuming here is that the definition of the commands is pretty much done right now and won't change drastically until release.

Since we are pretty close to the early access release now, could we perhaps already get a list of all the Hornet's input commands and their corresponding key strokes? (Or simply a list of all the commands present on the HOTAS, if the preparation of a complete list would be too time consuming.) This way people using external controller mapping software could already start preparing profiles for the Hornet now and have them pretty much ready on release. :joystick: Thanks!

Even though I think it's doubtful if Razbam currently has the resources for another project, a GR3 or FRS1 would be awesome at some point!

The High-G breathing sounds should either be customized or removed entirely for the Gazelle, due to the lack of oxygen masks.

+1

+1 for CH-53

+1

Still not fixed with today's update... :dontgetit: I'm a software developer myself and it really can't be that hard to simply completely disable the FFB device capability detection routine until this issue gets sorted out. That way people with FFB devices could at least play the game, even if this would cause FFB functionality to be completely unavailable in the meantime.

The server seems to have been down for a while. Will it come back online again or was it permanently shut down? Would be a shame because this was definately my favourite server for taking the MiG-21 up for a spin...

Just experienced this as well for the first time. I was on the 104th server and after flying for around 45 minutes with lots of people on it my FPS went down the drain just as described in the posts above.

Not an answer to your original question, but it might be intersting for you anyhow: Check out http://vjoystick.sourceforge.net in case you haven't seen it already. I'm using vjoy as the driver for my own controller software ControllerBuddy and it works just as expected in conjunction with DCS.

Callsign: bwRavencl Squadron: Lonewolf Location: Germany Ride: F-15C / Su-27

As a temporary workaround, I made a few minor modifications to the ControlIndicator_page.lua file lcoated in "...\DCS World\Mods\aircraft\M-2000C\Cockpit\ControlsIndicator". Here's the content of my modified ControlIndicator_page.lua file (I removed the indicators for the brakes and trimming, as I wasn't able to get them to work properly): dofile(LockOn_Options.common_script_path.."elements_defs.lua") local texture_red = MakeMaterial("Bazar/Textures/AvionicsCommon/arcade.tga",{255, 0, 0, 255}) SetCustomScale(1.0) function AddElement(object) object.screenspace = ScreenType.SCREENSPACE_TRUE object.use_mipfilter = true Add(object) end local pitch_stick_real_range = 9.03125 local pitch_stick_part_positive = (14+6.5)/(14+26) local pitch_stick_part_negative = (26-6.5)/(14+26) local roll_stick_real_range = 11.875 local roll_stick_part_left = 0.5 local roll_stick_part_right = 0.5 local aspect = LockOn_Options.screen.aspect local size_x = 0.15 -- +-size_x local size_y_positive = size_x * 2.0 * pitch_stick_real_range / roll_stick_real_range * pitch_stick_part_positive local size_y_negative = size_x * 2.0 * pitch_stick_real_range / roll_stick_real_range * pitch_stick_part_negative local tex_scale = 0.25/size_x local line_width = (4.5/512)/tex_scale * 0.3 local roll_stick_movement = 140 local k = size_x / roll_stick_movement local pitch_stick_movement_positive = 0.76 * roll_stick_movement * 0.625 * k local pitch_stick_movement_negative = 0.76 * roll_stick_movement * 0.375 * k local ds = 0.05 * size_x local rud_shift = 2*0.1*size_x local rud_base_shift = rud_shift --0.05*size_x local orange_mat = MakeMaterial("", {255, 100, 0, 50}) local rudder_shift = 0.1*size_x -- BASE ----------------------------------------------------------------------- base = CreateElement "ceMeshPoly" base.name = "base" base.primitivetype = "triangles" base.material = orange_mat -- "GREEN_TRANSPARENT" base.vertices = {{-(size_x + rud_shift + rud_base_shift + 2*ds), -(size_y_negative + 2 * ds + rudder_shift)}, -- lower left, CW {-(size_x + rud_shift + rud_base_shift + 2*ds), size_y_positive + ds}, { size_x + ds, size_y_positive + ds}, { size_x + ds, -(size_y_negative + 2 * ds + rudder_shift)}} base.indices = default_box_indices base.init_pos = {0,-(1 - 1.5*size_x)} base.controllers = {{"show"},{"screenspace_position",2,-(aspect - 2*size_x),0}, {"screenspace_position",1,0,0}} base.h_clip_relation = h_clip_relations.REWRITE_LEVEL base.level = DEFAULT_LEVEL AddElement(base) -- STICK SCALE----------------------------------------------------------------- pitch_scale = CreateElement "ceTexPoly" pitch_scale.name = "pitch_scale" pitch_scale.vertices = { {-size_y_negative, -line_width}, {-size_y_negative, line_width}, {size_y_positive, line_width}, {size_y_positive, -line_width}} pitch_scale.indices = default_box_indices pitch_scale.material = texture_red pitch_scale.init_rot = {90,0,0} pitch_scale.tex_params = {256/512,176.5/512,0.5*tex_scale,2*tex_scale} pitch_scale.parent_element = base.name AddElement(pitch_scale) roll_scale = CreateElement "ceTexPoly" roll_scale.name = "roll_scale" roll_scale.vertices = { {-size_x, -line_width}, {-size_x, line_width}, {size_x, line_width}, {size_x, -line_width}} roll_scale.indices = default_box_indices roll_scale.material = texture_red roll_scale.tex_params = {256/512, 176.5/512, tex_scale, 2*tex_scale} roll_scale.parent_element = base.name AddElement(roll_scale) -- STICK ---------------------------------------------------------------------- local stick_index_size = 0.1 * size_x stick_position = CreateElement "ceTexPoly" stick_position.name = "stick_position" stick_position.vertices = { {-stick_index_size, -stick_index_size}, {-stick_index_size, stick_index_size}, { stick_index_size, stick_index_size}, { stick_index_size, -stick_index_size}} stick_position.indices = default_box_indices stick_position.material = texture_red stick_position.tex_params = {330/512, 365.5 / 512, 2*tex_scale, 2*tex_scale/0.8} stick_position.controllers = { {"stick_pitch", -size_y_negative}, {"stick_roll", size_x}} stick_position.parent_element = base.name AddElement(stick_position) -- PEDALS --------------------------------------------------------------------- rudder_scale = Copy(roll_scale) rudder_scale.name = "rudder_scale" rudder_scale.init_pos = {0, -(size_y_negative + rudder_shift)} AddElement(rudder_scale) rudder_index = Copy(roll_scale) rudder_index.vertices = { {-rudder_shift, -line_width}, {-rudder_shift, line_width}, {rudder_shift, line_width}, {rudder_shift, -line_width}} rudder_index.controllers = {{"rudder",size_x},{"rotate",math.rad(90)}} rudder_index.parent_element = rudder_scale.name AddElement(rudder_index) -- THROTTLE SCALE ------------------------------------------------------------- throttle_scale = Copy(pitch_scale) throttle_scale.name = "throttle_scale" throttle_scale.init_pos = {-(size_x + rud_base_shift + ds), 0} throttle_scale.parent_element = base.name AddElement(throttle_scale) -- THROTTLE throttle_index = Copy(roll_scale) throttle_index.vertices = { {-0*rud_shift, -line_width}, {-0*rud_shift, line_width}, {rud_shift, line_width}, {rud_shift, -line_width}} throttle_index.init_pos = {-size_y_negative, 0} throttle_index.init_rot = {-90,0,0} throttle_index.controllers = {{"throttle", size_y_positive + size_y_negative}, {"scale",1.0, 2.0}} throttle_index.parent_element = throttle_scale.name AddElement(throttle_index)

Signing up! (F-15) Thx!

In case anyone is still looking for the Great Planes credits song: Artist: Mars Lasar Title: Fusion Spotify:

Nickname: bwRavencl Your profile at ED forum: http://forums.eagle.ru/member.php?u=115244 Chosen plane type: MiG-15bis Country of residence: Germany Time: GMT+1 Language of communication: English Confirmation of familiarization with regulations of the tournament and the obligation to comply with them: Familiarized with regulations of this tournament, oblige myself to comply with them.

Nice gesture STORM. :thumbup:

With visibility set to "low" in the graphics settings I'm experiencing the following graphical glitch in the MiG-21: Parts of the external 3D model that should not be visible are drawn in the internal cockpit view. Please see the screenshots in the attachment for reference. The glitch dissapears, with a visibility-setting of at least "medium". Steps to reproduce: Go to settings and set visibility to "low". Start the quick launch mission "Cold Start" included with the MiG-21 (any other mission or manually created mission should do as well). dcs.log.txt mig_21_cockpit_bug.trk DxDiag.txt

Unfortunately AFAIK your suggested approach won't work since you cannot bind a modifier + a mouse axis to an action. The mouse-look is fixedly bound to the X/Y mouse axis and is only activated upon enabling it by double-clicking a freely choosable button (by default mouse button 3). What I am suggesting above is that the mouse-look is active for only as long as the button is held down. This could probably be achived through LUA scripting, but I'd rather like to see this implemented directly into DCS...

I suggest that the following mouse-button function is added, that would be helpful for people without TrackIR. This suggestion only applies to planes with clickable cockpits - not the FC3 aircraft. Suggestion: Add a mouse button binding as follows: While the button is pressed down activates mouse-look in the cockpit view When the button is released mouse-look is deactivated If the cursor is currently over a switch etc. in the cockpit, the right click is forwarded to the switch instead and mouse-look is not activated. Currently there is only a binding (by default double click mouse button 3) that permanently enters mouse-look mode, until another double click of button 3 is performed. I think my suggestion would greatly increase the speed with which one can operate switches etc. in the cockpit. For reference, X-Plane implements such a cockpit-view control scheme.

I experienced a similar behavior with the Hawk during one flight in DCS 1.5. Unfortunately I don't have a track of when it occured...

Confirming this - pilot is missing in the mirror of the F-15 for me too.

I concur, the cursor is very annoying when flying in FC3 aircraft, especially when you are using mouse-look. Also when flying in an MP session it first appears, and then stays visible during any subsequent single player sessions until DCS is restarted.