FONS

I've been a DCS pilot since more than 4 years, every year until the release of the 2.0 there was at least two times per year E-Shop sales of 75% during the period of a weekend. And since the 2.0 release, almost a year now, i haven't seen one again. Is there any official word about this?

Thanks!

Thank you very much man! I was going nuts with this. NaturalPoint should update his manuals and more for a 180€ peripheral :megalol:

Hi, just bought TrackIR, downloaded this A-10C profile, unzipped it, copied it to the profiles folder but it isn't showing up on the profiles drop down list of the TrackIR interface. When i try to copy the profile it asks me for admin rights, which i do it, but still it isn't showing up. I am running Windows 10, and i tried running TIR5 as admin, and the profile donesn't show up either. Also, tried to create a new profile on the TIR interface, and it isn't showing up on the profiles folder. Can someone help me? All the tutorials tell me it should show up as soon as i copy a profile in the C:\Program Files (x86)\NaturalPoint\TrackIR5\Profiles Thanks in advance, hope someone can help me so i can finally try this... :joystick:

Oh my bad, looked for it and found nothing sorry. Feel free to delete this if necessary.

Ah ok thanks for your time. i will have a look at it asap. Aah man that makes too much sense xD. The Ural's with Grad i placed were almost pointing 12 'clock to the target i was giving to him with the fireatpoint. I mean the cabin was on the way and you are right, the missile banks were turned slightly off to the right when i think the objective was more to the left, where the cabin was... And yeah, they were static, so that can be the main reason. Thanks for the info man. Never tried giving it a radius, because as far as i understood in the Manual, the radius command consists in establishing a radius where the AI will shoot randomly around it. Am i wrong?

Don't know if this post is in the correct section or it should be on the "Object Errors" section, move it if necessary. I've noticed that few skins look weird on the new renderer, mostly metallic ones. In general i would say they now look a bit overwashed due to the change of the way surfaces reflect light on the new renderer. For example, on the P-51D "Gentelman Jim III" skin, everything looks now too light. In this screenshot you can notice how all the decals placed on the metallic surface now look way too light. On this ones, you can appreciate how the numbers look different when they are over the mettalic or the painted surface. As this skins, few more affecting other aircrafts too. From what i've seen, the MiG's and the F-86F's are also affected. I know that rechecking all the skins will be a tedious job, but it needs to be done by the developers of the aircrafts in order to adapt them to the new graphics engine, although not now, because it's not a high prority issue, and there's a lot of things with priority over this.

I second this, i would say it's a shadow tinkering issue plus the trees popping on my face with the view distance set to ultra

Sorry for the delay. Got home an hour ago. I attached the mission. The group that has to fire is "Grad group 1", located at Kobuleti abandoned airfield. When i change said units for SPH they fire, but they won't being MLRS. I don't know if there's something else to do when the units are MLRS's... Thanks for your help, if you need anything just tell me. Exodus_Warfare_WW2-KW_Coop_V0.8.miz

Skatezilla, mate i would love to learn that and help you fill the community with good american aluminium skins!

I second this, Gentelman Jim III for example looks weird ingame, and that's a ED skin afaik sine it's on the vanila game, so it's job of ED to fix them. I am going to create a post in the appropiate section to see if devs already know this.

:doh:My bad, then i don't know what could i be doing wrong if the SPH fired and the MLRS not... Sorry for not replying faster, haven't remembered this till now. I will upload the mission tomorrow morning asap. Thanks for your help.

Also Nvidia Shadowplay, when not allowing desktop recording, just records real Fullscreen 3D applications and it isn't recognizing DCS as that. So there's for sure something wrong with the Fullscreen mode.

Just tested it. Can confirm that RAlt + Enter doesn't make Shadowplay to recognize the .exe as a real Fullscreen 3D Application, even inside the plane.

Copy, gonna test it in half an hour, thanks. I will tell you the result later.

I have the game set as Fullscreen, Disable Aero interface = ON, Autodetect Oculus Rift = ON, and VSync = ON. Graphical settings maxed out, save from water at medium, heat blur low, depth of field off, and shadows at high. To record with Shadowplay just the game window, the game must be on a real fullscreen mode. And at the moment, Nvidia doesn't recognize the game as that, so there must be a problem with the actual Fullscreen mode, as i don't have problems with any other game in Fullscreen mode. Then, you can set Nvidia Shadowplay to record everything that appears on your screen, by enabling "Allow to record desktop" under the Shadowplay options. BUT, if i do this, the DCS Intro picture that shows up when you start the game, the one with the DCS logo and a black background, flashes up sometimes Maybe the dcs logo flashing appears on the recording i just did, if i see it, i can upload it here. If further information is needed just ask me. Cheers. EDIT: found the flashing. here's the video:

I second the issue of clouds flickering/tinkering. I just saw this bug today, when i joined two servers with high denisity of clouds. So this leads me to believe its a problem of clouds tinkering because of a clipping issue. Haven't experienced this problem on missions that doesn't have clouds so close, that they clip between them. If the moderator thinks a video would help, i can do it.

I know the team is working so hard, thanks for the fast reply and good luck with everything!

This is the third time in 12 hours that the MP server list bugs for me and suddenly shows up just 3 servers instead of for example the (e.g.) 50 servers that normally shows up. This also happened to me once in DCS 1.2, but happened to me 3 times in 12 hours in DCS 1.5. It happens when i exit a MP server, and i just can fix it by restarting my router as i already saw in a post when this first happened to me in DCS 1.2 months ago. DCS has permission on the firewall, no kind of Antivirus enabled, and the executable is launched with admin rights. I have a Comtrend FTTH router giving me 100 mb/s via optic fiber. It's very annoying and more if i have to go to my router and restart it 3 times a day. Hope this gets a fix soon. EDIT: 4th time in 12 hours. This is so frustrating. It happens when i exit my own machine hosted MP server. The full list bugs and just 3 servers show up there now until i reboot my router again. the last one was a full 3 minute reboot, so it's not a router problem. :(

Fire at point command not working for MLRS and Grad vehicles yet. Have been a few days trying to make the fire at point command to work with a group of Grad Ural's without success. Finally, today, i end up in a 3 year old bug report saying that the fire at point just works for artillery (SPH) and not for Grad/MLRS. http://forums.eagle.ru/showthread.php?t=98110 So tried changing the Grad for Artillery and it worked... Please, fix this soon, it's a more than 3 year old bug...

Hi, i am trying to make an Ural Grad to shoot at a certain point to give the battle more ambient. I've read a post somewhere about a guy saying that first: - give the ural the excellent skill - give the ural the fireatpoint command under the triggered action section - then create under "set rules of trigger" a trigger of (1 once - time more = 10 s - Ai group on) As far as i understood, the grad group should be turned on 10 secs after mission start, and with the excellent skill, start firing 2 minutes before. But even waiting more than 4 minutes after mission start, the ural is't even ready to fire, with his rocket bay, yet not aiming at the point. I've also tried to use instead a zone trigger, to turn the ai on when a blue coalition plan enters a determined zone, but still the same. Could someone help me with this? EDIT: Ok, just found after a few days eating my head with this, that the fireatpoint isn't yet working after seeing some posts 3 years old with people saying that the fireatpoint is bugged, and just works for the artillery, not for MLRS launchers... gonna create another bug report to see if they finally fix this...

Beautiful. Thanks for your work man.

Just saw on the today's changelog the crash is fixed. This can be closed.

I am doing a mission, and i included modules i don't have, for example, the MiG 15. I run the mission to see the skins i selected for each of the modules, but when i try to get inside a module i don't own, the game crashes. This repeated each time i tried it.

20 more minutes of research and i wouldn't have done this post. Just found it. I swear i looked for it before doing the post :doh: Can't delete it already, so if anybody wants to delete this post i don't mind. EDIT: Oh almost forgot, just in case this is the thread: http://forums.eagle.ru/showthread.php?t=143254&highlight=swastika