ajax

I get errors similar to those listed below with many of my missions in the mission editor. It appears the editor is looking in a non-existent path for sound files. For DCSW the path should be .\sounds\sdef\aircrafts\... etc. The defined path leaves out "sdef". Is this something to be concerned about, and can it be fixed by tweaking a lua file? 00002.410 ERROR SOUND: can't load proto file ".\sounds\aircrafts\a-10\apu\apustart.sdef" 00002.410 ERROR SOUND: can't load proto file ".\sounds\aircrafts\a-10\apu\apustartcpt.sdef" 00002.413 ERROR SOUND: can't load proto file ".\sounds\aircrafts\a-10\canopyclose.sdef" 00002.413 ERROR SOUND: can't load proto file ".\sounds\aircrafts\a-10\canopyclosecpt.sdef" 00002.414 ERROR SOUND: can't load proto file ".\sounds\aircrafts\a-10\cockpit\inverter.sdef" 00002.415 ERROR SOUND: can't load proto file ".\sounds\aircrafts\canopyjettison.sdef" 00002.422 ERROR SOUND: can't load proto file ".\sounds\aircrafts\cockpits\seatadjustment.sdef" 00002.422 ERROR SOUND: can't load proto file ".\sounds\aircrafts\cockpits\sidewinderhigh.sdef" 00002.427 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\helicopterengine.sdef" 00002.427 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\planebackengine.sdef" 00002.428 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\planefrontengine.sdef" 00002.428 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\enginejet.sdef" 00002.435 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\cockpit\exin.sdef" 00002.435 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\cockpit\exprop.sdef" 00002.436 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\cockpit\exrin.sdef" 00002.437 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\exb.sdef" 00002.438 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\exf.sdef" 00002.438 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\exr.sdef" 00002.439 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\exs.sdef" 00002.440 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\exsm.sdef" 00002.441 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\exsmdeaf.sdef" 00002.442 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\packardmerlinprop\prop.sdef" 00002.443 ERROR SOUND: can't load proto file ".\sounds\aircrafts\engines\helicopterfan.sdef" 00002.452 ERROR SOUND: can't load proto file ".\sounds\aircrafts\ka-50\ka50_dooropen.sdef" 00002.453 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51\cockpit\controllock_on.sdef" 00002.453 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51\cockpit\fuelpump.sdef" 00002.453 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51\cockpit\fuelshut_off_on.sdef" 00002.454 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51\cockpit\gyro1.sdef" 00002.454 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51\cockpit\primer.sdef" 00002.456 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\actuatorcoolant.sdef" 00002.456 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\actuatoroil.sdef" 00002.457 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\canopyopen.sdef" 00002.457 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\canopyclose.sdef" 00002.458 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\actuatorcoolant.sdef" 00002.459 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\actuatoroil.sdef" 00002.459 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\browningin_12.sdef" 00002.459 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\browningin_34.sdef" 00002.460 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\browningin_56.sdef" 00002.460 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\canopyopen.sdef" 00002.460 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\canopyclose.sdef" 00002.461 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\cockpit\rudderleft.sdef" 00002.462 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\dooropen.sdef" 00002.462 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\flaps.sdef" 00002.463 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\gearlockup.sdef" 00002.465 ERROR SOUND: can't load proto file ".\sounds\aircrafts\p-51d\rudderleft.sdef" 00002.481 ERROR SOUND: can't load proto file ".\sounds\rain.sdef" 00002.508 ERROR SOUND: can't load proto file ".\sounds\weapons\vulcancannon.sdef" I should note that this mission was originally created in BS2/A10C standalone product. I am trying to port it over to DCSW. I suspect that the path was defined when the units were placed on the map, and to correct the problem they will have to be deleted and recreated under DCSW. I searched the files inside the mission file for references to this path, but did not find any. Edit: I just tried creating a very basic mission from scratch in DCSW 1.2.1, and I got the same errors. So porting from an earlier version is not the problem.

Right, 0 works. Bear in mind that I've heard that doing this will break track playback. So you have to decide what's more important to you.

Thanks, Neverminded. That explains it. I recall now that when the problem occurred I was having some issues with my ISP.

Ahh, so you were using the unchain rudder mod (unbeknownst to you of course).:)

I simply meant that this behavior would be explained if you had used the xz unchain rudder method. That is all. Since you do not use it, then the cause must be elsewhere.

Yes. Post #7 in the link is exactly what I do. (The poster seems to think it doesn't work for X52, but it works fine for me.) Anyway, as soon as the x z is sent, you no longer have to recenter the joystick to have authority again.

The mod I was thinking of is accomplished by your joystick profile where a very short "z" "x" combo is sent upon trim release.

You haven't by chance implemented the "unchain rudder" mod, have you? If you did, that will cancel the return-to-center wait.

This is not the original post, but there is a link to it therein:http://forums.eagle.ru/showthread.php?t=94998

I got the black buildings again last night. I made sure to save a copy of the mp client track for Nate, but when I reviewed the track everything appeared normal--no black buildings. Go figure.

I've also noticed you can "correct" it by jumping to lctl-f11 view and moving the camera in the direction the shkval is pointing. At some point as you move the camera the black buildings will be re-rendered and will look fine in the shkval thereafter.

I get this too. I don't use alt-tab as I run in windowed-mode.

Look in C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts\config.lua line 5 v_angle_shift = math.rad(11) -- displacement for padlock and helmet

Check the mixer in the Windows sound applet to make sure sound for DCS is set to reasonable level.

Regarding the issue of activation: I've noticed in v 1.2.0 that every so often (every 5th? connection to the master server) the activation window pops up for one of the modules I have. As they are all already activated I just hit cancel (or exit?) and everything works fine. I wonder if this is the same thing for v 1.2.1. Has anyone just cancelled the activation step to see if it works anyway?

The same thing has happened to me. In fact it did it once tonight. It is very sporadic, though. I was definitely in a stable hover... the autopilot assists just turn off. It is possible that there is a glitch in my joystick mapping software, as there have been times where I hit my Team Speak push-to-talk button (mapped to my collective) and the autohover turns on. Again, it is very sporadic and I cannot intentionally reproduce the behavior.

Recently, I have been getting a "stream error" when trying to connect to a server. I have already connected to the master server, so I think this error is unrelated to that issue. Has anyone else run across this?

You're welcome. I'm just passing along info I got right here on the forums.

I believe there is a small bug for western coalitions: the M818 truck must be present to rearm even though you have an ammo depot static structure.

I've noticed two things: 1. If I use a single monitor, pings show up fine. If I use my dual monitor setup, then the pings initially appear but then soon disappear. A similar problem shows up once a server is joined: the player list initially appears but then disappears after starting to scroll - makes it hard to find an open slot. 2. It looks like the default sort order for the server list is lowest ping at the top of the list to slower pings at the bottom.

There are three places where the scenery levels can be set: 1) On the server, 2) on the client, and 3) in the mission design. It is possible that the mission designer set the level to low. I believe in this case regardless of the client and server settings, the scenery will be low. Edit: There are a few settings available in the ME, such as civilian traffic, but I do not remember if scenery level is one of them. However, if you are creating/editing a mission and you have scenery set low on that machine and have the "always use these settings" option checked, the mission will be saved with those settings; and I think those settings will override the settings on the client or server. (Did I remember to say, "I think".)

This is actually simpler than my earlier post: it leaves out saving the point in ABRIS by resetting the targeting system (backspace). I did not know that.

Page 11-8 of the BS manual: To send Target Point coordinates created in the PVI-800 navigation system: 1. Press the "ОТ" (Target point) push-light button on Navigation Control panel (button will light up). 2. Select the TP ID using the Navigation Control panel keypad. The number will then be displayed on the Navigation Control panel display and the ABRIS will have a blinking marker point as well. 3. Press the desired target type or ingress point push-light button on the Data Link panel (button will light). 4. Select recipient(s) number or all (button will light). 5. Press the "ПРД/ПАМ" (Send/Memory) button (button will light briefly).

You could always determine these empirically: Run a series of flights at differing speeds, altitudes, temperature, etc. with a fixed amount a fuel and record the time and distance at which you run out of fuel. (Time zoom is a wonderful thing!)

Thanks, PM. Djembe, you should try it before rejecting it categorically.