Jettix

HelloHave noticed that CDU indicates wrong ETA of next waypoints, but ATA last passed point is indicated correctly.The flight EBRR-LEIB have been started from c`n`d.I changed time in main sim menu (dont remember before AC select or after - but does it matter?)Would appreciate for any help

This is something that is starting to pee me off! For some reason, the last few flights I have been unable to reduce power sufficiently on my approaches. Power will not fall below about 40%Ni and I have to use full spoilers abd flaps to get the plane down on the ground. Not ideal. The power simply appears not to want to drop. Is there something I am doing wrong. I read elsewhere on the forumn that a few other guys were experiencing the same issue. Is this a bug, or as I said, is it something I am doing wrong? Help is quickly needed, thanks guys.

What Cost Index you use?

there was no problem before sp, same after

http://www.macecraft.com/ - vrey powerful and useful thing

Hi, I have another post in here regarding the frame killer performance with the ENB series

It`s very starnge that you`ve got such problem. Usually ENB has nil performance price. Make sure enbseries.ini configurated as below. It may help to get rid of performance lose [GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=0BugFixMode=1SkipShaderOptimization=0QuadVertexBuffer=0EnableShaders_3_0=1UseMRTRendering=0AdditionalConfigFile=[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0EnableDepthOfField=0.....[ENGINE]ForceAnisotropicFiltering=0ForceDisplayRefreshRate=0ForceDisplaySize=0

FIBER_FRAME_TIME_FRACTION=0.33 & SmallPartRejectRadius=2 - useless after SP2 TERRAIN_MAX_AUTOGEN_TRESS_PER_CEL=1200 & TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CEL=800 - may cause stutters

Since we are with the Replays subject. Do you guy know any other program beside EZDOK to place cameras at will, like for example at the runway end?Thanks

Same FS Recorder again.

+1 for TS post

I had 2 episodes when FSPax have induced failures - engine damage due to a bird strike and lose engine power during take-off. Both times NGX reproduced the entire sequence of damages involving FMS, hydraulic and electrical systems.The only minor issue I have - FSP doesn`t recognize strobe switch position. Each time I get penalty for not turning on them.

u can find quite a few in "C:\Windows\System32" just copy it to the fsx dir

I am afraid it has no sence. This folder contains 64-bit versions of files wich are not utilized neither sim nor ENB. Sim hooks 32-bit versions from redirected directory C:\Windows\SysWOW64.ENB uses d3dx9_26.dll d3dx9_40.dll. If you have DirectX those libraries must be installed, if you dont - can get them here http://enbdev.com/download_en.htm I`ve missed point you ment 32-bit OS. If so - you are right

This file is the main library of Nvidia driver.Have you recently reinstall driver? must be previous version have not been removed completely. it is not enough now just to choose 'clean install' for complete reinstall. I have to use DriverSweeper, Nasty File Remover and CCleaner to remove all files and registry entries from previous version.Also It will be useful to subscribe your new driver in display.cfg.

I have tried demo and didnt`t like it. Perhaps due to what I am member of FSPax fanclub ;) FSCap has a zillion settings and someone can say it can be configurated exactly. As for me in many respects they are redundant in contrast to the laconic and perfect style of FSpaxbtw Hope Dan Polli is all right no matter where he is and I thank him for his work each time when start FSPax.

IIRC antialiasing doesn't work in windowed. Or am I incorrect? I's much rather go without ENB than AA.

Being set as described in Tab`s instructions AA fully works. Otherwise it would not be worth the efforts To All I use it last few days and have not found any flaws. As result of applying this tool you gain complete emulation of fullscreen mode without any problem specific to 'native' sim`s fullscreen mode. If you found out any negative feature please post here.

The tool is not applicable for win 7 right?

No, wrong. I use it under Win7 x64 without problem. Try to start it as admin

Nice discovery, but you're forgetting one important downside of the windowed mode: VSync doesn't work with it, so there will be some tearing.

I`ve read this is due to the Windows Aero forced turns off when Sim launches. So, to make VSync work again you need turn on Aero by applying the following batch after Sim has been started:

net stop uxsmsnet start uxsmsexit

I dont think there will be large workload for modern VGA.Fsx.cfg should contain the lines ForceWindowedVSync=1ForceFullScreenVSync=1 and driver should be set as 'Controled by application' for Vsync.To tell truth I didn`t try this, only read before. But they say, it works perfectly.

fellows, try this http://forum.avsim.net/topic/347945-ngx-enbmod-and-fspassengersx-nothing-impossible/

Like many others, I have experienced problems when NGX, ENBmod and FSPassengersX. It was not possible for me to refuse of any of them. But I have had d3d9.dll-caused CDT almost every flight. (must note, I have had no problem when useing any two of these three add-ons, but noway three together).The root of the problem has been found in full screen mode. Windowed mode is completely devoid of these problems. But frames of window look so annoying.Here, a small utility that allows you to remove the frames of window (incl titlebar) and stretch the window to full screen. No installation required. Download and unpack in any directory.Start sim and flight. Switch sim to windowed mode. Launch the tool. Select Simulator window in explorer tree view, then switch to 'Style' tab and check off WS_DLGFRAME, switch to 'Size&Position' tab, select 'Maximized' and then push 'Modify' button. "auto-hide the taskbar" must be checked in taskbar properties.Here it is. Now you get sim window fitted to fullscreen but you can see 'fullscreen mode' unchecked in sim menu.There will be no problrme with alt-tab, changing view, access to menu and desktop. No more flashing when new in-sim window appears, and CDT when FSPaX flight reports.Hope it will help to all who likes Hi-End NGX Bird, HDR ENB light and passengersX. Plz write your feedbackSorry for poor English PS Note Sim`s window tittle - its a facepalm.

captain56 read this http://goo.gl/Oy8vU and this http://goo.gl/561sZ regards

Hi all.Dont want to start new topic, so put it here There is a little bug in panel.cfg - not slashed annotation line.

////////////////////////////////////////////////////////   VC SECTION 4//   Upper/Lower Eicas - CDUs - Main Panel Annunciators - CDU button lighting - Main PanelInstrument Lighting///////////////////////////////////////////////////////[VCockpit04]size_mm=1024,1024pixel_size=1024,1024texture=$GaugeFourbackground_color=0,0,0 

Of course it`s not a root of all evil but the structure of file must be kept. Maybe will help to somebody

Dave, problem you are experiencing is not due to the PMDG, but ENB and probably UIAutomationCore.You should try UIAutomationCore fixWhen I use FSPax I have no problem during daytime, but on dawn/dusk almost every flight I`ve got CDT. Unfortunately, NGX+ENB+FSpax almost are not compatible because of the algorithm of panels lighting. In my opinion, this problem is unsolvable.

AffinityMask=224 - very strange number for your specs. How did you get it?

Thank you very much!

I can confirm that the gear is down prior to landing as per my flight log:

Marc, wouldn`t you be so kind to tell wich the program has created this log

One test flight egkk-lfpo in custom sceneries. No freezes where were before. But seems (maybe only seems) performance has become slightly worse, especially at approach.Also, FMC cant determine vertical deviation correctly (VNAV mode) if app runway has been changed. May be my mistake here

It works for me and many other people.

Ethan, sorry, off course it does. I`ve missed the words "d3d9.dll that comes with Antilag" in your post. I use it myself.I thought you ment d3d9.dll from FPS_Limiter_0.2.Antilag works much more smoother than FPS_Limiter_0.2