Headspace

I need some suggestions for a gfx/motherboard combo that can support a triple-monitor setup that will run with an acceptable framerate. I'm exploring options here so cost isn't necessarily an issue. Is SLI recommended/required? I would prefer to stick with nvidia.

One of the easiest ways you can reduce your insurance rates is to get an instrument rating. If you haven't yet, that is. If you can afford a Cirrus, there's really no excuse not to.

FC3 is being worked on first, then CA.

Yes.

If you see that, send me the log. Teamspeak 3 occasionally changes the way muting is handled. Try reproducing it and tell me how you did.

For those having PTT problems, which of your applications (DCS, TS3) if any are running as Admin? That might be a big factor here.

USAF uses imperial units for altitude. In fact, I'm pretty sure that goes for all of ICAO as well.

Locations of all of the log files are listed in the "Report Bugs" section of the TARS website. Not yet but we are working on a way to make this possible.

They're supposed to be, but this is a bug. So evidently they're not--at the moment. This is the first issue being dealt with currently so please be patient. The transition over to World involved completely re-writing the DCS-side interface to fold everything under one umbrella.

Yes. I hope I was clear in the initial announcement that this is the case. If it wasn't clear, I apologize. Don't worry. The plan is to have ALL of the FC3 aircraft working with TARS in one way or another.

The spam issue was around well before this version. It requires adjusting the spam settings on the server to get rid of; at this point I am exploring ways to minimize the inter-client traffic, but I suspect this will always be a factor. As the release announcement says, the radio frequencies in the control panel are an as of yet unactivated feature. Everything on the A-10 is supposed to be working as it did before. As an aside: Out of everyone who has reported problems with the new release, and despite clear instructions to the contrary, only two people--two, out of everyone--have actually submitted anything resembling a log.

The API version didn't change so it should be fine. Feel free to test with 3.0.9.1.

We have released a new version, TARS 1.0.2b2. Please test with the latest Teamspeak.

Excellent. It looks like the A-10 and Ka-50 are stable. But we need reports from servers with relatively high playercounts (no upper limit--get as many people as you can). What's the biggest number of clients that some of you have tested this with?

The black buildings thing probably has to do with alt-tabbing out of full screen. TARS doesn't and can't touch the DCS address space let alone VRAM.

Thank you, do you remember who was transmitting that you couldn't hear on guard?

For now until the control panel based radio settings are activated. This is an msi thing, just go ahead and uninstall the old TARS before you install the new one to get around it. The wording in the dialog is misleading; evidently we left the flag on to stop if it finds an existing version on this particular installer build. I didn't update any art assets with the dialog; the 1.0.2 Beta 1 you see in the Control Panel text is correct. Ignore what the logo says for now. When in doubt: All logs. But in this particular case, the most relevant logs would be the ones created by the Teamspeak 3 plugin that are stored in \Users\<YourName>\AppData\Local\TARS. Keep reports coming. This is a good example of where the log would be helpful. If I had the log for something like this, it would provide the smoking gun required to duplicate the issue in the "lab." The plugin log shows who is talking and when, and on what frequency. Many times people have reported similar "bugs" only to reveal, in the log, that the person speaking on guard was actually on a different frequency and didn't know it, or some other configuration-related issue. These things can be very time-consuming to duplicate without logs.

TARS 1.0.2 Beta 1 I wouldn't mind seeing the Su-25 tested as well, but keep in mind that the primary goal here is to make sure things are still stable with the A-10 and Ka-50. Don't want to break those. If there are showstoppers involved I can fix these relatively quickly; it won't be months and months if you find a bug. Test with as many people as possible.

Definitely. I didn't want to hurt the A-10 since that's what most users play with TARS.

There is an issue related to 1.2.1 that I am dealing with; I will be releasing what we have tomorrow night. The fixed radios will be locked on two frequencies, respectively, until the next update, because stability testing requires it. I will be asking that people not submit bug reports unless there's a set of logs accompanying it. Once I'm comfortable that the new TARS is stable I will enable the control panel radio frequencies so that generic DCS: World aircrafts (Su-25, etc) can have their frequencies changed from the Control Panel. For now there is one UHF frequency and one VHF frequency.

Front-end stuff is done. All that remains before publicly releasing it for stability testing is to enable it for real time updates (So you can change frequencies in the Su-25 as you fly, for example). It won't happen this weekend but it may happen the one after.

Status update: We have a working version for DCS world. Functionality exists for Black Shark and A-10C and vehicle switching works. Any vehicle that doesn't have customized radio code can communicate with others with two different virtual radios that are configured from the TARS control panel. We're also working on a spectator frequency so that spectators can talk to people in-game on a certain frequency (will come in handy for training and so forth). That means that out of the box you'll be able to play with the Su-25T and any other aircraft in the DCS World universe, and those with custom panels will work the way they did with the original TARS. The P-51 won't be too much trouble and I'll add that in once we have debugged the core plugin to a relatively good level of stability. I will be putting this on the TARS website for testing when it's ready, but be warned that it's way more "beta" than previous TARS betas. Nearly done with the control panel side of it so expect an update soon. Thanks again for being patient.

paulrkii, do you have anyone making approach plates in your group?

I'm headed to the bar.

As with most of these problems, the best thing that can be done is to get us a track of the bad ILS behavior.