Sunday, December 23, 2007

Avid Pro FILE_EXCEPTION problem during startup

Если при запуске Avid Pro Express появляется сообщение

Error FILE_EXCEPTION filename:C\Documents and Settings\All Users\?УНЫПИЬЪЧ\sHARED Avid projects\

Если windows - русский, необходимо перенаправить Shared Documents. Делается это так

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Explorer \ User Shell Folders

Common Documents = %ALLUSERSPROFILE%\Shared Documents
исправь на путь, который не содержит русских букв в названии, например D:\Shared Documents

p.s. Big thanks goes to Russian Avid forums for usefull info.

Thursday, November 22, 2007

Lightwave 9.x OpenGL acceleration tip

Some people report slow OpenGL reaction in Lightwave`s modeler even with powerful graphics cards. For example, in default configuration with my GF 8800 GTS it works very slooow with objects larger then 1000 polygons. Compares to Maya or Luxology`s Modo - they can easily handle much more heavy objects with no delay. I spent some time to discover the reason. Check your Display settings in Modeler, there, you will find GL tab. There are some settings that by default set to some kind of safe mode.

On the pic you see correct settings (for nVidia boards at least, not tested on ATI).

First - texture size - only depends on amount of your GFX card memory, even with 2048x2048 it fly as well as 256x256.
Second - important- use multitexture engine instead of GLSL for acceleration. Next one, transparency sorting - doest affect speed. Finally goes second important thing - buffered VBO - it enables cache mode for your graphics chip. And I dont recommend you to use mipmapping since it useless for latest cards. All other settings depends on functions supported by your video card. I set them on because 8800 provides best visualization result with no speed degrading. Enjoy!

Saturday, November 10, 2007

Leopard (OS X10.5) and Airport problem

Problem most people describes after installing Leopard on Mac Pro stations and some iMacs Airport works but couldn't find any WiFi networks.
Symptoms: Airpot indicator on the tool bar Grey, no networks found.
Aiport device Broadcom 43xxxx

Solution: Install Mac OS update "Login & keychain" from official site. After reboot problem will be fixed.

Other possible solutions for this particular problem: In case you upgraded from previous tiger version in /Library/Extensions/Airport remove Airport.kext (part from Tiger version of Airport driver, not needed in Leopard). Try boot in safe mode (hold Shift during boot) and restart.

Sunday, July 01, 2007

Asus M2N - SLI: unknown away ASPI device problem

Problem: after installing drivers there is still unknown device in device list.

Solution: 1. Disable AMD Live! feature in BIOS.
2. Download AMD Live! patch from Asus site (Utilities part of downloads section)

Seems like Asus away feature (been used in most of Asus motherboards) have problem with AMD Live!. Simply installing driver for Asus ASPI BK0001 device is not enough. You need patch to fix this (if you want this feature) or just disable it in BIOS.

Tuesday, June 19, 2007

Fedora 7 install on VMware physical partition

I found some problems during install process of FC7 on VMware`s disks when they configured as physical partitions .

For successful installation (if you going to format, or repartition disks) you need to let Fedora full access to disk. So you need to make a new disk under VMware and choose entire physical disk instead of partitions - don`t worry Fedora installer will see other partitions and let you select what partitions to change. Thats it! When you got Fedora booting fine you can go back to Virtual Machine setup and make another different disks (to replace current disk with full drive access) with physical partition selected to avoid damaging data on other partitions (but its not so critical in fact).

For those of you who want to know why is that: VMware can`t trick guest operation systems thinking that selected f partitions are independent disks (unless you using hardfiles for VM disks). In fact Vmware just preventing access to partitions those are not in list. So if, for example, you have 500 Gig drive with 4 partitions (boot, VFAT, ext3, swap), and decided to choose linux partitions as independent drives(one for boot and, one for /root and swap), Linux will see complete 500 Gig drive for every partition. So Linux will think you have two different 500 Gig drives. And as you can guess you get cross pointing problem. Also Grub will not be able to get access to boot block. Thats why its so important to let hard disk and partition tools see drive as it is.

Thanks to many people who share with this solution!