Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/13/2016 in all areas

  1. Good morning, leaving Spokane KGEG to Juneau Alaska PAJN Carrying 78 Passengers and there gear. Expected bumpy flight in spots but over all a good flight. Our Cuz Alt. today is expected at FL320 for most of the flight. Enjoy your flight and thank you for choosing ALLied Air Carrier
    1 point
  2. There's nothing out there at all that can touch this plane, it's simply just the best!
    1 point
  3. Not a problem. Not asking to support your products on untested (Beta) OS. This is why the disclaimer: "IXEG Team, this is for your information only (I purposely use Betas to discover problems)" So, this is just an FYI (since I came across this). Just trying to help.
    1 point
  4. I've now done very first test with new GTX 1070. Great card by the way and I learned 2 things - first you can push everything much further and second you still cannot push enough it to maximum values. If you need push everything to max, probably wait for the cards that will be introduced in 2025 (if you will be still on X-Plane 10) :-). As regarding to FPS drop during the flight, I still noticed it. Not to single digit numbers like with GTX 960, but to numbers below 20. SMP was still reporting more than 4GB VRAM and 20GB RAM available. Quick cycling of SMP settings (for example turn cloud reflections on water to OFF and back ON) resolved it immediately. However what I noticed this time was interesting - overall CPU utilization was around 25%, but when FPS dropped, one of the CPU thread (1 of 8) was saturated to almost 100% while others were underutilized. Cycling SMP settings reduced that CPU thread utilization back to 70s. So maybe CPU is bottleneck or CPU optimization is not good enough. Not sure how much can be done here since X-Plane is limited because of its OpenGL engine. I am still keeping an eye on it.
    1 point
  5. I think that I had a conflict with X-Assign or Head Shake. I uninstalled them and things stabilized some. The only thing now is I have no Reverse. Should the " / " key initiate full reverse? Or " shift + / " ? I checked in key assignments and it's set for reverse. Thank you for your help, - PT
    1 point
  6. A helo trip in gale force winds at jfk, stick config setup for the ixeg, never again lol I was like a fly in a wind tunnel !! To cap it off, a trip in a Phantom Tony
    1 point
  7. Hello Guys (and Girls (if any)), 
 I created a support ticket almost 2 weeks ago (Ticket #YR1BG, Sat, 05/21/16) that I still haven't received any reply to. I'm eager to get SkyMAXX (SM) working on my new system so the wait is kind of torture. Are you ignoring me?  
 My problem is that I have built a new dedicated system for X-Plane and while doing so I wanted to test different OS to see which runs best with X-Plane. 
 Originally I used my MacBook, then I tried Mac OS X on the new system, then Debian (which I found you sadly didn't support (yet)) and lastly Windows 7. Since me and my brother live together and also fly together SM was also installed on his MacBook. The idea is to have X-Plane running on the dedicated system while me and my brother use our two MacBooks as Pilot/Copilot. 
 So... My problem is that since I have installed SM (and also the Saab 340A I purchased) on both our MacBooks and on my dedicated system with Hackintosh/OSX all my three activation slots have been used. When trying to activate SM on the Win 7 install it throws the "Activation slots used" message. I haven't tried activating the Saab yet but I'm assuming the same thing will happen. 
 I didn't think of the activation limit when installing, if I had then I would have waited with installing SM and the Saab until I had decided on which system to use. 
 Could you please help me with this. As I wrote in the ticket I don't need them on my MacBook anymore but uninstalling them didn't "reactivate" one slot. 
 Best regards Jonas
    1 point
  8. For the record, this support ticket was replied to. A reply back was never received from your end. I would encourage you to check spam folders. The bottom line for this situation is we do not condone nor allow sharing of files with anyone. This topic is closed.
    1 point
  9. I (think) I get it Ben. Your software has been pirated a lot and your angry about it, but why accuse me of something before you know if it's true? The correct thing, in my humble opinion, would have been to reply with something like ”Jonas, you can’t use our software on both your own and your brothers computer, even when they’re used simultaneously. For this you need to buy another license, sorry that I couldn’t help you”. Then, since I find your software attractive enough, I would have purchased another license without complaining about it. Being treated like a criminal, however, isn’t a very nice experience Ben. Probably the worst thing you could do to a customer... P.S. If you're hungry I gladly share the food in my fridge with you Ben. D.S.
    1 point
  10. Dice! I figured it out. Now no one has any excuse to not have custom failures in their aircraft! Here is my code. Use it! --list some things you want to trigger failures dr_sim_ITT_c = xp.getDataref("sim/flightmodel/engine/ENGN_ITT_c") --list what failure datarefs you want to fail dr_sim_engine_fail1 = xp.getDataref("sim/operation/failures/rel_engfir1") function engineOverStress() --build a timer that begins when the limit is reached, but is destroyed if the limit is no longer reached before the timer goes off local timer_overStress = nil local ITT = xp.getFloatV(dr_sim_ITT_c, 1, 2) --either of my engines in this case --start an argument if ITT >600 then if (timer_overStress == nil) then timer_overStress = timer.newOneShot("failEngine", 15) --calls failEngine() in 15 seconds unless the pilot reduces ITT! end elseif ITT <600 then if (timer_overStress ~= nil) then timer.stop(timer_overStress) --stops the timer when pilot corrects his erroneous ways end end end ------ function failEngine() --the dirty work... xp.setInt(dr_sim_engine_fail1, 6) --thanks Jim! --[[ Ok, here is what I had wrong: The failure method used in X-Plane has 7 modes- 1. always working [0 in lua] 2. mean time until failure [1] 3. exact time until failure [2] 4. fail at exact speed KIAS [3] 5. fail at exact altitude AGL [4] 6. fail if CTRL f or JOY [5] 7. inoperative [6] ]]-- end Now go forth and fail!
    1 point
  11. Looks like you've dug yourself a nice little hole trying to activate on as many machines for as many people as you can. Zero sympathy for people who think even "marginal" piracy like a hackintosh is ok. Even less sympathy for sharing with your brother.
    -1 points
  12. How about I help myself to the food in your fridge and we see what your attitude is like when I'm done eating?
    -1 points
×
×
  • Create New...