Jump to content

frank7006

Members
  • Posts

    52
  • Joined

  • Last visited

Posts posted by frank7006

  1. 1 hour ago, Rudel_chw said:

    The autoupdate log shows that you have normandy and ww2 assets installed:

     

    INFO : DCS/2.7.1.7139 (x86_64; EN; WORLD,F-5E,RAZBAM_M-2000C,MIG-15BIS,MIG-21BIS,F-86F,FW-190D9,MI-8MTV2,UH-1H,P-51D,KA-50,A-10C,MAPLEFLAG_F5E_BFM_campaign,A10C-REDFLAG_campaign,F15C-REDFLAG_campaign,FC3,CA,NORMANDY_terrain,WWII-ARMOUR

     

    Probably your antivirus may be interfering .. check the antivirus log, or add an exclusion for the /program files/eagle dynamics/ path and then do a dcs_updater repair.

     

    That worked! Thanks!

    • Like 2
  2. On 6/6/2021 at 2:04 AM, MAXsenna said:

    Have you checked that it isn't disabled in the module manager?

    Sent from my MAR-LX1A using Tapatalk
     

     

    I have Normandy map listed under the Terrain tab but I don't see a "WWII Armour and Technics" module listed anywhere and every time I try to load Normandy using a WWII aircraft like the P-51 I get the error: "Need Modules for load mission: WWII Armour and Technics".  I'm assuming there must be a module called "WWII Armour and Technics" listed under the Modules tab but there isn't.

     

    I was a DCS WWII: Europe 1944 backer and and under the backer rewards section of the DCS website it shows that I have a license for the "Normandy Map" and "WWII Assets Pack".  I assume the "WWII Assets Pack" and "WWII Armour and Technics" are the same thing or that "WWII Armour and Technics" is included in "WWII Assets Pack"?

     

    I guess it looks like DCS doesn't think that I own the "WWII Assets Pack" since it's not listed under Modules or it didn't install for some reason.  I've attached my autoupdate_log.txt file if it helps.

    autoupdate_log.txt

  3. On 5/27/2017 at 11:48 AM, LeCuvier said:

    Same here. After Normandy map installation I tried to run a Normandy mission, and it popped up a message saying something like "WWII Armour and Technics required". Obviously I need to install the assets pack. But it's not listed in the module manager.

    I found the solution via the "Support" page. It tells you to download an install batch file to the DCS World root and run it. So now it's downloading another nearly 2 GB of files, and hopefully that will be it. I started the update process to 2.1 yesterday evening, and now it's already 17:45. This thing is HUUUUUUGE!

     

    I downloaded this batch file and added it to my root folder and ran the file and it didn't download anything.  I still don't have the WWII assets pack installed even though I own it.

  4. If you're using high drag bombs and the airplane thinks it is at a high height then the solution will be very steep.

     

    Radio altimeter only works to 5,000'. Make sure to select "RS" on the PCA and that you can see the radio altimeter providing a valid height in the upper right corner of the HUD.

     

    I didn't have RS selected on the PCA. That step isn't listed in Chuck's guide and they didn't mention it in the videos I was watching. Thanks for the help!

  5. Did you set the Radar to proper A-G mode for ranging? did you turn on the radio altimeter?

    what was your altitude and which bomb did you try ?

     

    I set the radio altimeter to M. I also tried the other two modes. I selected BF1, the only option available in that mission. My altitude varied from starting my dive at 15,000 ft to starting at 3,000 ft.

  6. edit: NOT A BUG: I didn't have RS selected on the PCA. That step isn't listed in Chuck's guide and they didn't mention it in the videos I was watching.

     

    I tried CCIP bombing for the first time on DCS 2.0 NTTR with the instant action ground attack mission. I followed Chuck's guide and a couple youtube tutorials and couldn't figure out why I would never see the CCIP pipper when diving to bomb and then I noticed that I have to pitch down 90 deg to see the pipper because the pipper is stuck at 90 deg down. It doesn't move. I'm over 400 knots as recommended. This has to be a bug.

  7. I wonder if it's possible to create a mod or an alternate cockpit version of the Mig-21 that is performance friendly enough that it would run at a good frame rate in virtual reality. I have a 980 TI and i7-6700K 4.2 ghz and the frame rate is unacceptable using the Oculus Rift. Pretty much every other module gets a good frame rate.

  8. That's not just you. I also have a black flickering in just the right side of the Rift. I also thought it was a browser or some other window I had open when I started DCS, but even after closing everything I get it.

     

    You're not alone :thumbup:

     

    I'm glad you guys mentioned this. I thought I was the only one and I thought it was a problem with my DK2. I get the flickering in the left eye.

  9. JaySmiz, Timewarp is already implemented or Wags would not have said so. It's already in DCS 1.5 BETA.

     

    You can see the words Time and Warp in the following files if you have a look.

    C:\... Eagle Dynamics\DCS World OpenBeta\Bazar\shaders\PostEffects\oculus.fx

    C:\... Eagle Dynamics\DCS World OpenBeta\Bazar\shaders\PostEffects\oculusMesh.fx

     

    80% increase in framerate from Timewarp optimisation ... you are an optimistic person, which is not a bad thing, and I hope you are right.

     

    Yeah, I know, I acknowledged that it was in the same post you quoted me in. I just said that I was guessing that it hadn't been "fully implemented" yet because we should see much larger FPS gains than we're seeing now I would assume based on my limited experience with time warp in FlyInside FSX.

  10. I have Flyinside FSX and version 0.7 isn't stutter free like you are saying. In-fact, it stutters more for me in FSX then it does in DCS 1.5 once I go below 65 FPS. That CPU you have isn't that great running at 3.5 Ghz. I know that's hard to imagine, but when I lose my overclock of 4.1 Ghz on my i7 930, boy do I see a difference with judder. Dropping down to 2.8 Ghz and lossing my overclock gives me terrible judder, so it could well be that i3 3.5Ghz causing it.

     

    I don't believe I said it was stutter free, in fact it's far from that because it's a terribly optimized engine. FlyInside provides two FPS numbers: one for the actual FPS and one for time warp assisted FPS. On my PC the time warp assisted FPS only drops below 75 when the actual FPS dips below 40. That's where I got my 80% boost number (75 is an 87% increase over 40).

     

    My CPU of 3.4 ghz shouldn't be that much of a factor on a properly optimized engine but unfortunately DCS 1.5 still needs much improvement in this area.

  11. FYI - via PM to Wags

     

    Thanks, good info. If it's enabled by default in 0.7 then that means that all demos and games that are 0.7 compatible have async time warp but some of those games don't run any better than they did in 0.6 so I imagine that just because it's enabled by default doesn't mean that it's really being utilized until the dev chooses to utilize it. I imagine that's what they're working on now. We might see an 80% fps boost once it's fully implemented as I saw for myself in FlyInside FSX.

  12. DCS 1.5 Oculus Rift DK2 performance

     

    I have an i7-3770 3.4ghz quad core and a Nvidia GTX 980ti superclocked. Here is my experience with performance in the DK2 in the DCS 1.5 Beta:

     

    Mig-21 performance is atrocious. It's by far the worst and is absolutely unplayable even on my 980 ti superclocked - the fastest card you could possibly buy. If I turn every single graphics setting to its absolute lowest level I get on average 30 fps in the 'takeoff' instant action scenario. The other scenarios are similar in fps.

     

    The other aircraft modules don't work very well either and even keeping a steady 75 fps on medium graphics settings is not possible when flying low near cities. Some of the modules like the Mig-15 and F-86 run pretty well on medium settings some of the time though.

     

    Shadows - even the lowest setting - are a huge performance loss and have to be turned off completely.

     

     

    If ED implements asynchronous time warp we should see a roughly 80-90% increase in performance. When I played the FlyInside FSX demo, asynchronous time warp would maintain a steady 75 fps even though my actual performance would dip down to 40 fps. Below 40 fps it could not hold 75 fps.

     

    If anyone has any tips or tweaks please post them here. I'm always looking for anything that will boost my fps in the DK2.

  13. Full of it, nope - enjoying pushing your buttons due to your attitude, yep!

     

     

     

    Yep I saw that, thanks for posting it. I was actually going to get around to mentioning it to the OP but he had to drop the attitude first - which he hasn't.

     

    I imagine most people who attack another person and are then proven wrong would have nothing left but to criticize the other person's "attitude".

  14. Yes, I think you are full of it. Go ahead and post a live stream of you trying 100 times with it succeeding only twice.

     

    Ah yes, so you don't actually know what you're talking about then. Your irrelevant question has now been proven to be based on an assumption that you made and a really bad assumption considering lots of other people in here and other forums were talking about it failing "9/10" times or higher. It's probably different for different people based on their systems but in my case it was literally about a 2% success rate. Now, with the Vista compatibility fix that someone figured out, it's a success rate of about 80%.

  15. Where did I say you said that? Maybe you should work on your reading comprehension.

     

    Just as "2%" is a stretch, 100% is a stretch.

     

     

    You asked, "You honestly believe that everything will work 100% of the time?" Why would you ask me that question? Nowhere did I claim that I expected it to work 100% of the time or anything close to that so explain what relevance that question has.

     

    I said "literally 2%" and that's exactly what I meant which is why I added the word "literally". You said, "'2%' is a stretch". Are you claiming that you know that the success rate of getting the DK2 to work on my PC with DCS 1.5 is much greater than 2%? Please explain how you know this.

  16. What?

     

     

    You are talking about a beta DK2 and a beta DCS 1.5... You honestly believe that everything will work 100% of the time?

     

    Find a quote from me where I said anything remotely indicating that I believe that "everything will work 100% of the time" and I'll respond to you further.

  17. I think SweetFx is not going to work ever with direct mode (the way Oculus is working since SDK 0.7). The increased resolution of the consumer version sould be "enough" to play without it.

     

    The only thing that developers can do is to put some kind of image processing in the render code. For example Elite Dangerous lets you configure some supersampling resolutions but don't know if it will work once they introduce direct mode with SDK 0.7.

     

    SweetFX substantially increases clarity. I would choose SweetFX over direct mode any day. We need SweetFX and the higher resolution of the Rift CV1. I would guess that the increased clarity you get from SweetFX is more substantial than the increase in clarity you get from the higher resolution of CV1.

×
×
  • Create New...