ajax

You say that remarking function PopulateRadioMenu eliminates the crash. That tells me one of the two statements within is causing the problem. I suspect it is the first one: removeItemForGroup. Try remarking that line and see what happens. You may find that it is not needed at all.

Make sure you don't have a waypoint or target point selected on the PVI-800. I believe the HUD displays distance to that point instead of the laser range.

Yes, I have had this problem at least twice. Repair would not fix it. I had to re-install from scratch. Since then I maintain a complete working copy of the DCS folder. If I get it again, I will copy everything back to the original. I don't know if that will work but it should.

There seems to be a bug (?) in the PVI-800 where everything is rounded down. Wind speed displayed by the PVI-800 is always (except at 0) 1 m/s less than actual. With this in mind your pictures of the ABRIS and PVI-800 coordinates match. The ABRIS is degrees-minutes-seconds and the PVI-800 is degrees-decimal minutes. My calculations show that the PVI-800 should display longitude 041'47'9 instead of 041'47'8. So I'm not sure that even if alignment was modelled that you would see a difference before and after.

Many thanks to both of you!

Nice, Grimes. Is the multiline outtext capability part of Mist?

Now that's a good idea. Thanks!

Most of what you want to do cannot be done in FC2. Some them can be done with scripting in DCS. I'm certainly no expert but here's what I think: 1. Not possible. 2. The aircraft cycles between the begin and end loop waypoints until bingo fuel. 3. Multiple waypoints back and forth. Sometimes as many as 20-30 waypoints. 4. Not sure. 5. Not possible. 6. Not possible. 7. Destroy AI group when it lands, and respawn a new group. 8. If the location is known, create a late-activation infantry group at that location and activate when the condition is met. 9. Not respawning per se, but multiple late-activation groups that are activated by triggers. 10. Not sure.

I'm fairly new to Lua scripting so this might be a question with a simple answer: How do you debug scripts? The only way I've found is to put multiple env.info() statements in the script and then read the log file. Is there a better way?

You're welcome. I hope you get it to work. If you have problems, PM me and I'll send you the corrected file.

DCS always reverts to the default skin when you zoom out past a certain point. The problem is that for the Ka-50 the default skin package is incomplete--several files are missing. That is why you see the orange skin. The problem file is ..\bazar\world\textures\ka-50_general.zip. You can fix it yourself by zipping the ..\bazar\liveries\ka-50\Russia Standard Army folder and renaming it to ka-50_general.zip. Then replace the file of the same name in ..\bazar\world\textures. Note that this is not a global fix--it only fixes it for you. Edit: I should say zip the contents of the Russia Standard Army folder.

Works for me.

...that you know of.:) You may be using the same online username as someone else who has been banned. Some servers check both IP and username against a ban list. Edit: Try changing your name.

No problems here. Perhaps you are failing integrity checks or your IP address and/or username has been banned from a particular server? Edit: Also, what is your ping? Some servers limit the ping.

Well, Falcon, I figured it out just this morning and TBH never thought about it before you asked the question.:) I presume full file paths are acceptable, but I haven't tested it. Edit: Full pathnames work fine.

Here you go, Falcon: Edit {DCS}\Scripts\UserFiles.lua to include the lines in red. Modify according to your system. local lfs = require('lfs') sysTracksPath = lfs.currentdir() .. 'Missions\\Tracks\\' userMissionPath = lfs.writedir()..'Missions\\' userTrackPath = lfs.writedir()..'Tracks\\' sysCampaignPath = lfs.currentdir() .. 'Missions\\Campaigns\\' userCampaignPath = lfs.writedir() .. 'Missions\\Campaigns\\' userMoviePath = lfs.writedir() .. 'Movies\\' [color=Red]userSquadMissionPath = lfs.writedir()..'Missions\\Squad\\' userPublicMissionPath = lfs.writedir()..'Missions\\Public\\' userServmanMissionPath = lfs.currentdir()..'Missions\\Multiplayer\\' [/color] function initLocations() function _(str) return str end lfs.add_location(_('My Missions'), userMissionPath) [color=Red] lfs.add_location(_('Squad Missions'), userSquadMissionPath) lfs.add_location(_('Public Missions'), userPublicMissionPath) lfs.add_location(_('Servman Missions'), userServmanMissionPath) [/color]end initLocations()

Servman is working well on the 159th server.

I think that should be Left-Alt + ' .

If it is a western FARP you must have an M818 supply truck.

Yep. Only Ka-50 for me. I just don't have the desire to fly a fixed-wing aircraft.

I tried creating a new map (12000 x 6000 pixel bitmap) from scratch using NASA sat data which includes the new areas to the east. I got as far as the attachment, but then got stuck.

I believe the reason the orange skin shows up is that not all necessary files are packaged in the default skin: ".\Bazar\World\textures\Ka-50_general.zip" If you open the zip file you will notice that the following files are missing: ka-50_st_paint1.bmp.dds ka-50-lrm_b.bmp.dds ka-50-lrm_centre.bmp.dds ka-50-lrm-1.bmp.dds ka-50-lrmpart-1.bmp.dds ka-50-paint1-def-01.bmp.dds ka-50-paint1-def-02.bmp.dds ka-50-paint1-def-03.bmp.dds ka-50-paint1-def-04.bmp.dds ka-50-paint1-def-05.bmp.dds ka-50-paint1-def-06.bmp.dds These are the same files that show up in the error log as missing textures. I fixed my orange skin problem by copying these files from the "standard army" skin and including them in the zip file.

Yes, I've come to the same conclusion. The default ellipsoid seems to work better for the Ka-50.

Yes, I do. The custom neck pivot mod and custom snap views.

Confirmed. Even if "use these options for all missions" is selected in options, the Mission Editor does not save a view.lua file. So either the mission was extracted from a track file or, as Grimes rightly pointed out, it was manually placed there.