M
marco Starglider
Guest
hi,
a while ago i had a good project in visual studio 2005 (vc++), with a good
build and
a good .exe file. it used some basic openAL functionality,
with muliple buffers and sources. the sounds played
perfectly at the right moments.
i wanted to check the compatibilty and set the comp.
mode (in .exe file prop's) to '95 and medium res. or something.
since then i have an openAL problem with my project, in that
sometimes a source won't play. i have set the comp. mode back
to normal immediately after, but i have kept the .exe file from the
build in my solution folder, with a different name, for back-checking
possibilities.
i don't exactly know, what the comp. mode does with all the files,
related to your executable.
i guess all the files i load and use during run-time, are somehow affected
or associated with comp. information.
how does it work? and how do i fix this?
regards,
m
a while ago i had a good project in visual studio 2005 (vc++), with a good
build and
a good .exe file. it used some basic openAL functionality,
with muliple buffers and sources. the sounds played
perfectly at the right moments.
i wanted to check the compatibilty and set the comp.
mode (in .exe file prop's) to '95 and medium res. or something.
since then i have an openAL problem with my project, in that
sometimes a source won't play. i have set the comp. mode back
to normal immediately after, but i have kept the .exe file from the
build in my solution folder, with a different name, for back-checking
possibilities.
i don't exactly know, what the comp. mode does with all the files,
related to your executable.
i guess all the files i load and use during run-time, are somehow affected
or associated with comp. information.
how does it work? and how do i fix this?
regards,
m